Blocking

What players in combat can’t do. Combat Log blocks commands and teleports in general, so it works with any home, warp, spawn or teleport plugin.

Commands

These are under command-blocking: in config.yml.

yaml
command-blocking:
  mode: blacklist
  commands:
    - spawn
    - home
    - tpa
    - rtp
    - warp
    - back
SettingMeaning
mode: blacklistThe listed commands are blocked in combat. Everything else works.
mode: whitelistOnly the listed commands work in combat. Everything else is blocked.
commands:Command names, without the slash.
  • A listed command is blocked with every alias and every subcommand, and with its plugin prefix, for example /essentials:home.
  • /combat always works.
  • Proxy commands like /server and /hub are handled by Velocity, so they can’t be blocked here. Switching server in combat still counts as logging out.
  • Players see command-blocked from messages.yml.

Teleports

block-teleports: true cancels teleports from commands and plugins while a player is in combat. Players see teleport-blocked, at most once every 2 seconds. Ender pearls and chorus fruit aren’t affected. Use item cooldowns for those. Set block-teleports: false to allow teleports.

Teleports into a safe zone are always cancelled in combat, whatever caused them. See Safe zones.

Safe zones

Players in combat can’t enter safe zones and see a wall at their edge. Everything about them is on the Safe zones page.

Disabled worlds

Combat is off in every world listed in disabled-worlds: []. Nobody is tagged there. For example:

yaml
disabled-worlds:
  - lobby

Who is never tagged

  • Players with combatlog.bypass. Nobody has it by default, but a * permission includes it.
  • Players in creative or spectator.
  • Vanished players, with any vanish plugin that marks players as vanished.
  • NPCs from plugins like Citizens. Killing one doesn’t count in the stats either.

These players can’t tag anyone else either.