Sugar Pop cascading and all-ways rule guide

Betsoft lists the original Sugar Pop as live from 20 October 2014. Its public card confirms five cascading reels, an All Ways Pay system, 97.30% RTP, low volatility and a 58.84% hit rate. It also describes speciality candy features and level-based play but does not publish their full rules in accessible text.

This page deliberately covers the original edition only. It does not import the 7-by-7 clusters, Surprise Egg, Candy Bomb or Free Spin candy rules from Sugar Pop 2: Double Dipped.

Verified specification

Field	Official value	Verification boundary
Listed date	20 October 2014	Exact build revision
Reels	5, cascading	Row configuration in Help
Pay system	All Ways Pay	Direction and symbol count
RTP	97.30%	Active profile
Volatility	Low	Studio classification
Hit rate	58.84%	Not profit frequency
Progression	Level-based	Storage and reward rules
Specialities	Candy features	Names and effects in Help

Why edition identity matters

Sugar Pop has a later sequel with materially different public rules. A review of the original must begin by matching the title, Betsoft provider, 2014 listing and five-reel cascading layout. A 7-by-7 board is evidence that a different product has opened.

Save the Help title and version string before using any rule. Do not transfer the sequel’s Candy Wild threshold, Bomb counter, Surprise Egg or Free Spin candy trigger into this page. Similar artwork is not a reliable identity check.

If an operator shortens both titles to “Sugar Pop,” use the grid shape and Help document to resolve the edition before recording results.

Cascading reel record

A cascade removes winning symbols and introduces replacements without charging a new base stake for each replacement stage. The exact evaluation order must come from current Help.

Copy the initial stopped grid, circle every contributing symbol and write the first award. Number the replacement board as cascade two, then repeat until no further win exists. The round total should reconcile with the sum of all documented stages.

The public Betsoft page does not expose the original row count, minimum combination or complete paytable in accessible text. Those fields should remain unavailable until the deployed Help is opened. Do not infer them from the sequel or a third-party screenshot.

All Ways Pay

All Ways Pay normally evaluates matching symbols on adjacent reels rather than fixed paylines, but the exact starting reel and matching length are product rules. Capture the wording and any diagram from Help.

Trace each winning route through the stopped grid. A symbol participating in several ways may contribute to several combinations according to the paytable; count the displayed ways rather than estimating them visually.

The public page does not publish a numerical count of ways. “All Ways Pay” is therefore the verified label, while a specific number remains a live-build field.

Speciality candy evidence

Betsoft’s overview confirms that the original includes speciality candy features. The accessible product copy does not name their current effects or trigger thresholds. Accuracy therefore requires the active Help panel.

Create one row for each speciality candy: displayed name, appearance rule, affected cells, immediate award, cascade consequence and persistence. Capture the board before and after activation. If the feature changes another symbol, preserve both identities.

Do not reuse descriptions of the sequel’s caramel chew, Morphing Golden Wild, Jelly Bean Cannon or Sweet Hammer unless the original Help explicitly contains the same item and wording. A related title is not a primary source for this edition.

Level-based play

The official overview states that Sugar Pop uses level-based gameplay. It does not reveal the level thresholds, rewards, persistence rules or cap in the accessible text.

Record the level meter before a paid round, the progress granted, the unlock or reward notice and any credited value. Keep account progression separate from the outcome of the cascade. A new visual item is not automatically a cash award.

Check whether progression is stored per account, device or operator session. After signing out and returning, compare the meter with the saved state. Only the deployed interface can establish whether levels reset or persist.

Paytable and unavailable fields

The official page supplies RTP, volatility, hit rate, reel style and pay-system label. It does not supply the complete symbol table, stake range, maximum win, speciality probabilities or local currency values in accessible copy.

These gaps should be displayed as verification work rather than filled from aggregators. Open Help, capture the paytable revision and attach a date. If a figure cannot be reproduced from the active rules, leave it unavailable.

The same rule applies to demo and mobile availability. Betsoft’s global Play Demo link does not prove that a New Zealand visitor or 22Bet account can access the game.

RTP and hit-rate interpretation

The 97.30% RTP is a long-run theoretical return for the published profile. Low volatility describes distribution relative to the studio’s classification. The 58.84% hit rate may count small cascade awards that return less than the stake.

Keep paid stake, first-stage award, later cascade awards, level rewards and final credit in separate columns. A round with a recorded hit can still finish at a net loss.

Do not test a few hundred spins and claim to confirm 97.30%. Short observation can validate rule presentation and settlement, not the long-run model.

Responsible session setup

Level progression can encourage continued play because an unlock appears close. A practical limit should be based on money and time before the session, not on reaching the next level. Record the stop point independently of the progression meter.

Autoplay, turbo controls and loss limits are operator settings. Describe them only if the active interface displays them. Never portray a nearly completed meter as a reason to exceed a preset budget.

Mobile and accessibility

On mobile, confirm that all reels, cascade stages and speciality indicators remain readable. A winning route should not rely only on candy colour, which can be difficult to distinguish.

Check Help zoom, focus order, reduced-motion behaviour and the visibility of the final round total. If animations are disabled, the interface must still communicate which symbols cleared and what value was credited.

After interruption, compare the final cascade and level progress with server history. A replayed animation should not be counted as a second settlement.

Evidence checklist

• Match Sugar Pop, Betsoft and the 2014 edition.
• Confirm the five-reel cascading format.
• Capture the All Ways Pay definition.
• Verify the 97.30% profile in live Help.
• Record volatility and hit-rate labels separately.
• Save every cascade stage.
• Reconcile stage awards with the final round credit.
• Name speciality candies only from this edition’s Help.
• Record before-and-after boards for each effect.
• Keep level rewards outside cascade totals.
• Capture progression persistence after reconnect.
• Leave undocumented paytable values unavailable.
• Do not claim New Zealand or 22Bet access from provider publication.

Worked evidence template

Start with a header containing title, provider, version, currency, stake and round ID. Below it, create one grid for the stopped reels and one row for every cascade. Each row needs contributing symbols, ways count, award and running total.

If a speciality candy activates, insert a separate before-and-after pair rather than treating the removal as an ordinary cascade. If the level meter moves, record that change after the monetary settlement. This chronology shows exactly which event affected the balance.

At round end, compare the calculated cascade sum with game history. Any discrepancy should first be checked for unit conversion, simultaneous ways or a separate progression reward.

Original-versus-sequel confirmation card

Before publication, place four identity fields beside the evidence: exact title, listed date, reel layout and pay system. The original should show Sugar Pop, 20 October 2014, five cascading reels and All Ways Pay. If the screen instead shows a 7-by-7 cluster grid or the Double Dipped subtitle, stop the audit and use the sequel page.

This card is especially useful when an operator lobby truncates names. It prevents attractive feature details from one edition being attached to another and gives a future editor a quick way to repeat the check.

Verdict

The original Sugar Pop has unusually strong published headline mathematics but unusually sparse public feature text. The responsible approach is to explain the cascading and All Ways framework while leaving exact candy actions to the deployed Help.

This prevents the sequel’s much richer public rules from leaking into the 2014 edition and gives readers a reliable checklist for identifying the game they actually opened.

FAQ

What RTP does Betsoft publish for Sugar Pop?

97.30%.

Is this the Double Dipped sequel?

No. This page covers the original 2014 Sugar Pop.

Does the official page confirm cascading reels?

Yes, it lists five cascading reels.

Are all speciality candy rules publicly documented?

Not in the accessible product copy; current Help is required.

Is New Zealand availability confirmed?

No.

Sources

• Betsoft, Sugar Pop, 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.