Talismans ⭕ Create Custom Talismans ✅ Powerful Passive Effects ✨ Talisman Bag, Levels

MC Plugin Talismans ⭕ Create Custom Talismans ✅ Powerful Passive Effects ✨ Talisman Bag, Levels 6.56.1
Powerful and intuitive passive effects for your server.

- Added run-type to chains to cycle through effects rather than run them all together
- Added helix, double_helix, twirl, and circle particle animations
- Tweaked particle animation options for more flexibility
- Fixed static trigger console spam for users on base spigot
- Added particle animation system and the particle_animation effect to use it!
At the moment there are two effects: trace and ground_spiral, however many more will be added in the future!
Read the wiki page to learn more about how to use them: https://plugins.auxilor.io/effects/all-effects/particle_animation
- Added particle_line effect to draw a line of particles between you and the target location
- Fixed particle offsets / movement with spawn_particle effect
- Added support for chain arguments

These allow you to pass parameters to your chains, which makes effect chains far, far more useful and more reusable - your logic can get a lot more complex with this!

In any chain effect (run_chain, run_chain_inline), there is now an extra option you can put under args:

chain_args:
<name>: <value>
<name 2>: <value 2>

You can add as many arguments as you like. You use these values in chains just like other placeholders, with %<name>%, for example if you had an argument called strength, you would reference it with %strength% in your chain. Chain arguments support placeholders, too - just like anything else.

This is huge, and if you want to make something extremely powerful with effects, this will make it even easier and quicker with less repetition!
- Optimized not-met-lines with a caffeine cache
- Added placeholder_contains condition
- Added set_velocity effect
- Fixed any_of condition showing the wrong parameter name when provided with an invalid config
- Fixed infinitely growing whitespace
- Fixed riding_entity condition not using entity lookup strings and optimized the isMet function via CompileData
- Added not_ as a prefix for filters to invert them, and added the documentation for inverse filters; using ! as a prefix will still work, however this isn't recommended as yaml treats ! as a special character
Top Bottom