Evidence DeskIndependent Australian consumer reference
Verify Gates of Olympus claims
Gates of Olympus is associated with a grid-style tumble format, scatter-triggered features and multiplier symbols. Related releases can differ, so this guide describes what to inspect and makes no present Rainbet supply claim for any title, version or playable session.
Research checkpoint:
| Element | Question for the rules | Evidence for a dispute |
|---|---|---|
| Release | What exact title, provider and game code loaded? | Loading screen and information panel. |
| Grid wins | How are matching symbols counted? | Paytable and pre-evaluation grid. |
| Tumbles | When does the replacement sequence end? | Complete sequence and round ID. |
| Multipliers | When are values collected and applied? | Rule paragraph and affected win states. |
| Feature | What triggers, retriggers or changes the state? | Scatter states, feature rules and ledger. |
Evidence step 01
Identify the exact release
Record the complete in-session name, provider attribution, game code and rules version. Do not collapse the original title, sequels and similarly branded editions into one product. A lobby tile that adds a number or subtitle may indicate a distinct release. Compare the loading and help screens, because cached artwork or a shortened menu label can conceal that distinction.
Save the hostname, date, language and account context with the identification evidence. If the product cannot be launched, the finding must stop at the listing stage. An indexed URL or archived catalogue can show that wording existed historically, but it cannot establish that Rainbet supplies the release now or that the same configuration would load for another user.
Evidence step 02
Read the tumble and win rules
Use the actual paytable to determine how matching symbols are counted, whether positions must be adjacent, and what happens after a winning evaluation. In a tumble system, removed symbols and replacement symbols can create several evaluations within one paid action. Capture where the rules define the end of that sequence so a later balance question can be tied to the correct event.
Do not assume that conventional left-to-right paylines apply. Record any minimum symbol count and whether wins are calculated by symbol anywhere on the grid. If the interface presents a total for a tumble sequence, preserve the intermediate states as well as the final amount. A final screenshot cannot show whether every component was evaluated under the stated rules.
Evidence step 03
Examine multipliers and the feature state
Multiplier symbols in this game family are commonly linked to particular win or feature conditions. Check precisely when a multiplier is collected, whether several values combine, and whether it applies to one tumble, a sequence or a feature total. Never infer the rule from the animation. Save the paragraph in the help panel and the complete event sequence for any disputed application.
For scatter-triggered features, record the qualifying symbol condition, awarded state, retrigger rule and any changed symbol or multiplier behaviour. Optional entry or feature purchase controls, if shown, must be treated as configuration evidence and not assumed to exist elsewhere. Note their terms without encouraging use. A different feature state can change play mechanics, but it does not justify publishing unsupported performance figures.
Evidence step 04
Match provider and technical evidence
A familiar Zeus image does not identify the developer. Match the in-session provider label and game code to an accountable provider page or support response. If testing or randomness is claimed, the supporting record should identify the covered release, standard, jurisdiction and date. A badge or generic certificate with no product mapping cannot settle a configuration question.
Avoid numeric return, volatility, maximum-win or probability claims unless the assignment includes authoritative configuration-specific evidence; this page intentionally publishes none. Short play histories cannot validate those figures. When two rules screens disagree, retain both, note their dates and identifiers, and ask which version governed the disputed round instead of selecting the wording that appears more favourable.
Evidence step 05
Build a feature dispute record
Preserve the opening stake, balance, round ID, each tumble, multiplier appearance, scatter count, feature transition and final ledger movement. A screen recording is useful when it includes the product and time context, but retain still captures of identifiers and rules too. Do not continue wagering in an attempt to reproduce a rare sequence or gather a larger sample.
Ask support to confirm the exact release, rules version and server-side round record. Keep the response with the original evidence and redact unrelated personal information from shared copies. This page does not confirm current Rainbet access. A conclusion should say only what the dated records demonstrate and list the missing provider record if the mechanic or settlement cannot be reconciled.
Questions
Questions for this evidence task
Is every Gates of Olympus edition the same?
No. Treat subtitles, numbered editions and changed identifiers as potentially distinct releases and check their own rules.
How should a tumble dispute be recorded?
Save each evaluation in sequence, the round ID, starting stake and balance, applicable rules and final ledger movement.
Can multiplier behaviour be inferred from animation?
No. Use the help text for when values are collected and applied, then match it to the complete round sequence.
Is present Gates of Olympus access established here?
No. This guide makes no current availability or launch claim and explains how to test a dated representation.