Start inside the loaded game

Common entry points include an information symbol, a help menu, a settings panel or a paytable button. Their placement varies, so look for labelled controls rather than assuming a universal icon. The relevant material may span several pages. Distinguish game-specific rules from general account help: a wallet guide will not necessarily explain how a particular symbol substitutes or how a feature ends.

Record identifying details

Useful identifiers can include the displayed title, version or build number, provider name where shown, and the date of access. Some games expose a configuration identifier or an RTP statement without a readable build number. Record what is actually available; do not infer missing details from the artwork or filename. A title shared across versions is not sufficient evidence that every rule and percentage is identical.

Find the key rule sections

Read the ordinary award method, stake units, special-symbol behaviour, feature triggers and maximum-award conditions. If the game has multiple modes, note which panel describes the mode currently selected. A hypothetical feature may use a different multiplier rule from ordinary spins. A screenshot of the base paytable alone would then be incomplete evidence for a question about an award earned within that feature.

Handle apparent inconsistencies carefully

A short catalogue summary may lag behind the loaded information, or two panels may use different units. First check whether the statements concern the same configuration, mode and stake basis. Preserve the exact wording of both if the difference remains. Avoid silently resolving the conflict by choosing the higher RTP or larger award. The useful next step is a specific clarification supported by the conflicting details.

Prepare a compact reference record

  • Title and any visible build or configuration identifier.
  • Date, mode and language of the displayed rules.
  • Applicable stake and denomination.
  • The relevant rule text or permitted screenshot.
  • Round identifier if the question concerns an actual outcome.

Do not record passwords, authentication codes or unrelated personal information. The purpose is to identify the game and the rule, not to create a broad account dossier.

Finding a version number does not independently verify fairness or correctness. It provides a precise reference point. That precision helps separate a misunderstanding about units from a configuration question, and a general description from the rules actually presented when the round was played.

Language selection can matter when comparing wording. A translated label may shorten a technical condition without changing the underlying rule. If two language panels appear inconsistent, record both and request clarification rather than assuming the more favourable phrasing creates an additional entitlement.