NexaCombat
Stop combatloggers, control PvP rules, protect safezones, reward fair kills and give your staff full fight evidence - all from one GUI-driven combat suite.
Punish combatloggers
Kill, drop, corpse, NPC, grave or chest modes.
Control PvP rules
Safezones, item restrictions, command blocks and old-PvP tuning.
Reward real fights
Bounties, killstreaks, assists, points and anti-farm checks.
Give staff evidence
Fight recaps, timelines, heatmaps and risk flags.
Combat monitor
Live server state
PvP/PvE
Tag engine
8
Punishment modes
Recap
Timeline + evidence
GUI
Full in-game control
Production-ready feature set
No roadmap bait. The systems shown on this page are part of the production feature set.
GUI-driven configuration
Tune combat rules from in-game editors instead of living in YAML.
Built for PvP, SMP, Lifesteal and Survival
One combat layer for competitive and community server formats.
Works with plugin-heavy server stacks
Hooks for claims, teams, duels, shops, weapons and Nexa ecosystem plugins.
Storage: YAML, SQLite, MySQL, MariaDB
Run simple local files or a shared database-backed setup.
Developer API + PlaceholderAPI + LuckPerms contexts
Expose combat state, points, risk data and module events cleanly.
One suite for the problems that usually take five plugins.
Real servers do not only need a timer. They need clean combat enforcement, safezone behavior players cannot abuse, fair reward logic, staff evidence after messy fights and a setup your team can manage without editing config files all day.
Combatloggers stop being profitable
Choose how loot, deaths, corpses, NPCs, graves and chests behave when players leave mid-fight.
Safezones stay protected
Deny abuse at borders, push tagged players back and apply region-aware PvP rules.
Alt farming is easier to catch
Anti-farm checks score repeat kills, same-IP patterns, relations, proximity and one-sided damage.
PvP rules are not scattered
Restrictions, old-PvP tuning, rewards, safezones, storage and hooks are controlled in one stack.
Staff get fight evidence
Recaps, timelines, reports, heatmaps and risk flags give moderation teams something concrete to review.
Owners get GUI control
Admin menus expose the parts server owners actually change: restrictions, rewards, language, modules and storage.
Clean PvP rules from one control layer
NexaCombat gives server owners direct control over tagging, restrictions, safezones, old PvP feel, reward flow and fight visibility without stacking disconnected combat plugins.
Combatlog punishments
Restriction engine
Safezones and borders
Old PvP tuning
Rewards and bounties
Make logging out during combat cost something.
NexaCombat lets you decide exactly what happens when a player disconnects while tagged. Keep punishments strict for Lifesteal, controlled for SMP, or loot-focused for Survival PvP.
Punishment profiles
Loot control
NPC and corpse flow
Fair recovery rules
Combatlog outcome
Loot recovery chain
This is built for the common PvP complaint: players escaping consequences by closing the game. Your server decides whether that means death, dropped loot, a temporary NPC, a corpse, a grave or a protected chest.
Give staff the fight context chat logs miss.
Recaps, evidence reports, heatmaps, reputation and anti-farm scoring help moderators review messy PvP disputes with timelines, snapshots and clear risk signals.
Fight recap
Evidence export
Anti-farm scoring
Reputation and heatmaps
Evidence timeline
Fight #A8F3
00:00 - Combat started
PvP tag created, opponent and cause recorded.
00:07 - Crystal burst
Explosion source linked to placer and damage timeline.
00:13 - Combatlog
Punishment profile selected, evidence export attached.
Heatmap sample
Turn fair PvP into progression players care about.
NexaCombat rewards real fights while anti-farm checks protect your economy from repeated kills, alt abuse and coordinated farming.
Kill rewards
Bounties
Progression
Rankings and seasons
Admin GUI and in-game editors for the whole combat stack.
The admin surface mirrors the plugin modules server owners change most: status, debugging, language, restrictions, rewards, bounties, old PvP, knockback, storage, regions, rankings, saved drops and addons.
Settings editors
Restriction editors
Reward editors
World and region tools
Screenshot-ready in-game editor showcase
Placeholder panels are kept for the BuiltByBit listing until real GUI screenshots are added.
Admin control center
Buyers will see the central menu for status, reload actions, language, debug output, validation warnings and module editors.
Restriction editor
Buyers will see command, movement, item, inventory and protected-player rules grouped for fast PvP rule tuning.
Progression menus
Buyers will see rewards, points, bounties, assist shares, ranking outputs, seasons and data groups in one admin flow.
Combat feel editor
Buyers will see old-PvP behavior, shield/offhand rules, regeneration, weapon damage, projectiles and adaptive knockback controls.
Loot recovery views
Buyers will see corpse access, NPC loot, protected loot, saved drops, void restore and combatlog inventory recovery flows.
Staff evidence screens
Buyers will see recap timelines, report indexes, risk flags, combatlog attachments and particle replay views.
Storage and sync dashboards
Buyers will see storage backend controls, queued saves, migrations, heartbeats, active network combat locks and addon status.
Built for plugin-heavy PvP stacks
Hook groups are organized around the server problems they solve: land and team relations, practice bypasses, economy guards, visual states, custom weapons and local Nexa suite protection.
Claims and teams
Practice and duel states
Economy and local actions
Visual and state plugins
Mobs, items and weapons
Developer surface
A broader combat control layer, not only a tag timer.
DeluxeCombat, CombatLogX and MasterCombatPro are commonly used reference points in the combat-plugin market. NexaCombat focuses on one built-in combat layer for enforcement, staff evidence, rewards, local ecosystem guards and in-game editing.
| Feature | DeluxeCombat | CombatLogX | MasterCombatPro | NexaCombat | NexaCombat focus |
|---|---|---|---|---|---|
| PvP/PvE tag engine | ✓ | ✓ | ✓ | ✓ | Opponent, cause, groups, duration overrides, API events. |
| Combatlog punishments | ✓ | ✓ | ✓ | ✓ | NONE, CLEAR, DROP, KILL, NPC, CORPSE, GRAVE, CHEST. |
| Corpse/NPC loot flow | ~ | ~ | ~ | ✓ | Armorstand corpse, Citizens NPC, Sentinel, ghost recovery. |
| Safezone / region rules | ✓ | ~ | ✓ | ✓ | WG deny, pushback, fake border, per-region overrides. |
| Old PvP mechanics | ~ | - | ✓ | ✓ | Attack speed, regen, armor, sharpness, KB editor. |
| Bounty / rewards | ✓ | ~ | ~ | ✓ | Bounties, tax, glow, compass, assist share, points. |
| Ranking / seasons | ~ | - | ~ | ✓ | Stats, KD, Elo/MMR, tiers, hologram/sign/tablist output. |
| Fight recap / timeline | ~ | ~ | - | ✓ | Snapshots, usage, damage timeline, GUI, export, replay. |
| Evidence / risk flags | - | ~ | - | ✓ | Report IDs, exports, staff GUI, combatlog attachments. |
| Anti-farm intelligence | ~ | ~ | ~ | ✓ | Same-IP, ally, claim, proximity, one-sided, cleanup guard. |
| In-game editor | ~ | ~ | ~ | ✓ | Restrictions, rewards, bounty, UI, old PvP, storage, addons. |
| Storage backends | ~ | ~ | ~ | ✓ | YAML, SQLite, MySQL, MariaDB, migration, autosave queue. |
| Local Nexa guards | - | - | - | ✓ | NexaShop, Trade, Spawners, Vaults, Homes, Teams, TrainingBot. |
| Developer API | ~ | ✓ | ~ | ✓ | Services API, points service, PAPI, LuckPerms, module events. |
| Network locks | ~ | ~ | - | ✓ | Heartbeat files, stale cleanup, hub/server command blocking. |
Comparison is based on public product positioning and common documented feature surfaces. Symbols describe how each product is positioned around the listed area, not a guarantee that every setup has or lacks a specific behavior. Exact third-party behavior depends on version, expansions and server configuration.
Built-in platform features for serious server setups.
NexaCombat includes the backend pieces a production PvP stack needs: storage options, migration support, developer hooks, placeholders, LuckPerms contexts, module events and network combat locks.
Storage backends
Developer API
Network locks
Placeholders and contexts
Every major module included in the production build.
A fast scan of the main systems before the full feature map. Every module listed here is included in the current production feature set.
Tagging and attribution
Punishments and loot
Restrictions and protection
Safezone and old PvP
Economy and progression
Recaps and evidence
Anti-abuse intelligence
Admin and storage
Hook and API layer
All included systems, grouped cleanly.
The full feature surface is organized by what server owners actually configure: combat, loot, restrictions, PvP feel, progression, staff tools, admin menus, hooks and storage.
Runtime and configuration Core
Startup and control
Configuration files
Runtime safety
Combat engine and attribution Engine
Combat state
Attribution
Combat UI, health display and player feedback Player UI
Player feedback
UI modes
Combatlog, corpse, ghost and loot systems Loot
Punishment actions
Corpse and ghost recovery
Loot safety
Restrictions, protected players and dynamic item rules Protection
Shared rule model
Restrictions
Protection states
Dynamic item rules
Safezones, region rules and old PvP mechanics World Rules
Safezone controls
Old PvP mechanics
Economy, bounties, ranking, trophies and progression Progression
Stats and rewards
Bounty system
Trophies and returns
Fight recaps, evidence, replay, heatmap and reputation Staff Tools
Fight recaps
Evidence and replay
Analytics and reputation
In-game admin editor and menu system Admin GUI
Admin GUI core
Module editors
Ops dashboards
Addon, API, storage, network and integration layer Platform
Public API and storage
Addons, network and packets
Integration hooks
Local plugin ecosystem protection Nexa Suite
Local detection
Local action guards
Nexa ecosystem evidence
NexaCombat is not just another combatlog plugin.
It is a full combat control layer for serious PvP servers - built to stop combatlog abuse, enforce clean rules, reward fair fights, give staff evidence and keep plugin-heavy stacks under control.