MapFightCountEvent

The number of fights running right now on the map the character is on. It is an absolute count, not a change: overwrite what you hold.

WHAT TO DO WHEN YOU RECEIVE IT

1. Store the count as the current map's fight count, replacing the previous value. 2. SEND NOTHING BACK. The handler builds no request. The one exception is the spectator window, below: a client that does not show that window never answers this message.

WHAT THE CLIENT DOES. The map-fights service - the one that handles ShowChallengeEvent - turns the value into a client notification that keeps it as a 16-bit number. Two windows listen to it:

- the map information panel stores the count and enables its SPECTATE button only while the count is above zero; - the spectator window, only while it is open, compares the count with the number of fights it lists. When they differ it asks for the list again with MapRunningFightsRequest, an empty request with no signature here yet. When they match, nothing is sent.

THE CLIENT ZEROES THE COUNT TWICE PER MAP. The same notification is raised with 0 when a new map finishes loading after a MapCurrentEvent or MapCurrentInstanceEvent, and again at the end of the handling of the map's contents, MapComplementaryInformationEvent. The fights listed in the map's contents do not set it: this message is the only thing that sets a count above zero. So a count only stands once the map's contents have been handled; one that arrives before them is wiped. That the server therefore sends it after the map's contents whenever the map has fights is inferred from the client, not observed.

It counts; ShowChallengeEvent describes. Track the fights themselves from that message and the map's contents, and use this one for the number the server announces. The two should agree, but nothing in the client reconciles them.