FoCombatTag

FoCombatTag keeps PvP fights honest by tagging players after real combat, showing a clear countdown, and blocking the common escape routes: logout, commands, safe-zone entry, elytra use, and pearl spam. It is built for servers that want configurable PvP pressure without turning every fight rule into manual staff work.

Features

• Tag both players after valid player damage, including projectiles and configurable player-caused explosions.
• Show the remaining combat timer in chat and the actionbar so players know exactly when they are safe.
• Block combat-escape commands while still allowing configured chat, team, reply, and admin command patterns.
• Punish combat logging with optional death, broadcast messages, and console commands.
• Use optional WorldGuard checks to keep tagged players out of PvP-denied regions, with client-side border blocks and configurable pushback.
• Restrict elytra and ender pearl escapes when enabled, with /elytravault preserving stored elytras instead of deleting gear.
• Tune common settings from the in-game admin editor, including timer, command allowlist, WorldGuard border, logout handling, elytra rules, pearl cooldowns, and player explosion tagging.

Change Colours of the Combat Wall!

Dependencies

• WorldGuard - Optional; enables PvP-denied region checks, no-PvP border rendering, and region exclusions.
• PlaceholderAPI - Optional; enables the placeholders below.

Commands

• /focombattagadmin version|reload|editor|tag|untag|status - Check version, reload, edit settings, manually tag or untag players, and inspect active tags.
• /elytravault - Claim elytras stored while elytra restrictions are active.

Permissions

• focombattag.admin - Access to FoCombatTag admin tools.

Placeholders

Requires PlaceholderAPI.

• %focombattag_tagged% - Returns true or false.
• %focombattag_remaining% - Remaining tag time with s.
• %focombattag_remaining_raw% - Remaining tag time as a number.