- summary: The measurement of the file the server asked about, returned with the algorithm it asked for.
- area: Game.Client.Verification
- confidence: 0.99
The measurement of the file the server asked about, returned with the algorithm it asked for.
- Kind request
- Area Game.Client.Verification
- Named by beta, gamemapping
The answer to FileCheckEvent. It carries the measurement as a STRING - a
decimal byte count or a checksum, depending on which CheckType the challenge
selected - and the same check type echoed back.
COPY THE CHECK TYPE THROUGH UNCHANGED. The client does exactly that: the value from the event is written into the reply without transformation.
The current build declares a SECOND field of the same CheckType type that no
writer ever populates. It is a decoy; leave it at its default. The live one is
the field named here.
When you may send it
- Requires
authenticatedobserved
Related messages
- Answers
FileCheckEvent
Fields
| # | Field | Type | Meaning | You set it |
|---|---|---|---|---|
| 1 | value | string | The measurement, as a string: a decimal byte length or a checksum. Which of the two it is depends on the CheckType the challenge selected. | required |
| 3 | check_type | CheckType | The check type from the challenge, copied through unchanged. A CheckType value.The record declares a second field of this type that is never populated - leave it default. | required |
Recovered with score 200, confidence 0.99, margin 200 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.