Rewards & Commands
Warden Party can run console commands at different points during an encounter. This system is flexible enough for loot rewards, economy payouts, broadcasts, quest progress, or chained event logic.
Available Trigger Groups
Section titled “Available Trigger Groups”The commands section in config.yml supports these trigger groups:
spawnhitdievulnerable-againphantom-got-killedtop-players.most-damagetop-players.most-hits
Chance-Based Entries
Section titled “Chance-Based Entries”Each trigger can define numbered entries, and each entry can contain:
chancecommands
This allows weighted reward behavior without writing your own event handlers.
Placeholder Context
Section titled “Placeholder Context”Depending on the trigger, you can use placeholders such as:
%player%%health%%total_health%%damage%%hits%
Make sure you only use placeholders that make sense for the event you are configuring.
Common Use Cases
Section titled “Common Use Cases”Examples of what this system can handle:
- Give all participants a reward when the boss dies
- Reward the top damage player more heavily than everyone else
- Trigger broadcasts or titles when the boss becomes vulnerable again
- Grant small loot drops on successful hits
- Chain the encounter into another plugin or script system