Volcano Riches — resolve every eruption before the grid pays

Volcano Riches by Quickspin uses a 5×4 grid. A landed Volcano Wild erupts before evaluation and places between two and five additional Wilds in neighbouring positions.

Base-game eruption sequence

Volcano Wilds appear on reels two and four. Only one can land directly during a base-game spin, but its eruption may create another Volcano Wild, which then erupts in turn. An erupting Wild may replace any neighbouring symbol, but it does not overwrite another Wild already placed by an eruption.

The Volcano Wild feature and Free Spins cannot trigger in the same base-game spin. That means the event type should be identified before any chain is reconstructed.

Free Spins

During Free Spins, wins are evaluated left to right and right to left. Up to two Volcano Wilds can land directly in one Free Spin; they act independently and can each start another eruption chain. The official page states that Free Spins do not retrigger.

Evidence limits

The public page does not expose a readable RTP, stake range or full Free Spins trigger table. It does not confirm New Zealand casino availability.

Frequently asked questions

Verified mechanic map

Quickspin describes a five-reel, four-row grid. Volcano Wilds are associated with reels two and four. When one lands, it erupts before wins are evaluated and places between two and five additional Wilds in neighbouring positions. An eruption can generate another Volcano Wild, creating a further eruption that must also resolve before evaluation.

In the base game, only one Volcano Wild can land directly on a spin. A generated Volcano Wild is a separate event and does not contradict that direct-landing limit. A symbol already replaced by an eruption Wild is protected from being overwritten by another eruption. The product description also separates the Volcano Wild feature from the Free Spins trigger: both cannot start on the same base-game spin.

During Free Spins, as many as two Volcano Wilds can land directly in one spin, and each acts independently. Wins are evaluated both left to right and right to left in that mode. The provider states that Free Spins do not retrigger. The accessible page does not provide a readable RTP, stake range, full trigger table, maximum exposure or New Zealand availability.

Direct versus generated Volcano Wilds

Give every Volcano Wild an origin label. Use D for a symbol that lands directly and G for a symbol produced by an eruption. In the base game, the direct-origin count should not exceed one; in Free Spins it may reach two. Generated symbols are counted separately because each can begin another branch of the chain.

This distinction prevents a common reporting error. A final grid may contain several Volcano Wilds even though only one landed directly in the base spin. Saying that several “landed” would misstate the rule. The event ledger should show the original landing, the number of ordinary Wilds it created, and any generated Volcano Wild that continued the sequence.

Where two direct Volcano Wilds appear in Free Spins, assign them D1 and D2. Record their eruptions independently, even if their neighbouring areas overlap. The live help and server event order should determine which branch resolves first and how protected Wild positions are handled.

Building an eruption tree

Represent the feature as a tree rather than one flat list. The root is the directly landed Volcano Wild. Its child nodes are the two-to-five neighbouring Wild placements. If one child is itself a Volcano Wild, open a new branch under that child and record its placements. Continue until no generated Volcano Wild remains unresolved.

For every node, save reel, row, origin, eruption order and final symbol state. This makes it possible to reconstruct a long chain without counting the same cell twice. It also preserves the difference between an ordinary Wild placed by an eruption and a new Volcano Wild capable of erupting.

The published range of two to five applies to additional Wilds from an eruption. It does not establish the total number of Wilds after a chain because a generated Volcano Wild may continue the process. Nor does it provide chain probabilities or a mathematical maximum; those require the deployed rules and finite-board interaction details.

Neighbouring-position check

The public copy uses the concept of neighbouring positions but does not expose a complete placement priority for edges, corners or occupied cells. Therefore map the actual affected coordinates and consult the live help before defining adjacency as orthogonal, diagonal or another pattern. Do not infer wrapping from the far side of the grid.

When an eruption occurs beside an existing Wild, mark that cell as protected because an eruption Wild does not overwrite another eruption Wild already placed. Record where the feature chose alternative positions, if any, but avoid turning one observed pattern into a general rule unless the help confirms it.

A clear diagram should show the source Volcano Wild in one style, newly placed ordinary Wilds in another, generated Volcano Wilds in a third, and protected prior Wilds with a lock marker. Colour alone is insufficient; labels keep the diagram understandable on mobile and for colour-vision differences.

Base-game event separation

Before analysing a base spin, identify whether it contains the Volcano Wild route or the Free Spins trigger. Quickspin states that the two features cannot trigger in the same base-game spin. The round record should therefore contain one event-type field and flag any apparent simultaneous trigger for comparison with the server log.

Do not assume that visible Scatter-like symbols during an eruption start Free Spins. The settled event must match the documented trigger rules in the game help. Likewise, an eruption animation is not a separate paid spin and should not create an additional stake debit.

If the interface appears to show both routes, preserve the initial grid, every replacement and the final message. Ask support which symbols were part of the original stop and which were generated after the feature path had already been selected.

Free Spins chain audit

During Free Spins, record whether zero, one or two Volcano Wilds landed directly. With two, keep separate trees and merge them only at the final grid. Each can independently generate another Volcano Wild, so a single animation sequence may contain branches from both roots.

After every branch ends, preserve the final symbol coordinates and evaluate wins in both published directions. A line that pays right to left should be labelled accordingly rather than duplicated as a left-to-right event. Use the actual paytable to determine valid combinations and symbol values.

The provider says Free Spins do not retrigger. A Bonus symbol appearance should therefore not be reported as a new Free Spins award unless the deployed help documents another distinct mechanic. Keep the starting spin count and remaining counter, but do not add an invented retrigger.

Bidirectional win evaluation

Both-way evaluation is a Free Spins rule in the public description. Build two result columns: left-to-right and right-to-left. A combination that is identical in both directions must be handled according to the live paytable, not automatically counted twice. The event history should supply the settled amount.

Do not apply bidirectional evaluation to the base game merely because the same symbols appear. Mode matters. Record whether the round is base or Free Spins before checking direction, and keep any multiplier or special feature adjustment in a later calculation column.

The term “both ways” does not identify the number of paylines or ways. Those are configuration facts that must come from the deployed help. A five-by-four layout alone cannot supply the correct denominator or number of possible combinations.

Worked chain example

Consider a base-game record in which D1 lands on reel two and produces three neighbouring Wilds. One of those is G1, a generated Volcano Wild. G1 then creates two additional Wilds while leaving an already placed Wild untouched. The ledger contains one direct origin, one generated origin and five placement events, subject to the actual server history.

Only after G1 finishes is the final grid evaluated. The example explains sequence and naming; it does not claim that those coordinates, counts or outcomes are typical. If D1 instead produced no new Volcano Wild, the tree would end after its first two-to-five placements.

For a Free Spin with D1 and D2, open two roots, resolve every branch, then apply both-direction evaluation to the final state. Never calculate a win from an intermediate grid because a later eruption can still change neighbouring symbols.

RTP, stakes and maximum exposure

The official overview does not expose these values in readable copy. Open the deployed game help and record version, RTP configuration, stake range, paytable, Free Spins trigger, starting counter, direct-landing limits, adjacency rule, chain order, protected-cell rule, directional evaluation and maximum exposure.

Do not derive RTP from volatility, eruption counts or a sample of rounds. Two-to-five additional Wilds describes feature output, not return percentage. A long chain does not establish the title’s maximum payout because symbol values and valid combinations are still required.

If the game help offers multiple RTP configurations, attribute the displayed value to the inspected operator and date. Do not combine one build’s return with another build’s stakes or feature rules.

New Zealand evidence boundary

The global Quickspin page confirms the game description but does not prove real-money availability in New Zealand. Local confirmation requires current operator country terms, a signed-in lobby listing, account eligibility and a matching deployed game sheet. A demo, search snippet or provider catalogue entry is insufficient.

Currency, deposits, withdrawals, identity checks and complaint routes are operator matters. No game-feature page can confirm them. If access cannot be verified, state that clearly and keep the article useful as a mechanics guide.

Do not recommend bypassing geographic controls. Availability may change, so preserve the date and recheck the operator evidence during editorial updates.

Mobile and accessibility checks

On a phone, the complete five-by-four grid must remain visible enough to distinguish reels two and four. Eruption origin, generated Volcano Wilds and protected placements need persistent markers or history entries after motion ends. Test portrait, landscape and reduced-motion settings.

Keyboard users should be able to reach help, paytable and round history with visible focus. Screen-reader labels should identify origin type and coordinates where the interface exposes them. A rapid lava animation cannot be the only explanation of chain order.

After an interruption, compare mode, stake, direct origins, unresolved generated branches, final grid, remaining Free Spins, balance and round ID. Wait for server settlement before placing another wager.

Dispute evidence package

Save title, provider, version, operator, date and time, currency, stake, balances and round ID. Add the initial grid, event-type selection, direct Volcano Wild coordinates, every eruption branch, protected positions, final grid, evaluated directions and settled amount.

For a chain-order dispute, ask authenticated support for the server event sequence and configuration. Identify one questionable placement by coordinate instead of sending only a video. Never provide passwords, authentication codes, private keys or seed phrases.

Responsible comparison

Volcano Riches may appeal to readers who enjoy state chains and can follow a multi-step result. It may be less suitable for anyone who interprets a generated Volcano Wild as evidence that another chain is “due”. Each spin and eruption follows the game’s random system; prior branch length provides no published prediction for the next round.

Choose a fixed stake, spend limit and time limit before play. Do not increase the wager after a short chain or continue because a previous eruption nearly reached a preferred symbol. The feature’s expanding presentation does not create a recovery strategy.

Publication checklist

• Confirm the five-by-four layout and inspected version.
• Label direct and generated Volcano Wilds separately.
• Apply the one-direct base limit and up-to-two Free Spins limit to the correct mode.
• Record two-to-five placements for each eruption without double-counting cells.
• Preserve protected eruption Wilds.
• Finish all branches before evaluating the grid.
• Apply both-direction evaluation only during Free Spins.
• State that Free Spins do not retrigger.
• Source RTP, stakes, paytable and maximum from live help.
• Confirm New Zealand access only through operator evidence.

Editorial conclusion

The game is best explained as a dependency tree. A final result cannot be audited from the first eruption alone because generated Volcano Wilds may create further branches. Separating origins, placements and protected cells produces a reliable account of the round.

A complete review should resist turning visual intensity into probability claims. The verified rules explain where Volcano Wilds appear, how many neighbouring Wilds one eruption creates, how chains continue and how Free Spins change direct landings and win direction. Missing return, stake and local-access facts remain explicitly unresolved.

Final round-reconciliation worksheet

The first row should contain the paid wager and untouched grid. The next row identifies the active route: base-game eruption or Free Spins. Each later row holds one Volcano Wild event with origin type, source coordinate, two-to-five output count, destination coordinates and any protected Wild. The last row contains only the final board and settled win.

This layout prevents intermediate combinations from being mistaken for final payouts. It also shows why the direct-landing cap and the total number of Volcano Wilds can differ. A generated symbol belongs in the tree even though it was not part of the initial reel stop.

For Free Spins, add columns for remaining counter and evaluation direction. Confirm that a right-to-left award belongs to that mode, and note that no retrigger was credited. Where two direct roots exist, retain both identifiers through the final merge rather than attributing the whole chain to whichever animation appeared first.

Questions for the deployed help

The final fact check should answer: what triggers Free Spins, how many spins begin the feature, which positions count as neighbours, what happens at edges, how overlapping eruption branches resolve, whether generated Volcano Wilds have any chain limit, how both-way wins are de-duplicated, and which RTP and maximum exposure apply. The public overview alone does not answer all of them.

If an answer is absent, say so in the article and avoid an estimate. This is particularly important for theoretical maximums: a finite grid does not let an editor calculate the approved maximum without symbol values, win rules and feature caps.

After the worksheet is complete, compare its total with account history and retain a dated copy. The goal is not to prove that an eruption was generous or disappointing; it is to show exactly how the recorded round moved from one direct landing through every generated branch to a single settled result.

What is the layout? Five reels and four rows.

Where do Volcano Wilds appear? Reels two and four.

How many additional Wilds can an eruption create? Between two and five.

Can an eruption create another Volcano Wild? Yes.

Do Free Spins pay both ways? Yes.

Can Free Spins retrigger? No.

Is New Zealand availability confirmed? No.

Official source

• Quickspin: Volcano Riches

Bottom line: finish the entire eruption chain, then evaluate the board in the direction rules active for that mode.

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 Quickspin, 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.