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

- Added support for block and item displays for FancyHolograms.
- Fixed line height for FancyHolograms to match DecentHolograms.
- Fixed existing generator y-offsets resulting too high for FancyHolograms.

- Added toolIsExecutableItem <item_name> condition
- Added toolIsEcoItem <item_name> condition
Code (Text):
on-break:
if: toolIsExecutableItem Free_Bucket5
do: sendChat &aTool is a free bucket!

Click to expand...

Current requirements for per-player generators: Paper server on 1.19.3+ with packetevents installed. Normal generators will work the same.

- Added server side calculations for break time, player distance/facing from/at block. This fixes exploits from fake packets from clients.
- Fixed exception on servers not running paper
- Fixed exception on servers without packetevents installed
- Fixed per-player generators being able to be created on servers which where missing requirements.
- Fixed per-player generators blocks disappearing when mining a non-harvestable stage.

- Added per-player-generators-barrier-layouts in config.yml (Regenerate config to see new options)

Code (YAML):

Code:

# Customize Barrier Layout
#   1. Definition -> A fake block is a block that only exists on the client but not on the server.
#   2. Visual problem -> You might see entities/items/players walk into fake blocks.
#  3. Anticheat problem -> If a player stands on a fake block for too long, the server/anticheat will kick/ban the player for flying.
#  4. Solution -> Place barrier blocks on the server-side, the player will not see them, but they will act as a physical layout.
#   5. Limitation -> Players might not be able to reach certain blocks and might run into invisible barrier blocks.
#  6. Customization -> You can set the layout of the barrier blocks to anything you want while keeping in mind problems 2. and 3.

# WARNING: use at your own risk, read above and make sure you understand before using this option.
per-player-generators-barrier-layouts:
great_oak_tree: great_oak_tree_silhouette   # generator_name: structure_name
wheat: none   # Use none, and no barrier blocks will be placed. (No barriers are placed for non-solid blocks by default)

- Fixed decorative blocks check per-player generators.

Click to expand...

- Non solid blocks no longer have a barrier block inside in per-player generators.

Click to expand...