Combat tag

How a player is tagged

With the built-in provider, a player is tagged whenever another player hurts them, and the attacker is tagged too. What counts as a hit:

• any damage whose culprit is a player: melee, arrows and other projectiles, and whatever else ExyliaLib traces back to a player;
• a splash potion with a harmful effect that reaches the player;
• a lingering cloud with a harmful effect a player left behind.

Both players are tagged for combat.duration (default 15s). A new hit renews the tag, but never shortens one already running. Hitting yourself tags nobody, and nobody is tagged when either player stands in a world listed in combat.blacklisted-worlds.

Hitting a logout NPC also tags the attacker, when the module's tag-attackers is on.

How the tag ends

With combat.notifications.on-tag and on-untag (both true), the player is told in chat when they enter and leave combat: combat.tagged and combat.untagged in messages.yml.

exyliacombat.bypass does not stop a player from being tagged. It frees them from every restriction and from the barrier, but they still show as in combat to other plugins and are still punished for logging out unless they also have exyliacombat.bypass.logout.

Providers

combat.provider in config.yml picks who decides the tag:

The console names the provider on every start, and %exyliacombat_provider% shows it. /combatadmin reload switches provider when combat.provider changed, or when AUTO would now pick another one.

What each provider covers:

The modules that refuse hits (PvP switch, newbie and respawn protection) and the ones that count kills work with any provider: they listen to the hits and deaths themselves.

/combat

/combat, also /ct, tells a player how long their tag still lasts and who they are fighting: timer.tagged in messages.yml, with %time% and %opponent% (timer.no-opponent when nobody is named), or timer.not-tagged. The names come from commands.combat-time in config.yml.

Showing the tag

Every mode below can be combined with the others. They follow the tag whichever provider decides it.

Action bar

The action-bar module draws the combat timer and the item cooldowns above the hotbar, through ExyliaLib's shared action bar (other plugins' segments sit after this one). Its text is in messages.yml under actionbar:

The combat timer is left out of the action bar when action-bar in modules/combat-display/config.yml is false.

Boss bar, titles and sounds

The combat-display module, modules/combat-display/config.yml. Text in lang/<language>/modules/combat-display/messages.yml, where %time% is the tag left and %opponent% the player last fought.

Nametags

The combat-nametag module is off by default. While a player is tagged, their name above the head changes for others, and goes back when the tag ends. Needs PacketEvents; without it the module warns once and does nothing.

The prefix ({error}⚔ ) and suffix (empty) live in lang/<language>/modules/combat-nametag/messages.yml.