EcoArmor 2026.40

- Added a placeholder that represents the value passed by the trigger (e.g. the amount of damage dealt; see here). It can be referenced with %trigger_value%, %triggervalue%, %trigger%, %value%, %tv%, %v%, and %t%, depending on what level of shorthand you prefer.

- Added chains.yml, a dedicated area to specify effect chains to be referenced with the run_chain effect

- Added onMaxHealth filter

- Fixed is_night condition not working

- API: Added Iterable<ConfiguredCondition>#isMet(Player) as shorthand for using .all { it.isMet(Player) }

- API: Added TriggerGroups (e.g. static_<interval>, custom_<id>) so you can programatically generate triggers with a common prefix

- Fixed load order bug

- Added has_item condition; like wearing_<armor piece>, except it just requires any item to be in the players inventory

- Updated EcoEnchants API to 9.x.x (Users using 8.x.x will not have the integration loaded)

- Moved configs to individual .yml files - existing configs will not break, but read the announcement at discord.gg/ZcwpSsE (#news channel)

- (API) Added HolderProvideEvent, with the ability to modify the list of holders that will be provided to the player

- Added shuffle_hotbar effect

- Fixed two errors with traceback and brew (Thanks OfTeN!)

- Another urgent hotfix

- Another urgent hotfix

- Hotfix for traceback error / plugin not loading

- Fixed mob_coins_multiplier effect

- Added elytra_boost_save_chance; chance to not consume a firework when boosting with an elytra

- Fixed damage_nearby_entities effect for base spigot users

- Added brew trigger

- Added smelt trigger

- API: Added ConfiguredCondition#runNotMetEffects

- Fixed warning with new truly-inline chain syntax

- Cleaned up contexts for config violations; instead of having a million brackets (i.e. 'Error for effect <id>, (inline chain) (args) (Effect send_message) (args)), it will be separated by an arrow (->) to be easier to read.

- Added truly-inline chains; a shorthand syntax to run multiple effects on a trigger without ever needing to worry about the run_chain_inline effect, or even what a chain is. Instead of specifying an effect ID, you specify a list of effects to be ran on the trigger. All chain features are supported (it is an inline chain, it's just simpler). Read more about it here: https://plugins.auxilor.io/effects/configuring-an-effect#shorthand-inline-chains

- Added not-met-effects to effect-specific conditions; a set of effects to be run when the trigger is activated but the conditions aren't met for that specific effect. Read more here: https://plugins.auxilor.io/effects/configuring-a-condition