FightTeamUpdateEvent

Updates one team of one fight. fight_id says which fight; team is the team record: which side of the fight it is (challengers or defenders), its leader, its alignment side, its team type and its members.

WHAT TO DO WHEN YOU RECEIVE IT

1. Look the fight up under fight_id among the fights you know on the current map (from ShowChallengeEvent and MapComplementaryInformationEvent). If you do not know it, ignore the message: the client does nothing either. 2. In that fight, take the team the record names (its side). 3. ADD the record's members that the team does not have yet, keyed by member id. Nobody is removed here: a member leaving arrives in its own message, FightTeamRemoveMemberEvent. Do not replace the team. 4. Send nothing back.

WHO ELSE LISTENS. Besides the map's fight list, the fight preparation side reads the same message: one handler keeps the team's leader id, another walks its members.

WHEN IT ARRIVES. In one capture the character attacked a monster group (AttackMonsterRequest) and about 70 ms later two of these arrived back to back, both for the new fight (3089), before the fight context started:

- the character's team: led by the character, the character as its only member; - the monster team: led by -20002 - the id of the monster group that was attacked - with an empty member list.

It also arrives while you stand on a map where other players fight, whenever a team changes.

A MONSTER TEAM IS LED BY ITS GROUP ID, which is negative. It is not a fighter id: the monsters themselves get their own fighter ids (see FightFighterShowEvent).