
Combat State
Shared combat-state tracker for Minecraft mods and modpacks.
About this Mod
Combat State
Track when a player is still in combat, even after a mob switches targets.
Combat State is a small shared dependency for combat-aware Minecraft mods and modpacks. It gives other mods a clear server-side answer to: “is this player still in combat?”
Combat rules
A player enters combat with a mob when that mob targets the player.
The player stays in combat with that mob if the mob switches target during the fight. Target switching alone does not end combat.
The player leaves combat with that mob when either:
- the mob has no target anymore, or
- the mob is not currently targeting that player and the player is more than 64 blocks away.
What it provides
- Server-side combat tracking for players.
- A small API for dependent mods.
- Configurable disengage distance.
- Optional yellow indicator for mobs that still keep you in combat but are not currently targeting you.
- Aggro Indicator compatibility: Aggro Indicator can keep showing the red current-target icon, while Combat State adds the yellow combat-memory icon.
API
Use CombatStateApi on the server:
CombatStateApi.isInCombat(player);
CombatStateApi.isActivelyTargeted(player);
CombatStateApi.getCombatMobIds(player);
Configuration
Config file:
config/combat_state-common.toml
Default values:
[combat]
disengageDistance = 64
syncIntervalTicks = 20
[client]
renderYellowIndicator = true
Requirements
- Minecraft 1.21.1
- NeoForge
Optional integration:
- Aggro Indicator
Source and issues
Available Versions
How to Install Combat State on Your Server
Order Server
Order a Minecraft Java server with at least 3 GB RAM (4 GB recommended).
Set neoforge Loader
In the panel under "Egg", select the neoforge loader and matching Minecraft version (1.21.1).
Install Mod
Open the mod browser in the dashboard and search for "Combat State". Click "Install" – done! Alternatively, upload the .jar via SFTP to the /mods folder.
Compatibility
Mod Loaders
Minecraft Versions
1.21.1
Server-side
✓ RequiredRecommended RAM
4 GB(min. 3 GB)Frequently Asked Questions
Combat State server crashes on startup – what to do?
Most common cause: wrong neoforge version or insufficient RAM. Check the server log (latest.log) for "OutOfMemoryError" or "Mixin" errors. With Mado Hosting: ensure at least 3 GB RAM is allocated and the loader matches the mod version (1.21.1). You can switch loaders with one click in the panel.
Is Combat State compatible with neoforge?
Combat State officially supports neoforge for Minecraft 1.21.1. The Mado dashboard automatically detects incompatible loader combinations.
Server lagging with Combat State – how to optimize performance?
Recommended RAM: 4 GB (per 8 players). Use /spark profiler to check if Combat State consumes the most tick time. Common fixes: reduce server view-distance to 8-10, install "performant" or "starlight" as supplementary mods on Forge. With Mado Hosting, your server runs on NVMe SSDs with dedicated CPU cores for minimal latency.
Similar Mods
Rent Modded Server
Install Combat State with just one click on your server.