Evidence DeskIndependent Australian consumer reference
Verify Starlight Princess representations
Starlight Princess belongs to a grid-style tumble game family associated with scatter features and multiplier symbols. This guide explains how to inspect that combination and makes no present Rainbet listing, launch or supply claim for any edition or configuration.
Research checkpoint:
| Element | Rule to confirm | Session evidence |
|---|---|---|
| Grid win | Required symbol count and position rule. | Pre-evaluation grid and paytable. |
| Tumble | Removal, replacement and sequence endpoint. | Ordered states under one round ID. |
| Multiplier | Qualification, combination and award target. | Values, game state and displayed calculation. |
| Feature | Scatter entry, spins and retrigger conditions. | Entry grid, counters and transitions. |
| Identity | Exact provider, edition and rules version. | Information panel and game code. |
Evidence step 01
Distinguish the release from its artwork
Record the complete title, provider wording, game code and rules version from inside the product. Character artwork, stars and pastel graphics can identify a theme but not a technical release. Treat sequels, numbered variants and similarly named editions as separate until their identifiers and rules match. Save both the lobby tile and session screen if their names differ.
Date the observation and state whether it reached a listing, loading screen, rules panel or completed round. Each stage supports a different conclusion. An archived URL can preserve an old claim, but it cannot demonstrate current Rainbet access. If account, location or device restrictions block inspection, record that boundary instead of assuming the reason or availability for others.
Evidence step 02
Check the grid win and tumble sequence
Read how symbols create a win across the grid, including the minimum count and whether position adjacency matters. Do not assume fixed paylines. When a win removes symbols and new ones fall into place, capture each evaluation until the rules say the paid action is complete. The entire tumble sequence belongs with the same round record.
For a settlement question, save the starting stake and balance, every symbol state, intermediate displayed award and final ledger movement. A final feature summary may not reveal which tumble produced an amount. Keep an unedited sequence. If recording is impossible, make ordered captures and note any missing transition rather than reconstructing it from memory.
Evidence step 03
Follow multiplier application precisely
Multiplier symbols are a key distinction, but their effect depends on the written rules and game state. Capture when a value appears, whether a qualifying win is required, how multiple values combine and which award receives the result. Do not treat an animated multiplier as proof that it applied to every visible amount. Match the displayed calculation to the rule paragraph.
Check whether multiplier handling changes during a free-spin or other feature state. Save the transition into and out of the feature, remaining-spin counter, retriggers and any accumulated values. Optional feature-entry controls, if displayed, belong to the exact configuration and should not be generalised. This guide describes the evidence only and does not recommend activating paid options.
Evidence step 04
Assess scatter and feature claims
Use the paytable to determine the required scatter count, permitted positions and awarded feature state. Capture the grid before evaluation and the message confirming entry. Retrigger rules may differ from initial entry, so save the separate wording. An animation cannot replace the rule or establish the number of spins that should have been added.
If a feature ends unexpectedly, preserve the counter before the event, the round ID, any connection message and balance change. Do not claim that a network issue caused the result without provider logs. Ask for the session chronology and applicable rules version. Further play is not a reliable diagnostic technique and can make the original event harder to isolate.
Evidence step 05
Verify attribution without unsupported figures
Match the in-session provider and game code to an accountable developer source. Testing claims should identify the covered release, standard, jurisdiction and date. A generic badge, affiliate commentary or result history cannot prove which outcome system governed the session. Preserve conflicts between lobby and session attribution and request clarification rather than choosing one label.
Do not assert a numeric return, volatility, maximum result or current availability. Those facts can be configuration-sensitive and require evidence outside this page. For a dispute, retain the exact rules, grid sequence, multipliers, feature state, round ID, stake and ledger. State what the record demonstrates and identify any missing server or provider evidence that prevents a conclusion.
Questions
Questions for this evidence task
Are Starlight Princess and Gates of Olympus mechanically identical?
They may share a broad tumble and multiplier family, but verify each release, symbols, rules and feature behaviour independently.
When does a multiplier count?
Only as the actual rules specify. Save the game state, qualifying win, visible values and calculation for the affected round.
What should be recorded during free spins?
Capture entry scatters, selected state, counters, every tumble, multiplier handling, retriggers and the final ledger movement.
Does this guide confirm Rainbet access?
No. It makes no current listing, launch or availability claim for Starlight Princess.