NZ-NI-0426 · supplier source record

Temple of Ra: cascading wins and multiplier accumulator rules

Temple of Ra pays by symbol count rather than paylines, then removes winning symbols to create cascades. Its coloured multipliers behave differently in the base game and Free Games, so the settlement order matters more than the headline maximum.

Supplier sources below. Operator eligibility needs a separate check.

Original editorial artwork of a monumental sun temple, falcon guardian and cascading gemstones
Original editorial artwork; it is not official Endorphina game art.

Temple of Ra is a six-reel, five-row Endorphina slot that uses scatter-pay combinations and cascading reels instead of fixed paylines. The official product page checked on 8 October 2026 publishes 96.05% RTP, high volatility, a €0.20–€10 reference stake range and Approved status. Four or more Ra symbols trigger 15 Free Games with a multiplier accumulator.

Every ordinary symbol counts wherever it lands. A qualifying group is removed, replacement symbols fall into the empty cells and the next cascade is evaluated. Multipliers can appear in the base game and Free Games, but their activation and carry-over rules are not the same.

Provider settings checked

Field Published setting
Grid 6×5
Win model Scatter payouts
Provider RTP 96.05%
Volatility High
Bet reference €0.20–€10
Initial Free Games 15
Provider status Approved

These values identify Endorphina’s supplier record. They do not confirm availability with a New Zealand-facing operator, NZD stakes, the RTP deployed to an account or optional Bonus Pop access. The live help remains the account-specific source.

How scatter payouts differ from lines

Temple of Ra does not require matching symbols to follow a path from the leftmost reel. Symbols of one kind are counted across the full 30-cell grid. The current paytable defines the minimum count and award for each symbol.

Only the longest qualifying combination of a kind is paid in one evaluation. If a symbol count qualifies for both a lower and higher bracket, use the higher bracket rather than adding both. Different qualifying symbol types can contribute to the same cascade total.

Record the pre-cascade grid, the count for each winning symbol and the paytable bracket used. Do not describe a cluster unless the help calls for adjacency; the provider says position does not matter and only the number is relevant.

Cascade sequence

After a win, paid symbols disappear and replacement symbols enter. This produces another evaluation under the same paid round. The cascade continues while new qualifying counts occur.

Number every stage beginning with the original grid as cascade zero. For each later stage, note removed cells, new symbols, qualifying counts and subtotal. The base stake is deducted once, not once per cascade.

Bonus symbols are evaluated at the end of a winning cascade when enough remain. Preserve the final grid before the transition because earlier Ra symbols may have disappeared or new ones may have entered during tumbling.

Ra Scatter and Free Games

Ra is both a Scatter and the provider’s highest-paying symbol. Four or more Ra symbols trigger 15 Free Games with the Multiplier Accumulator. During the feature, three or more Ra symbols add five Free Games.

Keep the direct Scatter award separate from feature entry. Record the Ra count, paytable bracket, starting counter and round ID. A retrigger changes the remaining counter; it does not create a second paid round.

If several cascades occur before the trigger, save the exact cascade on which qualification is assessed. The public description places Bonus-symbol evaluation at the end of the winning cascade.

Four multiplier colours

Endorphina publishes four colour ceilings: green up to ×5, blue up to ×12, purple up to ×50 and red up to ×1000. These are maximum possible values by colour, not values that must appear in any session.

A multiplier activates only when a winning combination occurs. It is applied at the end of that winning cascade and produces further tumbling. A multiplier visible on a non-winning terminal grid should not be applied merely because it is present.

For every activated token, record colour, displayed value, cascade number and the subtotal it modifies. A red token is not automatically ×1000; its printed value is the evidence.

Base-game multiplier addition

In the main game, values of all multipliers present by the end of a winning cascade are added and applied to that cascade’s winnings. The operation is therefore addition of displayed multipliers followed by multiplication of the eligible subtotal.

For example, visible ×2 and ×4 tokens would form ×6 if the current help matches the public rule. They should not be multiplied into ×8. Use the settled history to confirm which cascade subtotal receives the combined value.

Do not carry a base-game combined multiplier into a later independent paid spin. Its scope belongs to the current cascade sequence.

Free Games multiplier accumulator

During Free Games, activated multipliers accumulate into a running total. That total persists across the feature under the published rules. A cascade ending with no multipliers does not apply the stored total to that cascade, although the total remains available for later activation.

This distinction prevents a common error: multiplying every feature cascade by the current accumulator. Log the accumulator before the cascade, newly activated values, accumulator after activation and whether it applies to the settled subtotal.

If a later cascade has no token, retain the accumulator unchanged but leave that cascade unmultiplied. The visual meter and round history should agree.

Eye of Horus and paytable anchors

The Eye of Horus is identified as the third-highest-paying ordinary symbol. Twelve or more are listed at 25× base bet. This entry helps verify the loaded paytable but does not describe every possible symbol count.

Save the full table from the current build. A count of eleven cannot be assigned the 12+ award, and a larger count must use the bracket actually displayed. Preserve “base bet” as the unit until the interface defines it relative to total stake.

Ra, multiplier tokens and ordinary gemstones should be logged as separate symbol classes. A token can modify a win without belonging to the count that created it.

Bonus Pop and Classic Risk

Bonus Pop appears in the provider feature list, with the usual warning that jurisdiction and operator configuration may make it unavailable. If present, record cost, currency, state entered, RTP note and confirmation wording. If absent, mark it unavailable in the checked build.

The Classic Risk Game can double eligible settled winnings up to ten times according to the supplier. It is a post-win choice, separate from cascades and the Free Games accumulator. Save the eligible amount before entering and every later decision.

Neither option deserves a separate Temple of Ra URL. Their rules belong to this canonical page, and neither should be represented as universally available in New Zealand.

RTP, volatility and stakes

The 96.05% supplier RTP is a theoretical long-run value for the published configuration. It does not forecast when Ra or a red multiplier will appear. High volatility is a provider classification, not a schedule or promise of a large result.

The €0.20–€10 range is euro-denominated metadata. It does not prove NZD limits or increments. Record the actual account currency and total debit shown before a spin.

If a live build displays another RTP, publish it separately with operator, version and check date. Never average it with 96.05% or silently select the higher value.

Mobile and demo checks

On mobile, all 30 cells, multiplier colours and displayed values must remain distinguishable. Test portrait and landscape, enlarged text, the accumulator meter, cascade recap and feature counter.

Fast cascades can hide intermediate states. Disable rapid play where possible and use history to verify the numbered sequence. Restoring a backgrounded browser should preserve the accumulator and Free Games counter.

A permitted demo can explain interface flow but cannot prove real-money access, operator RTP or New Zealand availability. Label the domain, mode and check date on demo evidence.

Reconstructing a complete feature

Start with title, game ID, version, operator, date, device, currency, stake and displayed RTP. Save the symbol-count paytable, Ra trigger and both multiplier rules.

For every cascade, retain the grid before removal, qualifying counts, subtotal and activated multipliers. During Free Games, add the accumulator before and after each stage plus every five-spin retrigger.

Reconcile opening balance minus one paid debit plus the final settled credit. Add Risk only if deliberately entered after settlement. Do not add cascade animations again when history already includes them in the feature total.

Common interpretation errors

  • Looking for paylines in a scatter-pay game.
  • Requiring adjacent symbols when only total count matters.
  • Paying several brackets for one symbol type in one evaluation.
  • Applying a multiplier on a non-winning terminal cascade.
  • Multiplying base-game tokens together instead of adding values.
  • Applying a stored Free Games multiplier when no token activates.
  • Treating colour ceilings as displayed values.
  • Claiming the euro range as an NZD limit.

Each error changes settlement. A cascade-by-cascade table is the clearest safeguard.

Who may prefer the format

Temple of Ra may suit readers who enjoy count-based wins and want a feature with visible mathematical state. The accumulator is auditable when each activation is recorded.

It may be less suitable for someone who prefers fixed lines, low visual movement or a simple one-stage feature. High volatility and large headline multiplier ceilings do not remove ordinary loss risk.

Final assessment

Temple of Ra combines three rules that must be read in order: count scattered symbols, resolve cascades, then apply only activated multipliers. In the base game multiplier values add for one cascade; in Free Games activated values accumulate, but a no-token cascade does not use the stored total.

Endorphina supports the 6×5 model, 96.05% RTP, 15-spin entry and colour ceilings. Live help must still confirm exact brackets, deployed RTP, account access, stakes and optional controls.

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.

Primary source and correction path

This guide separates documented product information from market availability. Check the official source and the game help inside the exact version offered before making a decision.

Keep building your North Island plan