- Added custom commands module
- Added example /collections command and sub commands

Click to expand...

All users who purchased CastleGates will be automatically added to the Orestack buyers list.

Handling one project will be much easier and will allow me to push updates faster instead of leaving one project behind and then having to catch up.

Also the complexity and amount of features/effects/configuration is overwhelming especially when both projects share the same stuff. By making Orestack a complete MMO RPG Core that handles everything that complexity is justified as you will no longer need any other plugin to create your MMO server.

Anyways that's the goal, for the time being you can disable any modules you don't need.

- Merged gates into Orestack
- Replaced enabled-modules with disabled-modules, so that when updating new modules are always enabled by default.
- Improved dependency compatibly by fixing an issues related to PlotSquared

Click to expand...

Regeneratemenus/buttons.yml to avoid config errors when updating. If you haven't created any menus you can just deleted the menus folder altogether.

- Added custom collections system with default collections (farming, mining, combat, foraging, fishing)
- Added default placeholder-fallback and custom-placeholder-fallbacks
- Added nested condition statements
- Added end of configuration message in config.yml
- Added custom placeholders for chat messages
- Added toggle option for all modules
- Fixed exception when clicking slot 54 of a menu
- Added menu actions: openPreviousMenu, openFirstMenu
- Now you can no longer create an item with material air.
- Merged growth-bars and health-bars into progress-bars.
- Fixed not being able to call functions from inside other functions.
- Now only commands of enabled modules are registered
- Fixed issues when calling other plugin api's after they had disabled

- Added unlockable/lockable recipes, that will be used in new collections system that is coming up

- Added lockRecipe(s) and unlockRecipe(s) actions

- Added player-data database system, this allows me to save per-player data easily. This will be used for features such as permanent flags, collections, etc...

Click to expand...

- Added 9 different triggers for custom items
- Added max-uses and uses options for custom items
- Added placeholder support for custom items
- Added toolHasUses, toolHasUsesLeft conditions
- Added consumeToolUses, grantToolUses, restoreToolUses and giveTemporaryFlag actions

Code (Java):
tool:
type: iron_pickaxe
unbreakable: true
flags: [hide_unbreakable, hide_attributes]
name: '&7Tool'
lore:
- ''
- '&aUses: {tool_uses}/{tool_max_uses}'
- '&dCreated by: {player}'
max-uses: 10
uses: 10
on-block-break:
if: toolHasUsesLeft # default is 1
do:
- consumeToolUses # default is 1
else:
- cancelEvent
- sendChat &4Your tool is out of uses
on-left-click: sendChat You left clicked
on-right-click: sendChat You right clicked
on-left-click-block: sendChat You left clicked a block
on-left-click-air: sendChat You left clicked air
on-right-click-block: sendChat You right clicked a block
on-right-click-air: sendChat You right clicked air
on-swap: sendChat You swapped item with offhand
on-drop:
if-not: hasFlag confirm_drop
do:
- cancelEvent
- giveTemporaryFlag confirm_drop duration=10
- sendChat &4Press Q again to drop item

Click to expand...

- Added custom menus and buttons to orestack
- Added openMenu and closeMenu actions
- Added /orestack menu open <menu-name> command
- Fixed a bug from the last update related to the keep config up to date feature
Code (YAML):
title: '&7This is an example menu'

rows: 3

layout:
- 0 0 0 0 0 0 0 0 0
- 0 _ _ _ _ _ _ _ 0
- 0 0 0 0 C 0 0 0 0

buttons:
C:
type: BARRIER
name: '&cClose'
on-left-click: closeMenu

Click to expand...

When updating to this new version your config.yml will be automatically updated. Check it out!

Let me brag a little, Orestack is now the plugin with the best yaml config system. Not only the error system is the most detailed but it now also supports comments. So saving configurations will no longer remove your comments and it allowed me to add an auto updating config.yml that preserves comments!

- YamlConfig now supports comments to be loaded/saved to/from yaml.

- Added keep-file-up-to-date option in config.yml, when enabled your config will be updated automatically while also keeping comments and key order.

- Replaced dropItem with dropItemAtCoords, dropItem now works as a jolly by setting `default-item-drop-target` (block, player, coords) inside the config. It is faster to write and allows for better consistency across your project, while also allowing you to switch effortlessly between modes for all your generators at once.
Code (YAML):
# Default target is set in config.yml
on-break: dropItem dirt

# Target override. dropItemAtPlayer should be preferred over this
on-break: dropItem dirt target=player

Click to expand...

- Added growth bars to config.yml with 10 example styles
- Fixed cancelEvent action not working with on-break trigger.

Click to expand...

- Added damage-overflow options in config and per generator phase.
- Now if overflow is enabled and damage exceeds current phase health it is passed to next phase. This allows to one hit generators that use health mechanic if the tool is powerful enough.

- Now efficiency is a damage multiplier instead of adding 1 dmg per level.
- Addedefficiency-damage-multiplier-by-level:
Code (YAML):
# The damage multiplier based on the efficiency enchant level.

efficiency-damage-multiplier-by-level:
1: 1.25
2: 1.30
3: 1.35
4: 1.40
5: 1.45
- Added ignore-missing-translation-errors
Code (YAML):
# Whether to ignore missing translation errors from language file and use default values instead
ignore-missing-translation-errors: true