Super Sweets Sticky Wild and ticket rules

Betsoft lists Super Sweets as live from 15 January 2020 with five reels, ten paylines, 95.06% RTP, medium/low volatility and a 22.08% hit rate. Sticky Wilds can appear anywhere and each triggers one free spin; several Wilds can therefore produce several spins.

Candy Surprise appears on reels two, three and four and reveals either a respin or a Golden Ticket. Three tickets award five free spins, with the ticket positions turning into Sticky Wilds for the bonus.

Verified specification

Field	Official value	Live check
Listed date	15 January 2020	Deployed build
Reels	5	Visible row count
Paylines	10	Line map and direction
RTP	95.06%	Active profile
Volatility	Medium/Low	Studio label
Hit rate	22.08%	Not net-profit frequency
Ticket trigger	3 tickets	Five free spins
Surprise reels	2, 3 and 4	Revealed outcome

Super Sticky Wilds

A Sticky Wild can land anywhere and triggers a single free spin. The more Sticky Wilds appear, the more free spins are awarded. Record Wild count, coordinates and awarded spin count before the respin begins.

The key question is how long each Wild remains sticky. Capture every respin grid and mark carried positions. If a new Sticky Wild lands during a free spin, record whether it awards another spin and whether earlier Wilds remain.

Do not use the word “retrigger” unless Help applies it. The public description confirms one spin per Wild but does not state every queue and overlap rule.

Candy Surprise

Candy Surprise can appear on reels two, three and four. Opening it reveals either a respin or a ticket toward the free-spin feature.

Record the reel, position and pre-reveal symbol, then the revealed result. The public page does not publish the probability split, so a small sample cannot establish whether tickets or respins are more common.

If several surprises appear together, current Help must define independent or combined resolution. Save the reveal sequence and final counter instead of guessing from animation speed.

Golden Ticket free spins

Collecting three Golden Tickets awards five free spins. The three ticket positions transform into Sticky Wilds for the duration of the bonus rounds.

Save the ticket coordinates at trigger and verify that the same three positions become Wild. Number all five spins and mark any additional Sticky Wilds or Candy Surprise events according to Help.

The provider page does not state retrigger rules, maximum added spins or whether collected tickets persist between paid rounds. Do not describe a persistent meter without live evidence.

At feature end, confirm the ticket-derived Wilds disappear before the next paid round. A replay after reconnect should be checked against server history to avoid duplicate interpretation.

Paylines and paytable

Ten paylines make the route map manageable but still essential. Capture direction, matching length, symbol values and Wild exclusions from current Help.

Trace every Wild-assisted line through the saved grid. A Wild may trigger a respin and participate in a normal line award; record those consequences separately.

The public product page omits the stake range, maximum win and complete paytable. Third-party values are not substitutes for primary deployed rules.

RTP and session interpretation

The published RTP is 95.06%, volatility medium/low and hit rate 22.08%. RTP is long-run theoretical return, while hit rate can include awards smaller than the stake.

Maintain columns for paid stake, ordinary line win, Sticky Wild count, free respins, tickets and final credited value. This shows whether apparent activity translated into a net gain or loss.

Short sessions can verify how spins are queued but cannot validate the long-run percentage or reveal hidden probabilities.

Mobile and interruption checks

On mobile, confirm all Sticky Wild positions and ticket icons remain readable. Candy Surprise should identify its result with more than colour or animation alone.

Close only after a settled result, reopen and compare queued spins, ticket state and balance. Preserve the round identifier if the display differs.

Check Help legibility, focus state, reduced motion and contrast. The final award must remain available even if animation is disabled.

Evidence checklist

• Match title and Betsoft provider.
• Confirm 95.06% in active Help.
• Capture all ten paylines.
• Record each Sticky Wild coordinate.
• Compare Wild count with awarded free spins.
• Track carried positions across respins.
• Log every Candy Surprise reel and outcome.
• Keep ticket and respin outcomes separate.
• Save all three Golden Ticket coordinates.
• Verify five starting free spins.
• Confirm ticket-to-Wild transformation.
• Record additional feature events only from Help.
• Preserve round IDs after reconnect.
• Leave stake limits unavailable until verified.
• Do not claim New Zealand access without operator evidence.

Worked feature record

When two Sticky Wilds land, write both coordinates and the displayed number of awarded spins. Draw the first respin grid with those positions highlighted, then the second. If a third Wild appears, add its coordinate and note the extra spin separately.

For Golden Tickets, use a three-slot collection row. Record how each ticket was obtained, including whether Candy Surprise revealed it. At trigger, copy the three grid coordinates into the free-spin sheet and tick them on all five results.

This evidence distinguishes a ticket collection from immediate Wild respins. It also prevents a visually similar candy symbol from being counted as a confirmed ticket without the actual reveal.

How to separate the two respin routes

Super Sweets can place the same round into two visually similar but evidentially different states. A Sticky Wild directly awards a free spin, while Candy Surprise can reveal a respin without first becoming a Wild. The session record should therefore include a cause field. Write “Sticky Wild” when the symbol itself creates the extra spin and “Candy Surprise” when the concealed outcome does so. This small distinction stops a later replay from inflating the number of Wild-triggered spins.

The counter should also be copied at three moments: before the reveal, immediately after the award and after the resulting spin settles. If two Sticky Wilds and one Surprise respin occur in the same sequence, the record should show three separately sourced spins rather than one undifferentiated feature. Compare the sequence with game history, because animation can queue effects in a different order from their settlement.

Do not treat every candy-covered position as a Surprise. Record only the symbol and reels named by Help. Likewise, a ticket revealed by Candy Surprise belongs to the ticket collection, not to the immediate-respin count. The distinction matters when checking whether three tickets were genuinely accumulated.

A five-spin ticket audit

At the start of the Golden Ticket feature, create a row for each of the five awarded spins. Copy the three ticket coordinates into every row as the initial Sticky Wild set. Add newly appearing Wilds in a different colour or column so the original ticket positions can still be identified at feature end.

For each spin, save the paid lines, Wild-assisted routes, newly awarded spins and closing counter. If the deployed rules permit extra events, note the exact Help wording beside them. The official public description establishes five starting spins and three transformed ticket positions, but it does not establish an unlimited sequence, a maximum award or a particular retrigger probability.

Finally, reconcile the total credited value with the sum of the five recorded results and any documented additions. If history supplies only one combined feature value, retain the per-spin screenshots as supporting material. This approach explains the result without presenting a small personal sample as proof of frequency or long-term return.

What a reader can verify before playing

A useful pre-play check takes less than a minute: open Help, confirm the 95.06% profile, locate the ten-line diagram and find the definitions of Sticky Wild, Candy Surprise and Golden Ticket. If any item differs from this review, the deployed Help takes priority and the difference should be dated.

The same check should identify stake units, currency and any session controls visible to that account. Those are operator settings, not facts established by Betsoft’s global product page. Keeping them outside the permanent specification protects the article from claiming a local limit or availability that was never verified.

Verdict

Super Sweets is easier to audit than many modern feature stacks because its main units are countable: Sticky Wilds, free respins and three tickets. Accuracy still depends on keeping those units separate.

The provider confirms core mechanics but not paytable values, probabilities, limits or local deployment. A good review shows precisely where live Help must complete the record.

FAQ

What RTP does Betsoft publish?

95.06%.

What does one Sticky Wild award?

One free spin.

Where can Candy Surprise appear?

On reels two, three and four.

What do three tickets award?

Five free spins, with ticket positions becoming Sticky Wilds.

Is New Zealand availability confirmed?

No.

Sources

• Betsoft, Super Sweets, 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.