- summary: Where the fight map really is: its map id, subarea and, for an ordinary map, its world coordinates.
- area: Game.Gamemap
Where the fight map really is: its map id, subarea and, for an ordinary map, its world coordinates.
Kind event · Area Game.Gamemap
Sent while a fight is being set up, so the client can show where the fight takes
place. A fight runs on its own map: the map id is that fight map's id, the same
value as MapCurrentEvent.map_id and the one to echo in
ContextReadyRequest.map_id.
USE THESE COORDINATES, NOT A LOOKUP. When FightMapInformationEvent.coordinates
is set, the client takes the map's world position from it instead of looking the
fight map up in its map data. A script that converts the map id itself shows the
wrong place.
Read FightMapInformationEvent.subarea_id for the subarea name and treat the
complement as optional: at most one of coordinates or anomaly information is set.
When you may send it
- Requires
context_readyobserved
Related messages
- Unsolicited - nothing you send causes this observed — the server sends it with the other fight-placement events
Fields
| # | Field | Type | Meaning | You set it |
|---|---|---|---|---|
| 3 | map_id | int64 | Id of the map the fight takes place on. (map id) Same value as MapCurrentEvent.map_id during the fight; echo it in ContextReadyRequest.map_id. | never |
| 5 | subarea_id | int32 | Subarea the fight map belongs to. (subarea id) Look it up in the subarea data for the area name. | never |
| 1 | coordinates | MapCoordinates | World coordinates to show for the fight map. Element type MapCoordinates. When set, it replaces the position the client would derive from the map id. | never |
| 4 | anomaly_information | MapComplementaryAnomalyInformation | Anomaly details when the fight map is an anomaly map. Same record as MapComplementaryInformationEvent.anomaly_information.Named from that type only: no dumped client reads it here, so it stays obfuscated on builds where that record is not recovered. | never |