NZ-NI-0371 · supplier source record

Burning Coins 40: Hot Hold rules and four-version evidence

Coloured coins unlock Bonus, Collector and Payer states across several Burning Coins builds. This guide keeps every grid, line count and RTP attached to its exact version.

Supplier sources below. Operator eligibility needs a separate check.

Original fantasy cavern with red blue and green burning coins surrounding a golden vault
Original editorial artwork representing colour-coded Hot Hold routes; it is not official game art.

Burning Coins 40 by Endorphina is a 5×4, 40-line slot with Hot Hold variations triggered by blue, red and green coin tokens. Endorphina publishes 96.12% RTP, high volatility, a €0.40–€80 reference range and Approved status. This canonical guide also covers Burning Coins 20, Burning Coins 20 Dice and Burning Coins 100 without treating them as identical configurations.

The official page lists Wild, Multiplier, Hold and Win, Pile and Jackpots. Its description names Bonus, Collector and Payer symbols, prizes up to 25× total bet, extended column prizes and jackpots up to 2,000× total bet. These are provider claims for the documented build, not a forecast or proof of New Zealand operator access.

Exact-version checklist

Before comparing versions, record the full title, grid, line count, RTP, volatility, reference range and status from each official page. Then confirm those fields again in the loaded help. A lobby label shortened to “Burning Coins” is not enough because 20, 40, 100 and Dice products can use different mathematics.

The numeral generally helps identify a line model, but it should not be used as a quality ranking. More lines can change the minimum total debit and distribution without making the return better. Use the displayed total stake rather than a guessed per-line amount.

For the 20, 20 Dice and 100 builds, quote a setting only after checking that version’s page or live help. This review will not transfer the 96.12% figure, 5×4 grid or €0.40 minimum from Burning Coins 40 to its relatives.

Forty-line evaluation

Forty fixed paylines cross the 20 visible cells. The current paytable should show each path and the required left-to-right adjacency. Capture the final grid and highlight every qualifying line once.

Scatter or token awards may be evaluated outside ordinary lines. Keep them in separate columns, then combine them only where the rules say they are added. A large flame or coin image does not create extra reel positions.

The displayed total bet is the audit base. If a symbol award says “base bet” while a Hot Hold value says “total bet”, preserve that distinction and find the game’s definitions before calculating.

Wild Fire symbol

Wild Fire appears in the main game, may stack and substitutes for ordinary symbols except Scatter and Token. Endorphina lists five Wilds at 25× base bet.

Record every occupied cell in a stack. One tall artwork can cover several rows, but each payline must still pass through the correct positions. Do not use Wild to manufacture a token trigger or Scatter combination.

The seven is described as the highest ordinary symbol, with five paying 10× base bet. This is a paytable reference rather than a hit-frequency statement.

Coin tokens and route selection

Blue, red and green coins are Tokens. The activated colour leads to one of several Hot Hold variations. Record colour, starting meter, trigger screen and exact route name.

Colour needs a secondary label for accessibility. On mobile, confirm that icon or text distinguishes the routes at reduced brightness and enlarged text. Never infer a rule solely from colour.

If several colours appear together, the official description says multiple bonus types may trigger simultaneously. Preserve the order in which states enter, modify values and settle; do not merge them into one generic bonus.

Bonus, Collector and Payer states

Bonus symbols remain fixed within the Hold state. Collector symbols absorb displayed prizes, while Payer symbols enhance existing rewards. Those verbs describe different accounting events and must not be used interchangeably.

At each respin, record locked values, new symbols, counter resets and modifications. For Collector, save the exact set collected once. For Payer, save every value before and after the enhancement so it cannot be applied twice.

Where a prize is shown as up to 25× total bet, treat the number as a ceiling for the stated item, not the expected feature return. Confirm whether it applies per symbol, event or total feature.

Extended Hot Hold and jackpots

The provider description mentions extended variations with column prizes and jackpots rising up to 2,000× total bet, including an ULTRA label. A jackpot name does not prove a network progressive pool.

Open the rules to determine whether MIN, MID, MAX or ULTRA values are fixed multiples, locally configured currency amounts or progressive. Record any changing amount with currency and timestamp.

If a column prize fills or transforms a reel, save the grid before and after. An animation spanning a column should be counted according to the final evaluated positions.

Comparing 20, Dice and 100

Burning Coins 20 and 20 Dice should be compared as separate products even when they share a line count. Dice changes the symbol set and may alter paytable values or feature presentation. Burning Coins 100 adds a denser fixed-line model and may use another minimum total bet.

Build a table from the exact official details rather than completing missing cells by pattern. Record whether each version has the same Hot Hold colours, Bonus Pop access, maximum wording and status. A family resemblance is not configuration evidence.

When switching titles, reset the stake deliberately. Interfaces can remember the previous wager, and a 100-line build can produce a different total debit even where denomination looks familiar.

RTP and volatility

The provider’s 96.12% and high-volatility label apply to Burning Coins 40 on the checked page. RTP is theoretical over many rounds, not a short-session refund. High volatility cannot tell when a coloured coin or jackpot state will appear.

Save the live RTP with game ID, operator, mode and date. If another approved value appears, report it as a deployment rather than replacing the official reference silently.

Use a conservative stake within money and time limits fixed before launch. A growing collection, empty grid or repeated near miss does not make a bonus due.

Bonus Pop and optional modes

Endorphina’s FAQ says Bonus Pop may be included but can depend on casino and jurisdiction. If visible, read the cost, delivered feature and separate RTP before acceptance.

A purchase price is a wager, not an expected return. Convert the multiple into the actual account-currency debit and count it immediately against the session limit.

If Bonus Pop is absent, document that deployment. Do not assume a technical fault or use another operator’s interface as proof.

Demo and mobile checks

The official page links a demo and describes cross-device access. Demo mode helps locate line maps and practise reading Hold states, but it cannot prove funded access, NZD support or identical mathematics.

On mobile, check that all four rows, respin counter, values and total bet remain visible. Test portrait, landscape and enlarged text. A close control should remain reachable above animated columns.

After a connection loss, inspect round history before spinning again. Save round ID, starting balance, debit and settled credit.

New Zealand evidence boundary

Endorphina says availability depends on approved markets, local law and player location. Its supplier page does not establish a NZ operator’s eligibility or a title’s availability to every account.

Verify the consumer operator’s legal identity and country terms, then locate the exact build inside an authenticated lobby. Supplier B2B licensing and operator permission are separate questions.

Do not bypass location controls. If only demo access is available, label that state precisely.

Practical feature worksheet

Create one row per state: trigger, opening grid, locked values, new symbol, counter, Collector subtotal, Payer change and closing credit. Add the colour and version to every row.

This timeline makes simultaneous bonus types auditable. If the arithmetic differs from history, check wager units and event order before contacting verified support with the round ID.

Screenshots should exclude account identifiers, payment details and authentication codes.

Common questions

What RTP does Burning Coins 40 publish?

The official page shows 96.12%; live help must confirm the deployed setting.

What is the maximum published jackpot wording?

The description says jackpots up to 2,000× total bet. It is not a frequency claim or proof of a progressive cash pool.

Can Wild replace a coloured coin?

No. The provider says Wild excludes Scatter and Token.

Are all four versions available in New Zealand?

That was not verified at operator level.

Why combine the versions?

They serve one comparison intent, while the article preserves version-specific evidence and prevents thin duplicate pages.

Final assessment

Burning Coins 40 combines a conventional 40-line shell with several interacting Hold states. Its official 96.12% RTP, high volatility and 2,000× jackpot wording are useful references, but the key task is documenting colour, Collector and Payer order.

Keep the four family versions separate, verify the exact wager unit and never turn a burning meter into a prediction. The loaded help and server history remain decisive for a specific round.

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