EntitiesDispositionEvent

Moves entities without a walk: each entry is an EntityDisposition - which entity, the cell it now stands on and the direction it now faces. Nothing animates a path; the entity is simply put there.

WHAT TO DO WHEN YOU RECEIVE IT

1. For every entry, look the entity up by EntityDisposition.entity_id and OVERWRITE its cell (EntityDisposition.cell_id) and its direction (EntityDisposition.direction). 2. LEAVE EVERY OTHER ENTITY ALONE. It is not a snapshot: entities missing from the list keep their position. 3. SEND NOTHING BACK. No handler of this message builds a request.

WHEN IT ARRIVES. In the client it is handled by the fight services (the placement cells and the fighters' on-map positions). In a capture it arrived right after AttackMonsterRequest: first with the attacker alone, then four more times with the attacker and one monster each, while the fight was being set up. Expect it whenever a fighter is (re)placed during the placement phase, yours or someone else's - including after your own FightPlacementPositionRequest.

NOT THE PLACEMENT SWAP. The fight placement swap announcement carries the same kind of list but belongs to the fight-preparation protocol file; this one is the context-level message.

PADDING. Builds pad this message with an unread int32, or with a SECOND list of the same record type (3.6.10.10) that the client never reads. Read the recovered list only.