Rainbow Ray: cascades, Free Games multipliers and Magic Clover

Rainbow Ray is a six-reel, five-row Endorphina scatter-pay slot with cascading reels. The supplier page checked on 8 October 2026 lists 96.12% RTP, high volatility, a €0.20–€100 reference stake range and Approved status. Four or more leprechaun Bonus symbols start ten Free Games; three or more during the feature add five spins.

All ordinary symbols are scattered symbols, so location does not create paylines. During Free Games, multipliers from 2× to 100× can land and a Magic Clover clears the row and column crossing its cell.

Verified provider profile

Field	Official listing
Grid	6×5
Evaluation	Scatter payouts
Provider RTP	96.12%
Volatility	High
Bet reference	€0.20–€100
Initial Free Games	10
Retrigger	3+ Bonus symbols → 5 spins

This record identifies the supplier design. It does not prove NZ operator availability, NZD stakes, a deployed RTP or access to Bonus Pop. Verify those points inside the live account.

Counting scatter-pay symbols

For an ordinary result, count every copy of one symbol across all 30 positions. The official description says position does not matter; the count threshold in the paytable determines the award.

Do not build horizontal, diagonal or adjacent paths. A group split between opposite corners can belong to the same count, while a visually connected group still needs enough total copies.

Pots of gold are identified as the highest-paying ordinary symbol after the Bonus, with 12 or more listed at 50× base bet. That figure is a paytable anchor, not a maximum-win claim.

Cascade order

After a qualifying count, the contributing symbols disappear and new symbols fall into the empty cells. The next grid is evaluated again. A sequence can contain several cascades under one paid spin.

Number the initial grid C0 and later states C1, C2 and onward. For each state, record symbol counts, award components and symbols removed. This prevents the same cells from being counted twice.

The cascade ends when no new qualifying count appears. Reconcile the complete sequence with one round-history entry rather than treating every refill as a new wager.

Bonus trigger and retrigger

Four or more leprechaun Bonus symbols lead to ten Free Games. The product page lists an additional 100× base-bet award for six or more Bonus symbols. Preserve the exact count because trigger and paytable outcomes are related but distinct fields.

Within Free Games, three or more Bonus symbols add five spins. Record the counter immediately before the event, the added amount and the new total. A retrigger extends the original round and should not debit another stake.

Bonus symbols are protected from the Clover clearing rule according to the provider description. Keep them separate when reconstructing the cross-shaped removal.

Coloured multipliers in Free Games

Multipliers can appear during Free Games but remain inactive until the winning cascade ends. Endorphina groups them by colour: green up to 8×, blue up to 18×, purple up to 35× and red up to 100×.

The description says landed multipliers are summed and applied to cascade winnings at the relevant end point. Record every colour and printed value before adding them. Do not multiply them together unless current help explicitly instructs that operation.

An icon without a winning cascade does not automatically create a cash award. Preserve the feature summary to see whether unused multipliers carry forward or expire under the loaded version.

Magic Clover geometry

Magic Clover appears only in Free Games. It blasts all symbols in the same row and reel, except multipliers and Bonus symbols. On a 6×5 grid, this creates a cross rather than clearing the whole screen.

Mark the Clover coordinate, then shade its row and column. Remove ordinary symbols in that cross while leaving protected multiplier and Bonus cells untouched. Save the resulting grid before gravity refills it.

If more than one Clover appears, follow the current help and animation order rather than assuming simultaneous or repeated clearing. Event sequence can affect which symbols survive to the next evaluation.

A complete feature ledger

Start with the paid stake, currency, version and displayed RTP. Note the Bonus count and starting Free Games. For each spin, create rows for initial grid, ordinary winning cascade, Clover event, later cascades, multiplier activation and retrigger.

Keep the raw win before multipliers separate from the applied factor and final credit. If the history presents one inclusive amount, use it as the settlement reference and retain the component ledger only as an explanation.

The closing balance should equal opening balance minus the original paid stake plus the completed round credit. No additional stake belongs to individual cascades or Free Games.

Risk Game and Bonus Pop

The official page lists Classic Risk, allowing an optional post-win decision up to ten times. It comes after a settled eligible win and does not change how scatter counts, cascades or Clover work.

Bonus Pop is also listed, with the warning that availability depends on casino and jurisdiction. Confirm its presence, price and changed route from live help before describing it as usable.

An absent optional control is not evidence of a broken game. Operator configuration can remove the option while leaving core mechanics unchanged.

RTP, volatility and stake scope

The 96.12% RTP is a long-run theoretical supplier figure. High volatility signals that result distribution can be uneven; it does not predict a multiplier, retrigger or session outcome.

Where a live build reports another RTP, publish both figures with source and check date. Never imply that the higher catalogue number overrides the actual loaded configuration.

The euro stake range cannot be promoted as an NZD minimum or maximum. Account currency, increments and responsible-play limits require direct confirmation.

Mobile and demo review

On a narrow screen, check whether all 30 cells remain visible and whether colours have labels or readable values. Test paytable zoom, feature counter, round history and orientation changes.

A permitted demonstration can show cascade order and Clover geometry, but not real-money availability or cashier rules. Label screenshots as demo evidence and avoid presenting simulated balances as withdrawals.

Errors to avoid

• Inventing paylines in a scatter-pay grid.
• Treating each cascade as another paid spin.
• Multiplying coloured factors when rules say sum.
• Applying a multiplier before the cascade sequence ends.
• Clearing Bonus and multiplier cells with Clover.
• Awarding a retrigger from fewer than three Bonus symbols.
• Presenting 100× as a guaranteed Bonus value.
• Claiming Bonus Pop is available in every jurisdiction.

Frame-by-frame cascade worksheet

A Rainbow Ray screenshot should be treated as one frame, not a complete round. Build a worksheet with columns for frame ID, grid state, winning symbol, qualifying count, raw award, removed cells, Clover coordinate, protected cells, new multiplier and remaining Free Games. Start with C0 and add a row every time the grid changes.

When a Clover fires, list the cells in its row and column, then cross out any multiplier or Bonus position because the official description protects them. The remaining marked cells are removed before the refill. If a later cascade creates another award, place it in a new frame rather than rewriting C0.

At the end of the winning cascade, inventory every active multiplier by colour and printed value. Add values only as the current help directs, record the raw cascade total, and show the resulting product as a separate figure. This creates a transparent bridge between visual events and the inclusive credit in history.

For a retrigger, record the Bonus count and counter transition at the exact frame where it occurs. The five added spins should be visible as a change in the feature counter, not inferred from the final number of animations.

Handling version changes

The supplier page is a dated snapshot of the declared model. A later live build could alter the stake ladder, optional controls or RTP without changing the title artwork. Preserve the game ID, help revision and check date whenever a number is quoted.

If a changed version is found, update only the affected fields and retain the earlier observation in a revision note. Do not merge two RTP values into an average or describe a jurisdiction-specific Bonus Pop button as universal. A clean version history is more useful than a single confident number without scope.

Support-ready record

For a settlement query, provide the round identifier, complete frame worksheet, total stake, currency, opening balance, feature counter and final history amount. State the expected difference neutrally and keep the supplier page as contextual evidence rather than proof of the operator’s deployed setting.

Final assessment

Rainbow Ray is best understood as an event timeline. Counts create wins, wins create cascades, Clover changes the grid, and only then do stored multipliers resolve. A static final screenshot cannot explain that order on its own.

The supplier page supports the headline mechanics and 96.12% RTP. Live help must still confirm version, stake currency, RTP, optional features and local access.

Official and related sources

• Rainbow Ray official product page
• Endorphina catalogue guide
• All Ways Luck guide
• Responsible gambling guide
• Corrections policy

How to verify the version you can actually open

A provider page proves that a title exists and describes the supplier's intended rules. It does not prove that a casino accepts players in New Zealand, that the title is enabled for a particular account, or that the highest published RTP is the version in the lobby. Treat availability, operator eligibility and product configuration as three separate checks.

Start with identity, then configuration

Open the game only through the authenticated casino lobby. The information or help panel should identify Endorphina, the exact title and the active mathematical return. Compare the reel or grid layout, paylines or cluster rules, named features and symbol behaviour with the official product material. Similar artwork or a matching title is not enough when the help file is missing or inconsistent.

When the supplier publishes several RTP values, report all of them as configurations. Do not assume the highest option is deployed. RTP is a theoretical long-run measure across a very large number of rounds; it is not a refund rate for one player and cannot predict the next result. Volatility is different: it describes how unevenly results are distributed on the provider's scale.

Read stake controls as money, not interface decoration

Provider sheets often quote a reference range in euros. That range does not establish New Zealand-dollar support or the limits in a specific account. Before a paid round, identify the total amount that will leave the balance. If the interface separates denomination, coins and lines, verify the combined total. If Extra Bet is active, calculate its full cost before pressing spin.

Feature-buy prices are multiples of the current bet, not promised returns. A 100x purchase at a $1 stake costs $100; at a $2 stake it costs $200. Availability can vary by market and some mathematical configurations may not support the control. If the live help does not explain the price, delivered feature and active RTP, leave the option unused.

Keep simulation figures in their proper scope

A game sheet may publish a maximum result observed in a large simulation. That is not automatically the contractual maximum payout and never describes a likely session. Preserve the provider's wording, sample size and configuration. Check the live rules for a binding cap and the operator terms for any separate payout limit. Do not turn an extreme result into a promotional headline.

Audit a disputed round

If an animation freezes or a connection drops, do not repeat the wager immediately. Reopen the game through the authenticated lobby and inspect round history. Record the time, total stake, balance movement and round identifier. The result can be settled by the gaming system even when the device never displays the final animation. Send evidence through verified operator support; never disclose a password, recovery phrase or one-time code.

Read the paytable as a calculation document

The paytable should explain what creates a win, which symbols substitute, where special symbols can land and how multiple awards combine. For line games, confirm direction and active paylines. For cluster games, confirm adjacency, minimum group size and the order of collection. For respins, identify what remains locked, what resets the counter and what ends the feature. A graphic effect can illustrate those rules but cannot replace them.

Separate addition from multiplication. Several prize values may be added before a multiplier applies, while reel-specific multipliers can sometimes multiply together only when each reel participates in the same win. Reconstruct one low-stake result from game history. If the arithmetic cannot be matched to the help file, stop and ask the operator rather than guessing.

Do not confuse hit frequency with a profitable round

Provider sheets can publish hit frequency or category probabilities. A hit simply means a round returned a qualifying amount; it can be smaller than the stake. “Big”, “Mega” or “Epic” thresholds are provider reporting categories, not promises. They are useful for comparing mathematical versions only when definitions and samples are the same.

Random outcomes do not become due after a long gap. A feature that appeared repeatedly in a demo or marketing clip has no obligation to repeat in a funded session. Previous rounds do not create a debt from the next random result.

Confirm market and device behaviour independently

A title can exist in the supplier catalogue while an operator disables it for a territory, currency, device or bonus. Language localisation is not evidence of legal availability. Confirm the operator's identity, accepted countries and current lobby separately from the provider review.

On mobile, verify that balance, total bet, feature state and help remain visible without overlap. On desktop, check that browser zoom does not hide a purchase control or change the apparent denomination. Mathematical configuration should not change merely because the screen changes; if the help shows another RTP, treat it as a different deployment and record it.

Keep a compact evidence record

For any fact used in a review, save the title, provider, official URL, document date when available, access date and exact territorial scope. For a live session, add the operator domain, Game ID, RTP, currency and a non-sensitive screenshot of the help panel. This makes later corrections possible when a supplier updates a sheet or an operator changes configuration.

Missing information should remain missing. Do not estimate an RTP from results, convert a euro reference range into an operator's NZD limit, or treat another casino's configuration as evidence. A transparent “not confirmed” is more useful than a precise-looking number without the correct source.

Use limits that survive the feature design

Collection meters, expanding grids, sticky symbols and near misses can make a session feel unfinished. Unless the rules explicitly preserve progress, the visible state has no value after the round or feature ends. Set a money limit and time limit before launch, count feature buys immediately, and stop at the limit even when a meter appears close to an upgrade.

No random game is an income plan. Do not borrow, use essential funds or raise the stake to recover a loss. If play stops feeling recreational, use timeout, deposit-limit or self-exclusion tools and consult the site's responsible gambling guide.