Simple Combat Log

Refactor — no functional changes

This release is a pure code refactor. Gameplay behaviour is identical to the previous version.

Package structure

Packages have been renamed to follow Java conventions (lowercase):

What changed

CombatManager (new: combat package)

• Now fully owns combatTimers, activeTimers and bossBars maps
• Listeners no longer touch state directly — all changes go through the public API

PluginConfig (new: config package)

• Centralises every config.getString / getBoolean / getInt call
• Single instance passed to all listeners on startup

Listener split

• CombatTagListener — damage, projectile, explosion and enderpearl tagging
• CombatRestrictionListener — elytra, teleport, command block, mending, riptide
• CombatZoneListener — proximity tagging on join
• CombatLogoutListener — disconnect handling
• AntiKillAbuse — kill-farming detection
• WorldGuardListener — region entry guard (registered only when WorldGuard is present)

CombatLog (main class)

• Reduced to wiring only: config → manager → listeners
• registerListeners() is the single place to see which listeners are active

Migration

No config changes. No permission changes. No command changes. Simply replace the old jar with the new one and restart.

Fixed an issue with the WorldGuard integration where the plugin checked an unused local flag instead of the actual WorldGuardHook status. As a result, the region entry restriction during combat now works correctly.

Additionally, blocked commands are now case-insensitive (/TPA, /Tpa, /tpa are treated the same), making the command restriction system more reliable.

This update introduces a cleaner and fully restructured configuration.

All settings are now logically grouped (timer, restrictions, punishment, triggers, etc.), making the plugin easier to configure and extend. The Anti-Kill-Abuse system has also been adapted to the new structure.

⚠️ Old configs are not compatible. Please replace your existing config.

New Configuration

combat-log:
  timer:
    duration-seconds: 15
    display: actionbar

  restrictions:
    elytra:
      disabled-in-combat: true
    teleporting:
      disabled-in-combat: false
    mending:
      disabled-in-combat: true
    riptide:
      stop: false
      cooldown: 10000
    explosions:
      set-combat-on-explosion: true

  punishment:
    damage: 5.0
    kill-on-logout: false

  triggers:
    enderpearl:
      set-combat-on-land: true
      only-if-already-in-combat: false

  ignored-worlds:
    - "ffa"

  blocked-commands:
    - "tpa"

  combat-zone:
    enabled: true
    radius: 10

  messages:
    combat-log: "&c{player} has combat logged!"
    elytra-use-denied: "&dYou can't use elytra in combat"
    teleporting-denied: "&dYou can't teleport in combat"
    blocked-command: "&cYou can't use this command in combat"
    region-entry-denied: "&cYou can't enter this region in combat"

    timer:
      actionbar: "&c{timeLeft}/{maxTime}"
      bossbar-title: "&cIn Combat: {timeLeft}s"

anti-kill-abuse:
  enabled: true
  limits:
    max-kills: 5
    remove-kill-after-seconds: 60
  punish-commands:
    - "kick {killer} Kill-Abuse detected!"
    - "ban {killer}"

Changelog

Added

• New configuration options to control combat logging when an Ender Pearl lands.
• Players can now be set into combat when landing an Ender Pearl.
• Option to choose whether this should always happen or only if the player is already in combat.

Config

combat-log:
  enderpearl:
    set-combat-on-land: true
    only-if-already-in-combat: false

Fixed a bug that the plugin coudn't start without worldguard