Clover Flames and Dice: scatter-pays rules and bonus grid

Clover Flames by Endorphina and Clover Flames Dice belong in one comparison because they share the same reader task. Both checked pages publish a 5×5 grid, scatter payouts, 96.10% RTP, medium volatility and a €1–€180 reference range. The original is marked Approved; Dice reads Pending.

Their presentation differs: the original uses clovers and fruit, while Dice recasts symbols as dice. Never transfer a symbol value without matching the exact version.

Version table

Field	Clover Flames	Clover Flames Dice
Grid	5×5	5×5
Win model	Scatter payouts	Scatter payouts
RTP	96.10%	96.10%
Volatility	Medium	Medium
Stake reference	€1–€180	€1–€180
Status	Approved	Pending

These provider values do not establish NZD stakes or operator access. Save version title, game ID, currency and live help.

Scatter-pays base game

Endorphina says symbols count at any position. Confirm the minimum matching count and whether each symbol is counted anywhere on the 25-cell screen. This differs from left-to-right paylines; do not draw imaginary lines.

Record symbol count, paytable unit, total stake and credit. If the table uses base-bet multiples, confirm base bet. A cluster-looking animation does not make the game cluster pays.

Free Games trigger

Three or more pot Scatters trigger Free Games at the initiating bet. Dice symbol notes specify 10 spins for three Scatters, 15 for four and 20 for five. Verify the original version’s live table before assuming the same ladder.

During Free Games, number every spin and save retrigger rules. Keep scatter-pays awards separate from Clover Time awards and reconcile the final feature total once.

Clover Time

Six or more Golden Clover symbols—or Golden Clover dice in Dice—trigger Clover Time. The bonus uses a 5×5 grid with held symbols and empty cells, beginning with three attempts. Every new Golden Clover resets attempts to three.

At entry, capture all held symbols and values. After each attempt, record new landings, counter reset and jackpot labels. Count each cell once. Empty cells continue the sequence; they are not zero-value prizes to add.

The provider states that collecting all 25 Golden Clovers awards an ULTRA Jackpot of 1000× total bet. It also describes other jackpot outcomes up to 150×. Confirm the live paytable and whether any operator mode changes these values.

Original versus Dice symbols

In the Dice version, starred dice trigger Free Games and Golden Dice trigger Clover Time. Sevens are listed as the highest symbol, paying 50× base bet for twelve or more; hat dice pay 25× for twelve or more.

The original version uses corresponding themed objects without licensing the editor to assume identical names or values. Save each paytable separately. Visual equivalence is not mathematical evidence.

Risk Game

Both pages list Risk Game. Confirm eligibility, tie rule, maximum attempts and loss condition. Store the starting award, every card result and collection point.

An optional double-or-nothing decision sits after settlement. Declining it preserves the award and is valid. Previous card results do not improve the next choice.

RTP and medium volatility

The shared 96.10% provider figure is theoretical over many rounds. It is not a session refund or a forecast of a 25-clover screen. Preserve the live deployment’s RTP with version and date.

Medium volatility does not guarantee smooth play. Choose a fixed cash cap, time limit and ordinary stake. Do not chase the last empty bonus cells; their visual proximity does not determine probability.

Demo and mobile

Official demos can help locate rules where permitted, but do not prove funded NZ availability. Verify mode labels and IDs.

On mobile, test all 25 cells, counts, attempt counter, held clovers, jackpot labels, total stake and history at enlarged text. Dice pips and clover colours should remain distinguishable without colour alone.

After an interruption, use history to confirm server settlement before continuing.

New Zealand scope

The provider pages document two products, not their presence at a particular NZ-facing operator. Verify operator identity, country terms and authenticated lobby separately.

If a lobby title omits “Dice”, identify the version through symbols and game ID. Do not use artwork alone.

Audit worksheet

Create columns for version, RTP, currency, stake, round ID, symbol count, Free Games trigger, bonus attempt, new clovers, reset and final credit. This exposes double counting and version leakage.

For support, share redacted screenshots and exact timestamps. Never provide credentials or remote access.

Common questions

What RTP is published?

96.10% for both checked versions.

Are there paylines?

No fixed line count is published; both pages describe scatter payouts on 5×5.

What triggers Clover Time?

Six or more Golden Clover symbols in the corresponding version.

What happens at 25 collected clovers?

The provider describes a 1000× total-bet ULTRA award.

Is NZ access confirmed?

No operator-level access was established.

Worked bonus ledger

Start with attempt one and the six triggering clovers. After each spin, note new positions and reset the displayed counter only when a new symbol lands. If several appear together, record each value but one reset event unless help says otherwise.

At settlement, add regular prizes and named jackpots according to the live table. Do not add the ULTRA twice when it appears both on the final grid and summary screen.

Final assessment

Clover Flames is a clear example of scatter-pays accounting and a persistent 25-cell bonus. The Dice edition deserves the same canonical page but its own symbol evidence.

Use the provider numbers as scoped references. The loaded version, account-currency stake and current help determine practical suitability.

Twenty-five-cell accounting method

Draw a five-by-five table numbered from top left to bottom right. At feature entry, mark every triggering Clover and its displayed value. For each attempt, create a new row listing newly occupied positions and the counter shown after settlement. This makes it clear whether one event reset the attempts and whether several new symbols arrived together.

Keep regular symbol values, MIN, MID, MAX and ULTRA fields separate. When the twenty-fifth Clover lands, record the existing component total before the completion award appears. Then save the final screen and history. The difference between those values shows whether ULTRA was added separately or already included. Never add it again simply because the celebration repeats the label.

For Dice, also record pip or icon identity. For the original, record the corresponding fruit or clover identity. A shared numeric result does not prove that the two paytables use the same visual hierarchy.

Scatter-pays worked example

Suppose twelve sevens appear in Dice. Count all twelve cells, read the twelve-symbol row in that version’s paytable and use the unit displayed there. Do not construct paylines, and do not multiply by the number of possible geometric paths. Scatter pays evaluates the total count under its own table.

If pot Scatters also land, calculate their award or Free Games trigger separately. A symbol used to open a feature may still have a paytable value, but only current help can confirm whether both apply. Record the base-screen result before entering Free Games.

Version maintenance

Recheck both official URLs whenever either status, RTP or feature list changes. A change from Pending to Approved on Dice is not evidence that its mathematics changed; it is a status update. Conversely, matching artwork does not prove unchanged RTP. Maintain individual dated fields.

If an operator removes “Dice” from the visible title, use the actual reel symbols and game ID to identify it. If neither is available, do not publish a version-specific claim. An unresolved version should remain unresolved rather than being assigned to the original by default.

Budget and accessibility

The €1 provider minimum is only a reference, but it indicates that the live minimum deserves attention before play. Once the account-currency amount is known, calculate the number of ordinary rounds that fit the entertainment cap. Do not reserve extra money to chase twenty-five clovers.

On a small screen, each of the 25 positions must remain readable. Verify that held symbols, empty cells and attempt count use shape or text as well as colour. Reduced-motion settings should not hide settlement information. If the interface fails these checks, the sensible response is to stop rather than guessing values.

Recording a Clover Time sequence

Use a five-by-five paper grid or note template that mirrors the feature. Mark the six or more clovers that opened Clover Time, then write the attempt counter beside each subsequent state. When a new clover lands, circle it and reset the written counter to three only after the interface confirms the reset. This method separates a genuine new symbol from an animation replay.

At settlement, count occupied positions once and compare that total with the displayed award tier. Save the server round identifier alongside the grid. If the final screen disappears quickly, account history should remain the primary record; a hand-written reconstruction without the round ID is supporting context, not proof.

For the Dice edition, label the sheet “Dice” before starting. Mixing fruit and dice observations in one record would make later comparison unreliable.

Official and related sources

• Clover Flames official page
• Clover Flames Dice official page
• Endorphina catalogue guide
• Review methodology
• Responsible gambling

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.