- summary: The server naming the character about to be destroyed and stating whether a secret answer is required.
- area: Game.Character
The server naming the character about to be destroyed and stating whether a secret answer is required.
Kind event · Area Game.Character
STEP 2 OF 3. Read need_secret_answer before doing anything else: it decides
whether CharacterDeletionRequest must carry a hash, and it is per character.
character_id IS GONE FROM THIS MESSAGE. The reference build declared one and
NO dumped build carries it - the client already knows which character it asked
about. Do not expect it and do not treat its absence as a decode failure.
THE TWO STRINGS: CharacterDeletionPrepareEvent.name is the character's name (show it in your
confirmation) and CharacterDeletionPrepareEvent.secret_question the account's secret question (ask it
when need_secret_answer is set).
When you may send it
- Requires
authenticatedobserved
Related messages
- You must then send
CharacterDeletionRequestinferred — the flow is left open until the client either confirms or abandons it - Arrives after
PrepareCharacterDeletionRequest
Sequence
Step character_deletion.2 inferred — of 3 steps; the flow is a fixed ask / terms / confirm exchange
Fields
| # | Field | Type | Meaning | You set it |
|---|---|---|---|---|
| 1 | need_secret_answer | bool | Whether confirming the deletion must carry a hashed secret answer. Decided per character. Read it before building step 3. | never |
| 2 | name | string | The name of the character about to be deleted. The client stores it as CharacterSelection.m_askedToDeleteCharacterName and shows it in the confirmation popup. | never |
| 3 | secret_question | string | The account's secret question, to show when need_secret_answer is set. The client stores it as CharacterSelection.m_secretQuestion. | never |