Durian Dynamite — every direct Wild hit can split into the next explosion

Durian Dynamite by Quickspin is built around an interactive Wild supply and collision chain. The public page describes it as Quickspin’s first 3D-rendered game, but the practical feature rule is simpler: a Dynamite Wild landing on the reels starts the sequence.

Dynamite Wild chain reactions

The feature lets supplied Dynamite Wilds be launched onto the board. If one hits another Dynamite Wild, both explode and each splits into two Wilds. Those split Wilds land in new positions.

If a split Wild lands on another Dynamite Wild, that symbol also explodes into two and continues the chain. Resolution stops only when no explosions remain and the available Dynamite Wild supply is empty.

The sequence should be audited collision by collision. Do not count the animation twice: identify the two colliding symbols, their four resulting Wilds, their landing positions and any new direct hit.

Free Spins and picker upgrades

Three Bonus Scatters award six Free Spins. Quickspin says Dynamite Wilds are more likely during the feature than in the base game.

Before play, the Bonus Picker gives a random three to six upgrades. The possible upgrades are extra Free Spins, Durian Ammo and active Dynamite Reels. The page states that up to 30 extra spins can be collected, Durian Ammo can add up to two Durians, and Dynamite Reels increase the number of reels able to produce the feature symbols.

Evidence limits

The short HTML overview omits numerical return and stake fields, while its linked supplier sheet provides reference values discussed below. A complete active reel layout, pay evaluation and operator maximum still need deployed help rather than inference from promotional artwork.

Quickspin’s page does not confirm availability at a New Zealand casino. Feature documentation and local operator access require separate evidence.

Frequently asked questions

Verified feature sequence

Quickspin describes a supply of Dynamite Wilds that can be launched onto the grid. A direct hit between Dynamite Wilds makes both explode and each split into two Wilds, producing four new landing positions. A split Wild that lands on another Dynamite Wild causes another two-Wild split. The sequence ends only when there are no unresolved explosions and the supply is empty.

Three Bonus Scatters award six Free Spins. The picker gives a random three to six upgrades across extra spins, Durian Ammo and active Dynamite Reels. The page states up to 30 extra spins, up to two added Durians and an increased number of reels that can produce feature symbols.

The short HTML overview omits layout, line count and numerical return or stake fields. Its linked supplier sheet provides a reference model discussed below, including an internal RTP discrepancy. Active pay evaluation, operator limits and New Zealand access still need deployment evidence.

Supply ledger

Record the number of unlaunched Dynamite Wilds before every action. Assign an ID as each enters the grid. A launch reduces the supply by one; a collision creates new split Wilds but should not be confused with new ammo unless the live rules explicitly add it.

The chain ends only when both conditions are true: supply equals zero and no explosion remains pending. Stopping after the last launch while secondary collisions are unresolved would truncate the feature.

Collision tree

Represent every direct collision as a node with two incoming Dynamite Wilds and four outgoing split Wild positions. If an outgoing Wild hits another Dynamite, attach a child node. This tree prevents the same animated explosion from being counted twice.

Record coordinates and timestamps. Several effects can overlap visually, so the server event order is more reliable than the sound sequence.

Direct versus secondary hit

The original launch can collide with a Dynamite already on the reels. After splitting, one of the new Wilds can cause a secondary hit. Both use the documented split rule, but their origin differs. Keep generation numbers in the ledger.

A Wild landing without hitting another Dynamite ends that branch. It may contribute to a reel win under the paytable, but it does not create another split solely because it is Wild.

Bonus Picker

The picker awards three to six upgrades. Record each selected upgrade rather than only the total count. Extra Free Spins, Ammo and Dynamite Reels modify different parts of the feature and are not interchangeable.

Up to 30 extra spins is a published ceiling, not the normal picker result. Up to two additional Durians applies to the Ammo upgrade. The Dynamite Reels upgrade changes eligible reel supply, not the current Wild count by itself.

Six starting Free Spins

Three Scatters award six feature spins before picker modifications. Save the original six, list extra-spin upgrades and show the resulting counter. This makes it clear which value is the trigger award and which comes from upgrades.

The provider says Dynamite Wilds are more likely in the bonus, but it does not publish comparative probabilities. Avoid turning “more likely” into an invented percentage.

Worked chain example

Suppose one launched Dynamite hits a second. Both split, producing four Wild destinations. One of those lands on a third Dynamite and creates two further Wilds; the other three branches stop. Record the first node, second-generation hit and six resulting landing events.

The illustration explains the tree and does not claim layout, frequency or payment. Actual positions must come from the real game history.

RTP and paytable checks

Open the deployed help for grid, paylines or ways, RTP, stakes, Wild substitution, launch rules, collision placement, feature payments and maximum exposure. The public 3D description is not a mathematical specification.

Do not infer overall maximum from 30 extra spins or a large collision tree. Neither establishes a prize ceiling.

New Zealand scope

Quickspin’s global page does not confirm New Zealand availability. Verify operator country terms, signed-in catalogue and the active game sheet. A demo or media pack is insufficient.

Do not bypass territorial controls. Payments and verification require operator evidence.

Mobile and accessibility

Fast 3D effects must still expose launch supply, collision IDs and remaining feature spins. Use a history or reduced-motion state so a user can follow every split without relying on sound or particle effects.

On a phone, the picker’s three upgrade types and quantities should remain visible. After interruption, compare supply, pending collisions, upgrades, counter, round ID and balance.

Support evidence

Save provider, title, version, time, stake, currency, balances and round ID. Include initial supply, every launch, collision pair, outgoing Wild coordinates, secondary hits and picker awards.

Use authenticated support and never provide passwords, authentication codes, private keys or seed phrases. Ask for the event tree and version-specific rules.

Responsible-play view

A large supply or collision chain does not guarantee a large settled win. Up to 30 extra spins is not an expected feature length. Do not increase stake because a previous chain ended quickly or the picker showed fewer upgrades.

Set fixed loss and time limits. Interactive launching creates involvement but not control over outcomes. Use a break if the urge to rebuild a larger chain encourages chasing.

Common errors

One direct collision produces four outgoing Wilds because both symbols split into two. A secondary hit creates another branch; it should not be merged with the first. The feature stops only when supply and pending explosions are both exhausted.

Three to six is the picker upgrade count, six is the base Free Spins award, 30 is an extra-spin ceiling and two is the Ammo addition ceiling. They describe different fields.

Final checklist

• Track unlaunched supply separately from landed Wilds.
• Give every Dynamite and collision a stable ID.
• Resolve four outgoing positions for a direct two-symbol collision.
• Continue secondary hits until no pending branch remains.
• Use six spins for three Scatters.
• Record three to six picker upgrades by type.
• Present 30 extra spins and two added Durians only as ceilings.
• Verify layout, RTP, stakes, maximum and local access in the live version.

Editorial conclusion

Durian Dynamite is most clearly explained as a finite supply feeding a branching collision tree. The picker modifies the supply, reel eligibility or feature length, while the server history resolves the actual chain.

That model is detailed enough for a useful review without inventing missing mathematical or operator facts.

Ammunition and reel eligibility

Durian Ammo changes the available supply, while Dynamite Reels change where feature symbols can originate. Record both before the first Free Spin. An extra eligible reel is not an extra Durian, and an added Durian does not automatically activate another reel.

The picker can award multiple upgrades of different types. Preserve the sequence and quantity so support can reproduce the starting feature state.

Extra-spin calculation

Begin with six spins from three Scatters. Add only the extra-spin upgrades displayed by the picker. Quickspin publishes a ceiling of 30 extra spins, not a 30-spin standard award. Show base and added counts separately.

If more spins are awarded during play, require a version-specific rule and event record. The public copy used here does not justify an invented retrigger.

Collision coordinate map

For every explosion, record the coordinates of both colliding Dynamites and the four outgoing Wild destinations. Give secondary collisions a parent ID. When two branches reach the same cell, preserve the server order and avoid counting a cell twice without a settlement rule.

The graph ends when every branch terminates and supply is zero. A visually quiet pause may occur before the next animation; use the event history rather than assuming completion.

Win settlement versus feature resolution

The collision tree explains Wild creation, not the value of reel wins. After all relevant landings, apply the live paylines or ways and symbol table. Keep feature-state changes and monetary awards in separate columns.

Without a published layout or line model, the public page cannot support an exact payout example. This limitation should remain visible.

Disconnection recovery

Save supply, pending node IDs, landed Wild map, upgrades, remaining spins, stake, balance and round ID. Reopen the game from the authenticated lobby and wait for settlement.

Do not launch another Durian until the previous tree resolves. A replayed explosion can represent restoration, not a duplicate event.

Interface requirements

The supply count and remaining spins should stay visible during 3D animation. A reduced-motion history should show collision ancestry and final coordinates. Picker upgrades need text labels and quantities.

On mobile, particle effects must not hide the grid or controls. The article’s diagrams should provide a static alternative and use unique IDs for branches.

Source hierarchy

Quickspin supports the collision and picker overview. The live game sheet supplies layout, RTP, stakes, paylines and settlement. The operator supplies territorial access and account history. These evidence roles are not interchangeable.

A supplier page does not confirm New Zealand access, and a casino screenshot does not prove all Quickspin versions use the same mathematics.

Direct questions

Does one collision create two Wilds? No; both Dynamites split into two, producing four outgoing Wilds. Can one of those trigger another split? Yes, if it lands on another Dynamite. Does the feature end when ammo is empty? Only when no explosions remain as well.

Are 30 extra spins guaranteed? No. Are up to two Durians the same as two extra reels? No; they are separate upgrade types.

Final publication audit

Verify three Scatters, six starting spins, three-to-six upgrades, up to 30 extra spins and up to two added Durians against the provider. Keep active layout, operator RTP, currency stakes, contractual exposure and local availability unclaimed until deployment evidence supplies them; label the supplier sheet’s numerical reference and discrepancy separately.

Test the collision tree and tables on mobile. Keep sponsored links labelled and separate from the official source.

Reader decision

The title may suit readers who enjoy following branching feature logic. It may not suit those who find fast 3D sequences difficult to audit or who interpret interactive launching as skill.

The informed approach is to understand the finite supply, set limits and rely on the server record rather than animation alone.

Collision ancestry is not final Wild occupancy

An original arithmetic example helps distinguish launches, split events and the final board. Suppose one supplied Durian, L1, hits an existing Dynamite D1. The documented direct collision creates four outgoing Wilds, W1 through W4. Assume W1 then hits another existing Dynamite D2, which splits into two further Wilds, W5 and W6, under the supplier’s secondary-hit description. No other collision occurs in this hypothetical sequence.

Ledger field	Count in this example	Evidence needed for a real round
Items launched from supply	One	Supply before and after L1
Direct collision nodes	One	L1 meeting D1
Secondary split nodes	One	W1 meeting D2
Outgoing landing events across generations	Six	W1–W4, then W5–W6
Final distinct Wild coordinates	Not established by the event count	Final grid and collision resolution order

The six outgoing events do not prove six occupied cells survive at settlement. One intermediate landing caused a later event; destinations may overlap, and the short source does not fully specify the incoming Wild’s disposition after a secondary hit. Preserve the final coordinate set rather than treating every historical destination as an additional paid position. Similarly, neither split replenishes launchable supply under the published description: one launched item stays one launch debit in this example, not three items spent or six new ammunition units.

If supply is now zero but W5 and W6 have not finished resolving, the termination condition is not yet satisfied. Once they resolve without further collisions and no supply remains, both required conditions are true. This is a logical worksheet, not a claim that a player can direct those hits or choose a profitable branch. No reel award can be calculated until the actual final board and paytable are available.

The official sheet contains a numerical mismatch

The linked Durian Dynamite sheet, visually checked on 7 October 2026, identifies duriandynamite, volatility 5 on a 1–5 scale and euro stakes from €0.20 to €100, default €1. Those euro reference fields are not automatically NZ-dollar operator limits.

Although the column headings place the fields unusually, its return rows clearly print Base Game 33.07%, Swoop 33.49%, Free Spins 29.33% and Total 96.22%. The three components add to 95.89%, which is 0.33 percentage points below the printed total. Both the source total and the arithmetic discrepancy should remain visible. Do not silently replace the supplier’s total, invent another 0.33% component, or claim the mismatch proves the active operator game is incorrect.

The payout field is labelled Max payout x bet, with 2,515.25. Unlike some other Quickspin sheets, this panel does not attach an observed-spin sample to that figure. Report its actual label rather than inventing a simulation size; the active contractual limit and settlement handling still require the loaded help.

The PDF picker says up to thirty-six Free Spins, while the current HTML specifies six starting spins and up to thirty extra. Those statements are arithmetically compatible: six plus thirty equals thirty-six total. Thirty-six is a ceiling, not the result of every picker, and it says nothing about the monetary return of those spins.

Event-log example

Use a tree table with columns for node ID, parent collision, incoming Dynamites, outgoing Wild coordinates, secondary hit and resolution status. A branch is complete only when all outgoing Wilds have landed and any child collision has resolved.

Pair the tree with a supply ledger showing each launched Durian. This reveals whether an apparent missing explosion was actually an unlaunched item or a resolved branch.

Upgrade comparison

Extra spins change feature duration. Ammo changes the number of launchable Durians. Dynamite Reels change where feature symbols can appear. Comparing them by a single “upgrade strength” number would be unsupported because they affect different state variables.

Record the picker result exactly and let the deployed game sheet explain any upgrade levels. Do not assign monetary values to unused Ammo or eligible reels.

Operator and version questions

Ask for the grid, line model, RTP, stake range, maximum exposure, picker table and disconnection procedure. Confirm whether the feature is available in the account’s territory and whether the displayed version matches the provider page.

An operator screenshot is not a universal rule. Store its date and build identifier.

Final content review

Read every number with its noun: six Free Spins, three to six upgrades, up to 30 extra spins and up to two extra Durians. Confirm that the article never calls 30 the starting feature length or two the number of Dynamite Reels.

Test diagrams with reduced motion and phone width. Keep the official source direct and editorial artwork clearly labelled.

Closing evidence statement

The provider page is enough to explain the branching collision concept and picker categories. It is not enough to calculate payout or confirm New Zealand access. A final review is strongest when that boundary remains visible alongside a precise event tree.

Final audit questions

Was every launched item deducted from supply? Was every direct collision expanded into four outgoing Wilds? Were secondary hits attached to the correct parent? Did the feature stop only after both pending effects and supply reached zero? Those questions test the published mechanic without requiring invented probabilities.

Next verify the picker: three to six upgrades, with extra spins, Ammo and Dynamite Reels treated separately. Confirm six starting spins and keep the up-to-30 and up-to-two ceilings in their proper fields.

Finally test the article on mobile, open the official source and date the review. A reader should be able to follow the whole tree without watching the 3D animation or believing that interactive launching changes the random outcome.

Keep the closing comparison factual: the game differs from an ordinary Wild feature because one collision can branch into later collisions and because a finite supply coexists with picker upgrades. That difference describes complexity, not profitability.

If the live help cannot show layout, RTP, stakes or maximum exposure clearly, leave those values unavailable and ask the operator for the version-specific game sheet. Do not estimate them from the number of Wilds on a promotional image.

What triggers the Dynamite Wild feature? A Dynamite Wild landing on the reels.

What happens when two Dynamite Wilds collide? Both split into two Wilds each.

When does the chain end? When no explosions remain and the supply is empty.

How many Free Spins do three Scatters award? Six.

How many picker upgrades are awarded? A random three to six.

Is New Zealand availability confirmed? No.

Official source

• Quickspin: Durian Dynamite

Bottom line: track supply, direct collision, split Wilds and secondary collisions in that order.

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.