THE QUICK ANSWER
Use the battle’s zero-based round number and the relevant user ID for a drop. A tie-break slot is a different input from the participant’s user ID.
01
Choose battle verification rather than a solo-case check
CSGOGem documents different inputs for cases and battles. Its battle system uses an EOS block hash from after everyone joined, together with the server seed and battle-specific identifiers.
The official battle page points to the Fairness panel after completion. Keep the battle ID, participant, round and case whose drop you are questioning; one battle can contain several different results.
Which identifier belongs to which check?
Battle ID
Identifies the overall battle.
Round number
Zero-based counter for the selected drop round.
User ID
Identifies the participant for a drop calculation.
Tie-break slot
A separate 1-to-count winner selection for tied players or teams.
Original identifier map based on the operator’s named fields.
Original explanation · not an account screenshot02
Match the revealed seed and the block hash
The help says the battle’s server-seed hash is displayed before gameplay and the actual seed is revealed after completion. It also distinguishes the EOS block number, used to look up the block, from the block hash used in the calculation.
Keep both the original commitment and the revealed data if available. A numeric block locator does not replace the long EOS hash in the verification inputs.
03
The battle round counter starts at zero
The official battle procedure names server seed, EOS hash, battle ID, round number and user ID. Its round number acts as the nonce, starting at 0 and increasing for each new round.
Use the identifier supplied for the participant being checked. A displayed name or a seat position is not automatically the same thing as the User ID requested by the drop calculation.
One battle, two possible verification questions
Case drop
Use seed, EOS hash, battle ID, round and User ID, then compare the ticket range.
Tie-break winner
Use the tie-break procedure and recorded player/team slot ordering.
Shared evidence
Keep the completed battle’s commitment and revealed seed together.
The illustration separates per-drop generation from final tie resolution; it contains no invented outcome.
Original explanation · not an account screenshot| Battle round | The documented counter begins at 0. |
|---|---|
| Drop participant | Use the User ID associated with that participant. |
| Tie-break slot | The separate selection is from 1 through the player or team count. |
04
A tied battle has a separate winner selection
For a tie-break, the help combines the server seed, battle ID and EOS hash, then selects a number from 1 through the number of players or teams. The matching slot receives the battle result.
A correctly reproduced case ticket does not by itself reproduce that tie-break selection. Keep the tied result and the relevant player or team ordering with the separate check.
05
Preserve a complete mismatch record
The operator’s fairness article links its verifier. Retain the exact input set, result, expected ticket range or tie-break slot and original battle reference. State whether the dispute concerns a particular player’s drop or the tied battle’s final allocation.
The article’s opening count of battle elements is inconsistent with its five-item list. Follow the named fields and verifier requirements; ask support about a missing field instead of dropping an identifier to match that introductory count.
BEFORE YOU CONTINUE
Quick checklist
- Select the original battle and the disputed participant/round.
- Use the revealed seed and full EOS hash.
- Retain the zero-based round number and User ID for drop verification.
- Check a tie-break slot separately from a case ticket.
Official sources
Official operator documentation reviewed on 26 October 2026. The checks below distinguish documented rules from suggested evidence to keep.
- CSGOGem — Provably Fair: battles and tie-breaks · reviewed
- CSGOGem — Case Battles and completed-game Fairness panel · reviewed
Public documentation only. No sign-in, payment, game, withdrawal or personal account test was performed. Recordkeeping suggestions are StrikePot editorial guidance.
Need the details for a particular website?
The code directory records each partner’s code, referral method and offer status. Use the relevant partner page when your question also involves one of those details.
Partner pages may include affiliate links. A listing does not confirm a reward or account eligibility.
