- summary: Destroys a character. This is irreversible and there is no further confirmation exchange.
- area: Game.Character
- confidence: 0.80
Destroys a character. This is irreversible and there is no further confirmation exchange.
- Kind request
- Area Game.Character
- Named by beta, gamemapping
STEP 3 OF 3, AND THE DESTRUCTIVE ONE. THE CHARACTER IS GONE. There is no undo, no grace period, and no second confirmation on the wire - the moment this is sent the decision is made.
If you are writing automation, the honest answer is that THIS MESSAGE HAS NO LEGITIMATE AUTOMATED USE. Deleting a character is a decision a person makes once; put it behind a human, not behind a script.
secret_answer_hash IS NEVER THE PLAINTEXT ANSWER. The client sends the
lowercase hex MD5 of the UTF-8 bytes of:
<character_id>~<secret_answer>
with a literal tilde between them. The separator, the digest and the hex casing were all read out of the client rather than assumed. Send the plaintext and it will not match; hash without the id prefix and it will not match either.
Whether the hash is required at all comes from
CharacterDeletionPrepareEvent.need_secret_answer. Read that first.
Two builds declare a second int64 beside character_id; the named one is the
one the hashing writer actually stores.
When you may send it
- Requires
authenticatedobserved
Related messages
- Answers
CharacterDeletionPrepareEvent - Reply not yet recovered: the character list is re-sent afterwards; the deletion's own acknowledgement has no signature here yet.
Sequence
Step character_deletion.3 inferred — of 3 steps; the flow is a fixed ask / terms / confirm exchange
If you get it wrong
- the hash must be MD5 of <character_id>~<secret_answer>; sending the plaintext answer, or hashing without the id prefix, produces a value that cannot match inferred
Fields
| # | Field | Type | Meaning | You set it |
|---|---|---|---|---|
| 1 | character_id | int64 | The character to destroy. (character id) Also the prefix of the hashed string - the two must agree. | required |
| 3 | secret_answer_hash | string | Lowercase hex MD5 of the UTF-8 string <character_id>~<secret_answer>. NEVER the plaintext answer. The tilde separator, the digest algorithm and the hex casing were all read out of the client. | required when the prepare event asked for it |
Recovered with score 225, confidence 0.80, margin 225 over the runner-up. A margin close to the score means nothing else came near; a thin margin means a decoy nearly won. Members recovered: 2 of 3.
Aucun avis à afficher.