- summary: One member left one team of one fight: the fight, the team and the member's id.
- area: Game.Fight.Preparation
One member left one team of one fight: the fight, the team and the member's id.
Kind event · Area Game.Fight.Preparation
The removal counterpart of FightTeamUpdateEvent: that one only ever ADDS members,
this one takes one member out.
WHAT TO DO WHEN YOU RECEIVE IT
1. Find the fight under FightTeamRemoveMemberEvent.fight_id among the fights you
know (the map's fights from ShowChallengeEvent and
MapComplementaryInformationEvent, or the fight you are preparing).
2. In the team FightTeamRemoveMemberEvent.team names, REMOVE the member
FightTeamRemoveMemberEvent.character_id. Leave every other member alone.
3. SEND NOTHING BACK. No handler of this message builds a request.
WHAT THE CLIENT DOES. Two services react: - the map's entity service takes the three values together and drops the member from that fight's team on the map; - the fight-preparation service removes the id from its own list of team members.
IF YOU ONLY HANDLE FightTeamUpdateEvent, YOUR TEAMS ONLY GROW. Members who leave a
fight during placement stay in your model until the fight ends.
PADDING. Builds may add unread members beside the three; read the recovered ones only.
When you may send it
- Requires
context_readyinferred
Related messages
- Unsolicited - nothing you send causes this the server pushes it when a member leaves a team, whoever caused it; no request asks for it
Fields
| # | Field | Type | Meaning | You set it |
|---|---|---|---|---|
| 1 | fight_id | int32 | The fight whose team lost a member. (fight id) | never |
| 2 | character_id | int64 | The member that left the team. (entity id) | never |
| 3 | team | Team | Which team of that fight the member left (challengers, defenders or spectators). The enum type (beta's Team) has no signature yet, so its values stay obfuscated. | never |