Minecraft plugin CombatLogX

🔌 About the plugin CombatLogX

CombatLogX — is a Minecraft plugin for servers that provides modular combat tagging and anti‑combat‑logging behavior. CombatLogX tags players into combat, applies configurable punishments for logging out during combat, and offers many expansions so the core remains lightweight. CombatLogX is open source and maintained with build artifacts on Jenkins and source code on GitHub.

🎯 Purpose

CombatLogX solves unfair PvP disconnects by ensuring players who leave during combat are punished (for example: death, commands, or other configured penalties). The plugin is focused on PvP fairness, modularity, and extensibility through expansions. CombatLogX supports global or permission‑based combat timers and links damage sources such as pets, projectiles and TNT to tag events. ()

⚙ Main features

• Modular combat tagging core with many optional expansions (action bar, boss bar, force field, damage taggers, logger, loot protection, etc.). ()
• Configurable punishments for players who disconnect while tagged (including kill on logout and command execution).
• Permission‑based bypasses and command nodes for granular control. ()
• Expansion system keeps main jar lightweight; install expansions into /plugins/CombatLogX/expansions.
• Force field visual effect (requires ProtocolLib) and region expansions — visual only; not a secure entry prevention by itself. ()

🧩 Who should use CombatLogX

• Servers with active PvP (Survival, Factions, PvP arenas).
• Admins who need configurable anti‑combat‑logging behavior without bundling all features in the core.
• Teams that prefer a modular plugin architecture where features can be added via expansions.

🏗 Usage examples

• Kill or punish players who disconnect within X seconds after receiving PvP damage.
• Show an action bar or boss bar countdown while players are combat‑tagged.
• Use Loot Protection expansion to prevent item theft after logout during combat. ()

⚡ Notable characteristics

• Developed and published on Spigot with source on GitHub (author: SirBlobman). Recommended Minecraft versions are listed on the resource page. ()
• Uses expansions to add optional functionality so the main CombatLogX jar remains focused on tagging and punishment. ()

⌨️ Commands

All listed commands are confirmed in the official documentation. For command syntax and aliases see the documentation. ()

🔐 Permissions

Note: the official documentation lists the permission nodes but does not explicitly document default (true/op/false) values for each node; do not assume defaults without checking your plugin config or testing on your server. ()

⚙ Installation

📥 Installation steps (confirmed)

1. Download the CombatLogX.zip from the Spigot resource or Jenkins builds.
2. Stop the server (use your panel or stop in console).
3. Upload CombatLogX.jar and BlueSlimeCore.jar to /plugins/.
4. Extract or upload expansion jars to /plugins/CombatLogX/expansions/.
5. Restart the server.
6. Edit configuration files in /plugins/CombatLogX/ and reload with /clx reload or restart. ()

📦 Dependencies

• BlueSlimeCore (required). ()
• ProtocolLib — required by the Force Field expansion (for fake block packets). Only enable force field if your server can handle the extra client packets. ()

🧾 Configuration

• CombatLogX generates its configuration and expansions folder under /plugins/CombatLogX/ after first run.
• The plugin relies on expansion jars and separate config files; many behaviors (punishments, timers, expansions enabled) are set in those files.
• Use /clx reload to reload configuration files (or restart the server). ()

🗄 Database support

• Official documentation does not list built‑in MySQL/SQLite core requirements for CombatLogX itself in the main resource page; some expansions or logging options may write to files. Check expansion configs for persistence options. (Information about database support not explicitly documented on the resource page). ()

🧠 Additional information

Known conflicts & limitations

• The Force Field is a visual client‑side effect and should not be relied upon as a secure region lock — players can ignore fake block packets. Performance may degrade if enabled on low‑spec servers or with many players. ()
• Some expansions require other plugins (e.g., ProtocolLib for force field) — enabling expansions without dependencies may break that expansion. ()
• User reports and reviews note some edge cases with actionbar/bossbar behavior on certain MC versions; test expansions on your target Minecraft version. ()

FAQ

Q: Which Minecraft versions are supported?
A: The Spigot resource lists recommended server versions (example set includes 1.19.4, 1.20.6, 1.21.7); other versions may work but are not officially tested — verify on the resource page and test on a staging server before production. ()

Q: Does CombatLogX collect anonymous metrics?
A: CombatLogX is listed on bStats, indicating it can report plugin metrics via bStats. Check your plugin config to opt out if desired. ()

Q: Is there official support or issue tracker?
A: The project is open source on GitHub; bug reports and issues should be filed on the repository. Jenkins developer builds are available for testing. ()

Q: Can I remove expansions later?
A: Yes — remove expansion jar(s) from /plugins/CombatLogX/expansions/ and reload or restart. ()

Support integrations

• GitHub repository and Jenkins for developer builds are available (see resource page). ()
• Discord support is not listed on the official Spigot resource; if you need community support prefer GitHub issues or the Spigot discussion thread. (Discord link not present in official sources). ()

When using CombatLogX, follow the installation guide precisely (CombatLogX uses expansions and BlueSlimeCore) and test expansions on a staging server before applying to production. CombatLogX is a mature, modular combat‑tagging solution with many optional expansions; consult the documentation for expansion‑specific configs. ()