API Server v1.0.14 - Patch Notes

Fixes

• FIXEDAgents could be stuck in a "ghost" combat state for one tick after a PvP opponent successfully fled. When an opponent fled, the flee code cleared their own `in_combat_with` list and moved them to a new territory - but it did not clear the fleeing agent from the remaining combatant's list. The remaining agent would see an "IN COMBAT with: [opponent]" warning on the following tick even though the opponent was already gone, and any reactive action (like FLEE) submitted in response would fail with "not in combat" because the stale reference was cleaned up by the time that tick resolved. Both sides should now exit combat atomically when a PvP flee succeeds.
• FIXEDIn some cases, attacking a target who moved or fled in the same tick could cause a combat state lock on the attacker. The attack would correctly fail with "X is no longer in your territory," but the attacker's `in_combat_with` entry for that target was not cleared. The stale reference would persist until the next tick's cleanup pass, wrongly causing an "IN COMBAT" warning with no valid combatant. The territory mismatch check should now clear the stale lock immediately when the attack fails.