- summary: How many challenges the current fight will have; the client resets its challenge list to that many pending entries.
- area: Game.Challenge
How many challenges the current fight will have; the client resets its challenge list to that many pending entries.
Kind event · Area Game.Challenge
The number of challenges the fight will have, before they are known.
WHAT TO DO WHEN YOU RECEIVE IT
1. Clear your challenge list and prepare ChallengeNumberEvent.challenge_number
pending slots. The client does exactly that: it clears its list and fills it with
that many placeholder entries, then refreshes the challenge display.
2. Wait for ChallengeListEvent (or ChallengeProposalEvent when the team
chooses) to fill the slots.
3. SEND NOTHING BACK.
PADDING. Builds add unread int32s or a nested record; the client reads one int32.
When you may send it
- Requires
context_readyinferred
Related messages
- Unsolicited - nothing you send causes this the server announces the number of challenges when a fight's challenges are being prepared
Fields
| # | Field | Type | Meaning | You set it |
|---|---|---|---|---|
| 1 | challenge_number | int32 | Number of challenges the fight will have. (count) | never |