Skins. Codes. Clear answers.

Guides/CS2 site guides

CS2 site guides

CSGOEmpire cases: match seed, nonce and ticket range

A CSGOEmpire case check needs the revealed server seed, client seed, nonce and ticket quantity. Compare the resulting ticket with the item’s range for that case.

3 min read
Published Revised

THE QUICK ANSWER

Use the inputs for the original opening and the correct version of the verifier. The spinner does not determine the recorded case result.

CSGOEmpire logo
CSGOEmpire: case ticket verification

01

The opening record matters more than the spinner

CSGOEmpire says a case result is generated when the case is opened; the spinner displays it. If the animation froze or looked different from your expectation, start from the case-history record.

Keep its time, case type, result and reference. This is a result-generation check; a later skin trade or balance movement needs its own record.

STRIKEPOT / EXPLAINED

From original inputs to recorded item

  1. Original seed pair

    The pair used for the selected opening.

  2. Nonce and quantity

    The opening counter and relevant case size.

  3. Calculated ticket

    Output from the matching official verifier.

  4. Item range

    Compare the ticket with the case’s recorded outcome range.

Original explanation of the documented case-verification chain; no case was opened.

Original explanation · not an account screenshot

02

Copy the four script inputs for that opening

The published case verifier takes an unhashed server seed, nonce, client seed and ticket quantity. The nonce increases when that seed is used. The article locates case information under Cases on the Fairness page.

An active server-seed hash is not the revealed seed expected by that script. The help says regeneration reveals the prior server seed; retain the opening’s original pair instead of substituting whichever pair is current now.

Inputs that identify a particular opening
Server and client seedsUse the pair belonging to the opening.
NonceUse that opening’s counter, not the next visible value.
Ticket quantityUse the quantity for the relevant case.

03

A matching ticket also needs the matching case table

The official instructions calculate a ticket and then check which item range contains it. Open the relevant case type to compare the range with the skin recorded for that opening.

Do not treat a ticket number as the item’s price or as a guarantee of a particular Steam copy. Keep the table or result details attached to the same opening when asking support to reproduce a mismatch.

STRIKEPOT / EXPLAINED

Three common sources of a false mismatch

  1. Hash instead of seed

    A commitment cannot replace the revealed script input.

  2. New pair instead of old

    The current pair may belong to later openings.

  3. Wrong dated verifier

    The article separates openings before 18 April 2024.

  4. Wrong table

    The ticket must be compared with the relevant case’s range.

The cards identify input-selection errors, not evidence that a particular result was manipulated.

Original explanation · not an account screenshot

04

Older openings have a different documented script

The article links a separate verifier for openings before 18 April 2024. If you are checking an old record, its date is part of selecting the procedure.

Using a newer formula on an older opening can create a false mismatch. State the article or verifier version you used rather than reporting only that a number was different.

05

Send a reproducible ticket mismatch

Retain the opening reference, date, case, original inputs, calculated ticket and the recorded item range. Check spelling, whitespace and counter selection before escalating.

If the ticket matches but the item delivery does not, switch to the delivery record and explain that separate issue. A reproduced random draw does not confirm that a withdrawal completed.

BEFORE YOU CONTINUE

Quick checklist

  • Start with the original opening, date and case.
  • Use the revealed seed and original nonce.
  • Select the documented verifier version for the date.
  • Compare the calculated ticket with that case’s item range.

Official sources

Official operator documentation reviewed on 26 October 2026. The checks below distinguish documented rules from suggested evidence to keep.

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.

KEEP READING

A useful next read.

All guides

CS2 site guides · 3 min read

CSGOEmpire: pending skin trades

For a missing or wrong CSGOEmpire skin offer, check the pending trade’s timer, inspect the item in Steam and dispute it before that timer expires.

Read guide

Support · 3 min read

A better support ticket

Include the affected order or trade, the exact status and a dated timeline. Use the template to explain what happened and ask for the next step.

Read guide

Support · 2 min read

Share evidence, keep secrets

Show the error, affected item and useful reference. Hide passwords, codes, payment details and unrelated personal information before sharing.

Read guide