Stop combat logging and kill farming
Block escape commands in combat, refuse farmed kills and protect 1v1 duels from third parties.
Four systems keep kills meaningful: the combat tag, the command whitelist, anti-farmkill and the anti free-hit link. All work out of the box. The first three are in Settings; anti free-hit is a rule per arena.
Block escape commands in combat#
A player who takes a hit is tagged for 20 seconds. While tagged they cannot run commands such as /spawn, /hub, /home, /tpa or /rtp.
Open the combat settings
Run /ffaadmin, click Settings, then Combat.
Set the time and the list
Click Combat tag and type the seconds. Click Blocked commands to edit the list, one command name per entry, without the slash.
Shift + right-click a card puts it back to its default.
A tagged player sees a countdown above the hotbar. Anyone can hide it from /ffa settings, see Player settings.
Leaving the server while tagged counts as a death. It is recorded and announced, the player loses their streak, and the last player who hit them gets the kill if still fighting in the arena. Their items drop if the arena drops items on death. There is no setting to turn this off.
Allow only some commands in the arena#
The whitelist works whether or not the player is tagged. In Settings, Combat, switch on Command filter and edit Allowed commands. Any other command is refused inside an arena. The default list is msg, message, tell, w, whisper, reply, r, respond, ffa and ffaadmin. Allowing msg also allows essentials:msg. Staff with exyliaffa.bypass.blocked-commands skip the filter.
Stop kill farming#
Anti-farmkill refuses to count a kill that was clearly handed over: the same victim over and over, or two players on the same IP address.
In Settings, click Fair play, then Farm protection for the master switch, Repeat victim and Same IP. By default more than 3 kills on the same victim within 120 seconds stop counting.
Only the killer's kill counter, and with it their KDR and kills per minute. The victim's death is still recorded, the killer's streak still advances, and kill commands still run. If you pay money per kill, anti-farmkill does not block it.
Protect 1v1 duels (anti free-hit)#
Free-hitting is a third player arriving at the end of a duel to take the kill. This links two players who have traded hits and protects the duel. It is off by default and set per arena.
Open the combat rules
Run /ffaadmin, click Arenas, left-click your arena, click Rules, then Combat.
Turn it on
Click Anti free-hit. Set Hits to link (default 3), the hits two players trade before they are linked.
Choose how strict
Click Isolate linked players to stop third parties from damaging linked players. On, the arena becomes a run of clean duels. Off, the link only informs and the chaos stays.
The link ends when 8 seconds pass with neither player hitting the other. While it lasts the action bar shows the opponent's name, hearts, ping and time left, and the opponent glows if the player keeps Glow on linked player on.
Technical details
config.yml:
| Key | Default |
|---|---|
combat.tag-duration | 20.0 seconds, decimals accepted |
combat.blocked-commands | spawn, hub, lobby, warp, home, tpa, tpaccept, tpyes, rtp, back |
command-whitelist.enabled | true |
command-whitelist.commands | msg, message, tell, w, whisper, reply, r, respond, ffa, ffaadmin |
anti-farmkill.enabled | true |
anti-farmkill.same-player-enabled | true |
anti-farmkill.same-player-max-kills | 3 |
anti-farmkill.same-player-window-seconds | 120 |
anti-farmkill.same-ip-enabled | true |
anti-freehit.hit-reset-window-seconds | 8 (file only, no menu card) |
Arena rules: antiFreeHit (false), antiFreeHitHitsToLink (3), antiFreeHitIsolateLinkedPlayers (false). Texts in lang/<code>/messages.yml: combat.combat-actionbar (tokens %time_precise%, %time%) and anti-freehit.linked-actionbar (%linked_name%, %linked_hearts%, %linked_ping%, %time_precise%). The glow is sent by packets (packetevents), uses no teams and only the linked player sees it.
Something missing on this page? Tell us on Discord