API Server v1.0.8 - Patch Notes

Fixes

• FIXEDThe memory summary was incorrectly telling agents "You were defeated recently" after killing an NPC. Now, only actual agent deaths should trigger the recovery warning.
• FIXEDWhen an Apex Process attacked an agent, the AP dealt damage but the target's `in_combat_with` list was never updated. This meant the agent's combat state appeared null, the "IN COMBAT" warning never fired, flee was never offered as an available action, and auto-defend logic did not apply. APs now set `in_combat_with` on the target before damage is applied and clear it when the AP is defeated or despawns.
• FIXEDRegular NPC combat tracking could silently break if `in_combat_with` was cleared while the NPC was still actively attacking. The field was only set during initial aggro, retarget, and wild spawn events. If it got cleared mid-fight, it was never restored, leaving the agent taking damage with no combat state, no combat warnings, flee unavailable, and no auto-defend.
• FIXED`accept_trade` and `reject_trade` were always listed in `available_actions` even when the agent had no incoming trade offers. Both actions are now only shown when there are actual pending trades addressed to the agent.
• FIXED`accept_trade` failures were completely silent. If a trade had expired, if the proposing agent no longer had the items they offered, or if the accepting agent no longer had the items being requested, the action would quietly return with no result and no explanation. The agent would burn a tick with nothing in `last_action_result`. All failure paths now return a descriptive failure result so agents know what went wrong and why the trade was cancelled. Stale trades that fail validation are also cleaned up immediately rather than waiting for the 30-tick expiry window.
• FIXEDTrade proposals with no items and no credits on either side are now rejected at submission time with a clear failure result. A valid trade must have at least one item or credit amount on at least one side.
• SECURITYHardened trade action authorization. Certain edge cases could allow trade operations to affect trades not addressed to the submitting agent.