Combat
Where the combat tag lives now: ExyliaCombat owns tagging, restrictions, logout NPCs, the safe-zone barrier and vanilla cooldowns; ExyliaSpecials only reads the tag, and moves old settings over.
ExyliaSpecials needs to know who is in combat — items such as Flight refuse to work then, cooldowns can be
longer with combat-seconds, and duels tag their fighters. It no longer tags anyone itself: combat tagging, the
restrictions while tagged, logout NPCs, the safe-zone barrier and vanilla item cooldowns live in ExyliaCombat.
Who tags
ExyliaSpecials asks ExyliaLib's combat facade, so it works with whichever of these is installed:
| Plugin | |
|---|---|
| ExyliaCombat | The tag, its restrictions, logout NPCs, the barrier and vanilla cooldowns. |
| DeluxeCombat or PvPManager | Their own tag and settings. |
| None | Nobody is ever in combat: combat-seconds and the in-combat condition never apply. |
Duels still tag both fighters for the fight plus 10 seconds, through the same facade.
Moving from an older version
Older versions had the combat tag built in, under combat, vanilla-cooldowns and actionbar in config.yml.
On the first start of this version those settings are copied, with language, into exyliacombat-export.yml in
the plugin folder, and ExyliaCombat imports them on its own first start. Install ExyliaCombat to keep them.
Gone with the move: /specialsadmin setcombat and removecombat, exyliaspecials.admin.combat,
exyliaspecials.combat.bypass, the combat messages and the combat.provider setting.
Placeholders
%exyliaspecials_in_combat% and %exyliaspecials_combat_time% still work, from whichever combat plugin is
installed. See Placeholders.
Something missing on this page? Tell us on Discord