Provider and version: identify the exact game

Sweet Bonanza 1000 and Gates of Olympus 1000 are recognisable titles associated with Pragmatic Play. When locating a game on Zora.bet, they illustrate why version names matter: the complete title should accompany any feature description or RTP reference. A familiar theme can continue across several releases, while the rules, multiplier behaviour or available configuration may differ. Use the help panel inside the version opened from the catalogue rather than relying on memory of a similarly named game.

When comparing two releases, look at the stake selector, win evaluation and optional feature purchases separately. The studio name alone cannot tell you whether an option is enabled for your account or eligible under a selected promotion. The Bonus Buy guide explains ordinary spins and paid feature entry, while the bonus guides explain why campaign eligibility must be checked independently of catalogue availability.

Create a three-part record: exact title including any suffix, developer and the mode named in the rules. This is more reliable than a cropped game logo. When asking about a discrepancy, include those identifiers so a comparison does not accidentally combine the original release with a sequel or special edition.

A reliable identity contains the complete name, the developer shown on the game card and any version or mode suffix. Artwork is useful for discovery but can change independently of the name. A search result cropped to a familiar logo may therefore be insufficient for a technical question or a mathematical reference.

The public catalogue supplies examples across studios: Amusnet names include Shining Crown, 40 Super Hot and Burning Hot; Sweet Bonanza is associated with Pragmatic Play. The observed search also contains Chicken Road 2.0 from InOut. These names identify what was visible, not proof that every title was launched or that its active configuration was tested.

For one game, a full help panel may be available; for another, you may have only a public card. Record that difference instead of writing equally detailed claims for both. A thumbnail can establish the displayed title and controls. It cannot establish the complete paytable, enabled optional modes or account-specific promotion eligibility.

When a manufacturer describes more than one configuration, the general reference is not enough to identify the one loaded by the operator. Keep the reference and the observed configuration separate. Do not select the most attractive percentage simply to fill a comparison table that otherwise has a blank field.

A suffix such as 1000, Deluxe or a numbered sequel signals a distinct title that needs its own inspection. It does not, on its own, explain what changed. Compare the rule sections for symbol evaluation, feature entry, multipliers and optional actions, recording only the differences actually documented.

A useful note might say that a purchase option was visible in one inspected mode but not confirmed in the other. That is more precise than claiming the sequel always includes a feature. The observation should remain attached to the date, version and screen from which it came, rather than becoming a universal statement about the whole game family.

Name a saved image with the full title and the screen it shows, such as a public card or information panel. Keep the suffix in the filename. This prevents a later article from illustrating one release with another release's controls, especially when their colour palette and characters are similar.

For a support query, add the round identifier if a round is involved. A studio name alone narrows the catalogue but does not identify a transaction. If the question concerns a promotion, add the campaign and balance source as separate fields. Correct identification is the foundation for a useful answer; it is not an endorsement of a studio's expected results.