Crown Coins and Dice: two royal treasury builds

Crown Coins and Crown Coins Dice are related Endorphina games with separate official pages. Both use a 3×3 grid, five fixed lines, a 96.06% provider RTP reference and a €0.05–€80 range. Their key difference is not only fruit versus dice artwork: the original is labelled medium-high volatility and Approved, while Dice is labelled high volatility and Pending.

One canonical family guide prevents two near-identical rule explanations from competing. It also makes version identification unavoidable before any number is used.

Version comparison

Field	Crown Coins	Crown Coins Dice
Grid	3×3	3×3
Lines	5 fixed	5 fixed
RTP	96.06%	96.06%
Volatility	Medium-high	High
Bet reference	€0.05–€80	€0.05–€80
Status	Approved	Pending
Main motif	Fruit and coins	Coloured dice

Do not identify a build from the shared dimensions alone. Record the help title, game ID, symbol set and status date. An operator may shorten the lobby name, so the live symbols and source URL are stronger evidence than the tile caption.

Original base game

The original uses familiar fruit, bars, bells and sevens. Wild sevens substitute for symbols other than special symbols in the main game. The provider publishes 50× base bet for three Wilds and 30× base bet for three bars.

Check whether the paytable uses base bet, line bet or total bet before calculating. On a five-line game, multiplying a displayed total by another five can overstate a win. Save the active lines, debit and history credit together.

Dice base game

Dice replaces fruit with a neon dice presentation. Wilds remain main-game substitutes excluding special symbols, with 50× base bet published for three. The star follows at 30×, while thunder is listed at 20×.

Those symbol values help identify the Dice build, but they remain provider-page references. The live help must confirm the exact paytable and denomination. Do not combine the original bar value with the Dice star hierarchy.

Royal Treasury trigger

In the original, three or more Gold or Royal Coins across all three reels trigger Royal Treasury. In Dice, Gold or Royal Dice serve the same role. The official pages also describe Lucky Time as a possible route when special symbols appear on only one or two reels.

“Possible” is not a guaranteed rescue. Record which reels contain special symbols, whether Lucky Time appears and the resulting state. A near-trigger has no value unless the rules explicitly award one.

Three-by-three feature grid

The base reels become nine positions. Gold Coins or Gold Dice appear on reels one and three; Royal Coins or Royal Dice appear on reel two. Every regular special symbol carries a value, while Royal symbols act as collectors.

Create a nine-cell worksheet. Mark the starting state, attempts remaining and every subsequent arrival. Collector symbols should have their own column because they accumulate values from qualifying gold symbols after each spin. Do not add an accumulated display and the same underlying symbols twice.

Jackpot and value scope

The original page names regular prizes up to 15× total bet plus MIN, MID, MAX and ULTRA jackpots, with the feature description referring to a maximum of 1000× total bet. Dice also describes four jackpots up to 1000×. These are feature ceilings, not expected outcomes.

Check whether each jackpot is a multiplier or a fixed account-currency amount in live help. If a figure changes with stake, capture the stake before the feature. If it is fixed, preserve the displayed amount and currency without reverse-engineering a multiplier.

Collector arithmetic

Suppose two gold symbols show 2× and 5× while one Royal collector is present. The correct calculation depends on when the collector evaluates and whether it collects current, new or all qualifying symbols on each spin. The public description alone is not enough to settle that timing.

Write each state chronologically. Record the collector’s displayed total after every spin, then use the final history credit as the settlement reference. This method detects double counting without inventing a timing rule.

Classic Risk Game

Both public descriptions say winnings can be doubled up to ten times through a Classic Risk Game. “Up to” does not mean ten attempts are always available, and a successful step does not make the next one safer.

Before using any risk control, read the stake, eligible balance, stop condition and potential loss. Record the amount entering the risk screen, each decision and final credit. Opting out preserves the settled win; the feature should never be treated as necessary to complete a round.

RTP and volatility difference

Both pages publish 96.06% RTP, yet their volatility labels differ. RTP describes a long-run theoretical proportion; volatility describes distribution. Equal RTP does not make two versions interchangeable, and higher volatility does not mean a larger result is due.

The loaded build may expose another certified setting. Keep the provider reference and live help value in separate fields with dates. Do not average the two or report the original label for Dice.

Demo, mobile and accessibility

Endorphina provides demo links and describes both games as mobile compatible. Demo access still depends on location, age and host policy. It does not establish real-money availability at a New Zealand operator.

On a phone, confirm that reel numbers, collectors and attempts remain visible. Gold and Royal pieces must be distinguishable by shape or label, not colour alone. In Dice, verify that different jewel colours remain legible under reduced brightness.

New Zealand scope

The provider pages do not prove a New Zealand listing. The operator lobby, account location and current terms must be checked directly. Record the precise product identifier because two versions share much of their name and structure.

Keep supplier status separate from casino permission. Approved on a studio page describes provider-side evidence; it does not certify a particular operator relationship or make the pending Dice page available locally.

Version-control worksheet

For each observation, save: version name, game ID, symbol family, RTP, volatility, minimum debit, currency, Royal collector wording, Lucky Time wording, Risk Game availability and check date. Store the original and Dice rows separately.

If a lobby switches versions, retain the earlier observation and mark it no longer observed. Silent replacement would erase useful history and could attach the wrong volatility or paytable to a screenshot.

Common questions

Are the two games just visual reskins?

No. Their official pages publish different volatility and status labels, even though core dimensions and RTP match.

Does one or two special-symbol reels guarantee Lucky Time?

No. The pages describe a chance. Verify the live rule and observed result.

Is 1000× a fixed jackpot?

The source uses a total-bet multiple. The live help must show how the current deployment presents each jackpot.

Should each version have a separate URL here?

No. Their search task and rule comparison belong in this single canonical family guide.

Royal collector timing test

Collector timing is the most important detail to verify. Start with an empty nine-cell diagram. After every feature spin, copy the Gold values currently present and the displayed total on each Royal collector. If a collector increases, compare the difference with the qualifying Gold values. Repeat only as long as the feature naturally continues.

This observation can distinguish collecting on landing, collecting after every spin and collecting only newly arrived symbols. It cannot prove that every certified build behaves identically. Publish the result with game ID, version, help wording and date.

If more than one Royal collector appears, track each separately. Do not assume they share an accumulated balance. The final history credit remains the authority for settlement, while the worksheet explains how the feature reached it.

Original-versus-Dice accessibility

The original relies on coin type and reel position; Dice adds several bright colours. Test both in greyscale and under reduced brightness. A Royal object should remain distinguishable from a regular Gold object through shape, label or position. Colour alone is a weak accessibility cue.

On mobile, rotate the screen during demo mode and confirm that the attempt counter, collector totals and all nine positions remain visible. Do not perform that test with a paid feature in progress if rotation risks reloading the game.

Correction procedure

If Endorphina changes one version, update only that column. Preserve the other page’s facts and the earlier check date in editorial notes. A change from Pending to Approved for Dice, for example, would not alter the original’s volatility or symbol hierarchy.

Readers reporting an error should provide the exact official URL or live help screen, product ID and observation date. Screenshots without a version name are insufficient because the two builds share the same headline RTP and dimensions.

Final assessment

Crown Coins is a useful version-control exercise disguised as a simple three-reel game. The shared Royal Treasury framework makes the two editions comparable, while different volatility, symbols and status make merging their evidence unsafe.

Identify the build first, document collector timing second and reconcile the final credit last. A preset spend limit remains more important than a collector that appears close to filling the grid.

Official and related sources

• Crown Coins official page
• Crown Coins Dice official page
• Endorphina catalogue guide
• Review methodology
• Responsible gambling
• 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.