
Simple Combat Log
The Simple-Combat-Log plugin prevents players from logging out during combat by setting a combat timer, disabling actions like Elytra use, and broadcasting a message if they leave the server mid-combat.
PlaceholderAPI Support, Admin Bypass & Combat Effects
Список изменений
New Features
PlaceholderAPI Integration CombatLog now supports PlaceholderAPI. Use these placeholders in any compatible plugin (scoreboards, TAB, HUDs, etc.):
%combatlog_in_combat%—true/false%combatlog_time_left%— remaining combat seconds%combatlog_opponent_name%— name of the current opponent%combatlog_opponent_health%— opponent's current HP (00.00format)
PlaceholderAPI is optional — the plugin loads cleanly without it.
Permission Bypass (combatlog.bypass)
Players or groups with the combatlog.bypass permission are fully exempt from CombatLog:
- Will not be tagged into combat
- Are not subject to any in-combat restrictions (elytra, teleport, commands, etc.)
- Disconnecting while in combat produces no broadcast and no punishment
- Default:
op
Potion Effects on Combat Tag You can now configure potion effects that are automatically applied when a player enters combat and removed when combat ends. Effects are only applied if the player does not already have that effect active.
Configure in config.yml under combat-log.tag-effects:
tag-effects:
- type: GLOWING
duration-seconds: 15
amplifier: 0
show-particles: false
Supports any valid Bukkit PotionEffectType. The list in the default config includes GLOWING as an example — remove or comment it out if you don't want any effects.
Improvements
CombatManagernow tracks the current opponent per player, enabling opponent-related placeholders to work correctlyPotionEffectTypelookup updated to useRegistry.EFFECTinstead of the deprecatedgetByName()method (Paper 1.20.3+)
Dependencies
- PlaceholderAPI: optional (
softdepend) - WorldGuard: optional (unchanged)
