Sugar Pop 2: Double Dipped cluster rules

Betsoft dates Sugar Pop 2: Double Dipped to 16 February 2018. Its public specification lists a 7-by-7 Cluster Pays grid, 96.46% RTP, high volatility and a 29.66% hit rate. Winning symbols disappear and replacement candies can create consecutive clusters.

This sequel adds Surprise Eggs, an unlockable Special Candy list, Candy Wild creation, Candy Bombs and Free Spin candy clusters. These mechanics should be logged in their resolution order because one cluster can create the object that changes the next cascade.

Verified specification

Field	Official value	Live check
Listed date	16 February 2018	Build identity
Grid	7 × 7	All 49 cells
Pay system	Cluster Pays	Minimum group and adjacency
RTP	96.46%	Active profile
Volatility	High	Studio label
Hit rate	29.66%	Not profit frequency
Free-spin trigger	4+ Free Spin candies	Starting spins in Help
Bomb condition	More than 5 winning clusters	Cascade count

Reading a cluster cascade

The stopped 49-cell board should be recorded before clearing. Current Help must define the minimum cluster, whether only horizontal and vertical neighbours connect, and the value for each cluster size. Circle each winning group before symbols disappear.

Number every replacement stage. A cluster in stage one is different from a second cluster created by falling candies. The total round result is the sum of the documented stages, not the largest cluster shown on screen.

Large winning clusters can leave a Candy Wild. Betsoft states that five or more symbols in a cluster combine into that Wild. Save the original cluster size, the Wild coordinate and its contribution to later wins.

Surprise Egg and Special Candies

A Surprise Egg can appear during play. After all cluster wins settle, it opens and reveals one Special Candy already unlocked through the level system. The revealed candy activates immediately.

Record the Egg’s appearance, current level, available Special Candy list and revealed result. The official overview names examples including a caramel chew that removes one candy colour, a Morphing Golden Wild that changes shape to match a nearby candy, a Jelly Bean Cannon that removes its targets and a Sweet Hammer that clears symbols in its path.

The page does not publish the reveal probabilities or exact target-selection algorithm. Do not describe any Special Candy as equally likely. For a Golden Wild, record the matched colour and resulting cluster; for removal tools, mark every affected cell before replacements enter.

Candy Wild creation

When at least five matching symbols form a winning cluster, they combine into a special Candy Wild. Capture the group before it clears and the board after the Wild appears. Help should identify which coordinate receives the Wild when the cluster has several possible centres.

A Wild can support later clusters, but it should not automatically be counted as a Free Spin candy. Keep its substitution behaviour separate from trigger-symbol collection.

If several qualifying clusters settle together, record whether each creates a Wild. The public wording describes the threshold but not every simultaneous-cluster edge case.

Candy Bomb threshold

More than five winning clusters in a single spin leave a Candy Bomb. When no more wins remain, the Bomb explodes, clears part of the board and can award further prizes. Additional consecutive wins increase its blast size.

Maintain a cascade counter from the first win. The condition is more than five clusters, so the sixth qualifying cluster is the relevant threshold. Do not substitute “five or more.” Save the Bomb’s initial cell, blast footprint and any new winning groups created after the explosion.

The accessible official page does not specify the maximum blast size or formula for its growth. A dramatic animation does not establish how many cells should clear in every deployment.

Free Spin candy clusters

A cluster of four or more Free Spin candies triggers the free-spin mode. Each additional Free Spin candy in that winning cluster awards two extra spins. Further qualifying clusters during the feature can add spins.

Record the trigger cluster size and starting counter shown by Help. The public page establishes the +2 rule for additional trigger candies but does not state the base number of spins in the accessible copy. That value should therefore be taken from the active rule panel, not guessed.

During the feature, number every added-spin cluster separately. A Candy Bomb or Special Candy may create removals that lead to a trigger cluster; the evidence should show the complete chain.

Levels and persistent unlocks

Betsoft says players level up across spins, unlock new candies and receive level rewards, with no level cap. That is a persistent progression system rather than a single-round pay mechanic.

Capture the level before and after a session, the precise unlock notice and any reward credited. Do not infer how many spins a level needs or how progression transfers between operators. Account storage and reset behaviour belong to the deployed Help.

If a browser or device change loses the level, preserve the authenticated account state and contact support with the round history. A visual level badge alone does not prove that a reward was credited.

RTP and session interpretation

The published 96.46% RTP is a theoretical long-run value. High volatility signals uneven distribution, while 29.66% hit rate can include results below the paid stake.

Use ledger columns for stake, initial cluster value, number of cascades, Candy Wilds, Bomb activation, Egg result, free-spin additions and final credit. A level reward should be separated from the reel result.

Short play can verify the sequence and interface, not hidden probabilities or long-term return. Do not use promotional footage to estimate Surprise Egg frequency.

Mobile and continuity

On mobile, all 49 cells, cluster highlights and Free Spin candies must remain distinguishable. Colour should not be the only indicator of a selected cluster or Golden Wild transformation.

After reconnecting, compare the current level, unlocked candy list and unsettled cascade with history. If a Bomb animation repeats, verify that the server credited it once. Record the round ID before reporting an apparent duplicate.

Audit checklist

• Confirm the Double Dipped title, not original Sugar Pop.
• Match 96.46% in active Help.
• Capture the complete 7-by-7 grid.
• Save the cluster adjacency definition.
• Number every cascade stage.
• Verify five-symbol Candy Wild creation.
• Count more than five clusters for a Bomb.
• Record Bomb blast growth from Help.
• Save Surprise Egg timing and reveal.
• Keep each Special Candy action separate.
• Record the Free Spin candy cluster size.
• Apply +2 spins only to additional candies.
• Preserve level and unlock changes.
• Do not claim New Zealand deployment without operator evidence.

Worked cascade record

Start with coordinates A1 through G7. Highlight each opening cluster, total its documented value and mark the disappearing cells. After replacements settle, copy a second grid. Continue until no win remains.

If the sixth cluster creates a Bomb, write its coordinate but allow all ordinary cascades to finish before documenting the explosion. Copy the blast board and every post-Bomb cluster. If a Surprise Egg opens afterwards, begin another stage and name the revealed Special Candy.

This chronology prevents one visual sequence from being incorrectly described as a single cluster and makes the final credit independently reproducible.

Separating progression from paid-round evidence

Sugar Pop 2 can change the available Special Candy list as levels rise. That persistent state should be recorded before the paid-round grid. Otherwise a newly unlocked tool may be mistaken for a random feature that was always available.

Use two timestamps: one when the level or reward message appears and another when the next paid spin begins. Record whether the unlock changes only future Surprise Egg possibilities or immediately modifies the current board. The public page confirms that new candies join the list and that levels bring rewards, but it does not publish the exact timing for every transition.

After reconnecting, compare the unlocked list rather than only the displayed level number. A restored level with a missing Special Candy is a different continuity issue from a monetary settlement dispute. Keep both records separate when contacting support.

Verdict

Sugar Pop 2: Double Dipped combines cluster arithmetic with persistent unlocks. Its main review risk is collapsing Candy Wild creation, Bomb thresholds, Surprise Egg actions and Free Spin clusters into one vague “cascade feature.”

The official page provides strong feature evidence but not every probability, base free-spin count, paytable value or local setting. Those fields stay tied to live Help.

FAQ

What RTP does Betsoft publish?

96.46%.

What is the grid size?

Seven columns by seven rows.

When does a Candy Bomb appear?

After more than five winning clusters resolve in one spin.

What triggers free spins?

A cluster of four or more Free Spin candies.

Is the title confirmed at a New Zealand operator?

No. The provider catalogue cannot prove local deployment.

Sources

• Betsoft, Sugar Pop 2: Double Dipped, official product page, checked 9 October 2026.
• Betsoft official games catalogue, checked 9 October 2026.

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