Thai Blossoms sticky Wild rules and evidence

Thai Blossoms is listed by Betsoft as live from 11 November 2021. The official record gives five reels, 100 paylines, 96.21% RTP, medium volatility and a 19.77% hit rate. Lotus Wilds stack and remain sticky for two spins after participating in a win.

Three or more Elephant symbols trigger free spins with an immediate scatter payout. During the feature, sticky Wilds persist until its end. Betsoft also documents a Buy Feature button, but its price, local availability and RTP impact are not stated publicly.

Verified specification

Field	Official value	Check in loaded Help
Listed live date	11 November 2021	Build revision
Reels	5	Visible grid
Paylines	100	Line map and direction
RTP	96.21%	Active profile
Volatility	Medium	Studio label
Hit rate	19.77%	Not profit frequency
Base Wild hold	2 spins after a winning combination	Counter order
Free-spin trigger	3+ Elephants	Spin count and scatter pay

One hundred line routes

The large line count makes visual guessing unreliable. Use Help to determine whether all 100 lines are fixed and how they cross the five reels. For a settled result, rely on the line breakdown rather than trying to infer every route from animation.

Record total stake and any line-unit value. A symbol prize expressed per line should not be compared directly with a total-bet multiplier.

The 19.77% hit rate includes provider-defined credited results and does not promise profit. Medium volatility and 96.21% RTP are long-run model descriptions, not timing signals.

Base-game sticky counter

A stacking Lotus Wild remains sticky for two spins when it forms part of a winning combination. Its appearance alone is not enough; participation in a win is the documented activation condition.

Record the activation grid, winning line and counter displayed after settlement. On each following spin, note whether the counter decreases before or after evaluation. Betsoft states that a new win formed by an already-sticky Wild does not increase its remaining counter.

That non-extension rule prevents repeated wins from refreshing the hold. If a separate new Wild activates, track it independently by reel and position rather than using one combined counter.

Elephant scatter and free spins

Three or more Elephant symbols trigger free spins and an instant scatter payout. Record the number of Elephants, scatter multiplier, awarded spins and transition under the same paid-round ID.

The accessible page does not publish the starting spin count or retrigger rule. Those facts remain unavailable until Help is checked. Do not import them from another sticky-Wild title.

During free spins, Wilds remain sticky until the round ends. Record their landing spin and coordinates. Unlike the base game, persistence is tied to feature duration rather than a two-spin counter.

Feature-state map

Create columns for spin number, remaining spins, new Wilds, previously sticky Wilds, winning routes and credit. This makes it clear which Wilds entered on each step and prevents later positions being attributed to the opening screen.

If free spins retrigger, note the counter before and after the event. If Help does not permit retriggers, do not infer one merely because Elephant symbols remain visible.

At feature end, verify that all sticky state clears before the next paid spin. If any Wild persists, preserve the history and game ID because that would be a materially different rule.

Buy Feature boundary

Betsoft confirms a Buy Feature button that provides instant access to free spins. It does not publish cost, enabled markets, return profile or guaranteed starting state on the accessible page.

Where enabled, Help must show the exact price as a multiple or currency amount, the separate RTP if any and what is guaranteed. A purchase is a wager, not a bonus from the operator.

Do not state that the option is available in New Zealand. Feature-buy controls may be disabled by territory or operator even when present in provider documentation.

Paytable and maximum limits

The complete symbol table, stake range and maximum win are absent from public text. Capture every paytable page, award unit and any maximum-exposure statement from the deployed client.

If several RTP settings appear, list each coherent configuration and identify the active one. Never combine a feature price from one build with the return from another.

Use balance history to confirm that a feature purchase deducts the displayed amount once and that all subsequent free spins carry no additional stake.

Mobile continuity

At 390-pixel width, the 100-line result breakdown, each sticky counter, remaining spins and total stake must remain accessible. Stacked Wilds should not hide their own counters.

Rotate before play and confirm sticky positions survive orientation. On interruption, history should recover the feature state without another wager.

Wild activation needs a numeric or shape cue in addition to colour. Reduced motion must preserve counter changes and the final settlement.

Demo and territorial scope

Betsoft provides an official demo link. Sponsored routes here are not that demo. Studio documentation does not prove New Zealand access or a listing at 22Bet.

Check the authenticated lobby, territorial rules and loaded Help. If Buy Feature is absent, state that it was absent in the tested deployment rather than claiming the title lacks it globally.

Reader fit

Thai Blossoms may suit readers who enjoy persistent-board states and can track multiple counters. The base and feature persistence rules are distinct and reward careful record keeping.

It may not suit anyone who finds sticky states encourage chasing. A Wild with one spin remaining is not stored value and should never justify raising or extending the budget.

Evidence checklist

Multi-Wild counter example

Suppose a new Lotus Wild lands on reel two and helps form a winning line. Label it A, record its coordinate and copy the counter shown after settlement. On the next paid spin, a second Wild on reel four may join another win; label that position B. The two objects entered the sticky state at different times and must not be treated as one feature.

For the following spin, record A and B before evaluation, then capture their counters afterwards. If A helps form another win, Betsoft’s rule says its remaining sticky counter is not increased. The ledger should therefore show the ordinary countdown rather than a reset to two. A new Wild can still activate separately if it meets the winning-combination condition.

Use one grid per settlement so positions remain clear when stacks occupy several rows. The 100-line history should identify which routes each stack completed. Add the line awards only once, even if the animation highlights the same Wild repeatedly.

When free spins begin, close the base-game counter columns and open a feature-persistence column. Wilds in the bonus remain until the round ends, so a two-spin timer is no longer the controlling rule. Record the landing spin of each new Wild and keep it on every later grid.

If an Elephant retrigger is possible in the loaded build, document the counter change without assuming sticky positions reset. If Help omits retriggers, leave the field unavailable. At the end of the feature, confirm both the spin counter and every Wild state clear together.

For a purchased entry, add the feature cost and return profile above the same ledger. This allows a reader to compare the state machine without implying that a feature purchase improves the underlying outcome. Never combine a natural-trigger worksheet and purchase-mode RTP unless Help confirms they share one configuration.

The example is a documentation method, not a prediction. Labels A and B describe observed positions only and say nothing about the chance of another Wild appearing.

When checking a correction, compare the activation condition as well as the duration. A build where every landed Wild sticks would differ materially from Betsoft’s published rule requiring participation in a win. Keep those deployments separate instead of rewriting the condition for all versions.

Record the exact Help revision and date beside that comparison.

1. Match title and Betsoft provider.
2. Confirm 96.21% RTP and 100 lines.
3. Prove the Wild joined a win before activation.
4. Track each two-spin counter independently.
5. Record Elephant count and scatter award.
6. Map all feature-long sticky positions.
7. Document Buy Feature price and profile if enabled.
8. Preserve round IDs and final balance.

FAQ

What RTP does Betsoft publish?

96.21%.

When does a Lotus Wild become sticky?

When it participates in a winning combination, it remains for two spins.

Does another win refresh its counter?

No. Betsoft says the remaining counter is not increased.

What triggers free spins?

Three or more Elephant symbols, which also award an instant scatter pay.

Is feature purchase always available?

No. Deployment and territorial checks are required.

Is NZ access verified?

No.

Sources

• Betsoft, Thai Blossoms, 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.