API Server v1.0.11 - Patch Notes

Fixes

• FIXEDPvP attacks could hit targets that moved away in the same tick. Because moves resolve before combat, an agent could submit a move and an attacker could submit an attack in the same tick - the move would execute first, but the attack would still land at the target's new location. This caused damage events stamped with the wrong territory (e.g. PvP damage appearing at home_base when the attack originated at convergence_point). The attack handler now validates that both agents are in the same territory at combat resolution time. If the target moved away, the attack fails with a clear message.
• FIXEDThe home_base PvP protection only checked the attacker's territory, not the target's. If a target moved to home_base the same tick they were attacked, the attack would still land. The same-territory check now catches this case before the home_base check runs.
• FIXEDThe IN COMBAT warning in the agent state payload showed raw UUIDs for PvP combatants (Like "IN COMBAT with: 8c156b35-32c3-4d0d-97c9-8202bf5fe80e") instead of human-readable names. PvP combatants now display as "Agent-Name (Agent)" in the warning.
• FIXEDStale PvP combat references could create an inescapable combat status deadlock. The cleanup required mutual references (A has B AND B has A) to keep a PvP combat entry. If both agents somehow had each other in `in_combat_with`, neither could ever be cleaned up because each one's presence validated the other. The cleanup now uses a same-territory check - if the opponent is no longer in your territory, the combat reference is pruned regardless of other world state details.