Rapunzel's Tower — Bonus Wilds stay locked until a win

Rapunzel’s Tower by Quickspin uses three rows, five reels and 20 paylines. Its two central systems share the Bonus Wild symbol but resolve differently.

Wilds stick until a win

Three or more Bonus Wilds start the feature. Those Bonus Wilds lock in place and the game respins until a winning combination appears.

The ending condition is a win, not a fixed respin count. Keep the original locked positions visible when checking the final combination.

Tower Feature

Three Scatters award ten Free Spins with the Tower Feature. Every Bonus Wild that appears adds one step to the climb. Additional Free Spins can be awarded during the ascent.

If the climber reaches the top, every remaining Free Spin uses a ×2 multiplier on all wins. The multiplier applies to the remaining portion of that feature, not retroactively to earlier spins.

Evidence limits

The short HTML overview does not expose a readable RTP or stake range. Its linked supplier sheet provides reference fields, discussed below, but neither source confirms Rapunzel’s Tower at a New Zealand casino.

Frequently asked questions

Verified rules and known limits

Quickspin describes Rapunzel’s Tower as a three-row, five-reel game with 20 paylines. Three or more Bonus Wilds trigger a hold-and-respin sequence in which those Wilds lock and respins continue until a winning combination appears. The stopping event is therefore the first qualifying win, not a published fixed number of respins.

Three Scatters award ten Free Spins with the Tower Feature. Every Bonus Wild that appears during this feature advances the climber by one step. The ascent can award additional Free Spins. If the top of the tower is reached, all wins on the remaining Free Spins receive a ×2 multiplier.

The short HTML overview omits numerical RTP and stakes; the linked sheet supplies reference values rather than proof of an active deployment. A contractual maximum, tower-step table, additional-spin schedule and New Zealand operator availability still require deployed help or operator evidence.

One symbol, two different jobs

Bonus Wilds appear in both central mechanics, but their state depends on the active mode. In the base route, three or more lock into position and cause respins until a win. In Tower Free Spins, each new Bonus Wild advances the ascent by one step. A useful ledger must begin with a mode column so one occurrence is not credited to both systems without a rule saying so.

Use B1, B2 and B3 for the Wilds that start the hold-and-respin feature, adding further IDs if the live rules allow more to appear. For Tower progress, use a separate sequence such as T1, T2 and T3 and record the step after each arrival. Stable identifiers make the shared artwork less confusing.

Do not state that a locked Bonus Wild automatically advances the tower. The public descriptions concern separate feature contexts. Likewise, a Tower Wild should not be presented as starting a base-game respin while Free Spins are active unless the deployed game sheet explicitly connects those behaviours.

Base hold-and-respin trigger

Capture the complete grid before the feature message. Confirm at least three Bonus Wild coordinates, then preserve those positions as the locked set. Record the stake, balance and round ID; subsequent respins belong to the same paid round and should not create additional debits.

The wording says three or more, so four or five visible Bonus Wilds still satisfy the trigger. Report the actual number rather than reducing every event to three. The live help should explain whether more starting Wilds change any other aspect of the sequence.

Only the Bonus Wilds are explicitly described as locking. Do not mark ordinary symbols as held merely because an animation pauses them. Compare each respin grid and rely on the game history to identify which positions were fixed.

Win-based stopping condition

The sequence continues until a winning combination appears. For every respin, record the locked Bonus Wilds, changing positions, evaluated paylines and whether a valid win settled. A respin with no win continues; the first winning respin ends the sequence under the published description.

This rule differs from a fixed three-spin or counter-based hold-and-win mechanic. Do not add a decrementing counter that the source does not describe, and do not declare the feature expired after an arbitrary number of blank respins. The server state determines continuation.

When the win occurs, map the contributing symbols and relevant Bonus Wild substitutions. Use the 20-line paytable to confirm the combination. A visually aligned set is not enough if it does not follow an active line.

Locked-position audit

Create a three-by-five grid and shade only verified locked Bonus Wild coordinates. After every respin, compare the same cells and note any newly appearing special symbols. If the deployed rules allow additional Bonus Wilds to lock, record the event and source; the public overview does not provide that detail clearly enough to assume it.

The grid should remain readable on mobile. Label reel and row rather than relying on colour. A screenshot must show the entire board, feature state and final wager, because a crop can hide a third trigger Wild or the winning line that ended the sequence.

If a connection drops, preserve the last known locked set. On restoration, compare it with the server-returned grid and avoid placing another wager until settlement appears in history.

Tower Feature entry

Three Scatter symbols award ten Free Spins. Record their coordinates, the award message and the starting counter separately from the base Bonus Wild trigger. A Wild does not substitute for a missing Scatter unless the live paytable expressly says so.

The initial tower state should be captured before the first Free Spin: current step, visible route, any milestone labels and remaining counter. This is the baseline for every later one-step movement. Do not infer the total number of steps from decorative windows or bricks if the help publishes a specific ladder.

Ten is a starting spin count, not an RTP, multiplier or guaranteed duration after all possible additions. Any retrigger through Scatters needs its own evidence; the public page highlights extra spins through the ascent instead.

One Bonus Wild equals one ascent step

For each Free Spin, record the number and coordinates of newly appearing Bonus Wilds. Advance the tower ledger by one step per qualifying symbol, matching the game’s displayed progress. If several appear together, preserve their individual order only when the interface or server log supplies it.

Do not advance the ledger for a Bonus Wild carried from an earlier visual state unless the rules describe repeated counting. The provider wording refers to each Bonus Wild that appears, so the event history should identify new occurrences.

After movement, record the new tower level, any milestone award and counter change. This produces a reproducible path from entry to summit instead of a vague statement that progress increased.

Additional Free Spins on the ascent

Quickspin confirms that additional Free Spins can be awarded while climbing. The public overview does not expose the complete milestone schedule, so obtain it from the deployed help. Record the exact tower step, written award, counter before the event and counter after it.

Do not assume that every step gives another spin or that all additions are equal. Avoid constructing a maximum number of Free Spins without the full ladder and any cap or repeated-progress rule. Where an interface label is unclear, keep the award unavailable until it is confirmed in history.

Separate the award animation from the arithmetic. A completed Free Spin may be deducted before the addition appears, producing a counter change that looks smaller unless both operations are logged.

Reaching the summit

The ×2 state begins only when the climber reaches the top. Record the specific Bonus Wild event that completes the ascent, the confirmation message and the remaining Free Spins counter. Mark all earlier feature spins as pre-summit and all later eligible spins as post-summit.

The multiplier applies to wins during remaining Free Spins. It is not retroactive: do not double wins that settled before the summit. It also should not be applied to non-winning spins or account totals outside the feature.

For each post-summit win, preserve the base line total and the doubled settlement shown by history. If another multiplier is present, the live help must establish calculation order. Never multiply values by intuition.

Worked tower timeline

Imagine a feature starting with ten spins at tower step zero. The first spin produces one Bonus Wild, so the ledger moves to step one. A later spin produces two Bonus Wilds and moves two additional steps. If a milestone then adds spins, record the played-spin deduction and milestone addition separately.

When a later Bonus Wild reaches the published summit, mark that exact event. Only wins on feature spins remaining after the summit receive ×2. This example illustrates bookkeeping, not the actual tower height, award schedule, probability or likely payout.

If the feature ends before the top, do not carry partial progress to another round unless the deployed rules explicitly provide persistence. A near-summit state is not stored cash and does not make the next feature more likely to complete.

Twenty-payline verification

Obtain the 20-line diagram from the live paytable and number the paths consistently. For the base respin’s stopping win, list the line, symbols and Bonus Wild substitutions. For post-summit Free Spins, identify the same base award before applying ×2.

A five-reel, three-row layout does not allow an editor to reconstruct all line paths reliably from artwork. Do not draw assumed diagonals or count matching symbols outside a documented payline.

Where one symbol contributes to multiple lines, preserve one coordinate with several line references. The account-history total and deployed paytable remain the authoritative settlement evidence.

RTP, stakes and maximum exposure

Open the deployed help and collect version, 20 line paths, symbol values, Bonus Wild substitution, Scatter rules, stake range, RTP configuration, hold-and-respin behaviour, tower ladder, extra-spin milestones, summit multiplier and maximum exposure. Record the operator and date.

RTP cannot be derived from ten Free Spins, 20 paylines or ×2 after the summit. Those quantities describe mechanics but not the probability distribution. Maximum exposure cannot be calculated without the complete ladder, paytable and feature caps.

If multiple RTP variants exist, publish only the one displayed in the tested build. Do not combine figures from different operators or old versions.

New Zealand availability

The global Quickspin page does not confirm that Rapunzel’s Tower can be played for real money in New Zealand. Verify the operator’s country terms, account eligibility, signed-in catalogue and matching help. A demo or provider portfolio listing is not enough.

Currency, payment methods, verification and withdrawal rules belong to the operator and require separate sources. Do not infer them from the game’s fairy-tale theme or global availability.

If local access is unverified, say so clearly and retain the page as a mechanics guide. Never recommend bypassing location or account controls.

Mobile and accessibility audit

At phone width, all fifteen grid positions, the locked Bonus Wild set, tower step and feature counter should remain visible. Portrait orientation must not crop the summit indicator or hide the final wager. Test reflow during both base respins and Tower Free Spins.

Use written labels or icons in addition to colour for locked symbols, new tower progress and summit status. Reduced-motion mode should still reveal the step change and ×2 activation. Keyboard focus must reach help, paytable and history.

After an interruption, compare mode, locked coordinates or tower step, remaining counter, summit status, balance and round ID. Allow the server to restore or settle before another wager.

Support evidence package

Save title, provider, version, operator, time, stake, currency, balances and round ID. For the base feature, add trigger coordinates, locked-set history, each respin grid and the stopping win. For the tower, add Scatters, starting counter, each Bonus Wild step, milestone awards, summit event and post-summit settlements.

Ask authenticated support for the server event log and game sheet. Identify one disputed coordinate or counter transition at a time. Never share passwords, authentication codes, private keys or seed phrases, and redact unrelated personal information.

Session control and suitability

Rapunzel’s Tower may appeal to readers who like persistent progress within one feature and can distinguish two states of the same symbol. It may be less suitable for anyone who feels compelled to continue because a tower is nearly complete or because locked Wilds have not yet produced a win.

Choose a fixed stake, money limit and time limit before play. The public rules provide no method for forcing Bonus Wilds, summit completion or a particular respin length. Increasing stake after partial progress does not make the next required symbol more likely.

Treat the stopping win and end of Free Spins as natural review points. Partial tower progress should not be valued as money or carried psychologically into a new round.

Publication checklist

• Confirm the three-by-five layout and 20 paylines.
• Record three or more base Bonus Wilds and their locked coordinates.
• Continue base respins until a documented winning combination.
• Keep base locked Wilds separate from Tower progress Wilds.
• Record three Scatters and ten starting Free Spins.
• Advance one tower step for each qualifying new Bonus Wild.
• Source additional-spin milestones from deployed help.
• Activate ×2 only after the summit and only for remaining Free Spins.
• Obtain RTP, stakes and maximum exposure from the tested version.
• Confirm New Zealand access only with operator evidence.

Editorial conclusion

Rapunzel’s Tower needs two ledgers, not one generic Bonus Wild description. The base ledger explains which symbols lock and which winning respin ends the sequence. The Tower ledger explains one-step progress, added spins, the summit event and the boundary between ordinary and doubled feature wins.

That separation makes the shared symbol understandable and prevents the ×2 multiplier from being applied retroactively. It also keeps missing mathematical and local-access details visible instead of filling them with assumptions.

Final maintenance record

Archive the base-feature grid sequence and Tower timeline with the same versioned game sheet. The evidence folder should show the review date, operator, RTP configuration where available, 20-line diagram, stake table, round histories and local-access check. This prevents a later editor from joining facts taken from incompatible builds.

Before republishing, verify that every mention of ×2 says it begins after the summit and applies to remaining Free Spins. Confirm that the base respin ending is described as a winning combination rather than a fixed counter. Recheck all FAQ answers against the body, label editorial artwork clearly and rerun the mobile and duplicate-content audits.

The finished page should allow a reader to trace either route from trigger to settlement without treating tower progress as stored value or a near-complete climb as a reason to continue. That is the practical editorial standard for this feature.

Supplier reference separates two feature contributions

The official PDF linked from the current product page identifies Game ID Rapunzel2, with capitalisation retained. It prints 96.25% total return and volatility 3.84 on the supplier’s one-to-five scale. Its euro stake reference is €0.20–€100, with a €1 default. Those are reference-model fields, not current NZD limits or a confirmed operator build.

Return-panel label in the sheet	Printed contribution
Base Game	39.35%
Feature Game	28.39%
Free Game	28.51%
Total	96.25%

The three contribution rows add exactly to the stated total: 39.35 + 28.39 + 28.51 = 96.25. Retain the supplier’s “Feature Game” and “Free Game” labels rather than pretending the panel publishes a conditional return percentage for each individual trigger. The sheet does not give enough event-frequency data to turn a contribution into a likelihood of seeing the tower or a return on entering it.

Its maximum-payout line reports 1,619 times bet observed in a billion spins. That sample observation is not a contractual maximum, a guaranteed sticky-Wild payment or a tower-summit target. The number must stay separate from a cap supplied by active help. The reference also does not fill the missing full tower-step and additional-spin milestone schedule.

An original pre-summit versus post-summit settlement example

Suppose five completed free-spin records have already been classified by a verified summit event. The first two are pre-summit and show unmultiplied awards of three and one bet unit. The following three are expressly post-summit, with unmultiplied awards of two, zero and five units. No extra modifier or cap intervenes in this invented example.

The pre-summit portion remains 3 + 1 = 4 units. The later portion receives the published ×2: (2 + 0 + 5) × 2 = 14. Together these five settlements total eighteen bet units. Doubling all five raw awards would instead produce (3 + 1 + 2 + 0 + 5) × 2 = 22, incorrectly adding four units to spins that had already settled before the summit.

This illustration deliberately does not identify a fictional tower height, climbing-spin number or milestone award. It begins with a history that has already resolved which spins are “remaining” after the summit. The exact treatment of an award on the spin that completes the ascent must likewise come from that history and versioned help; it must not be assumed to belong to the later group merely because the summit appears during its animation.

The climb counter is not a multiplier counter

If a later Bonus Wild advances the climber, record its step event independently of the monetary line award. A two-step movement is not another ×2 multiplication, and a granted extra spin is not an award equal to the value of the prior spin. Only the published summit boundary enables the stated multiplier on eligible remaining spins.

Attach the supplier identifier and the actual build to that classification. If an operator’s information screen differs from Rapunzel2, retain its dated fields rather than forcing the reference 96.25% onto the session. The reference fills an evidence gap in the short HTML, while leaving unresolved ladder and deployment details visible.

What is the layout? Three rows, five reels and 20 paylines.

What starts the sticky-Wild respins? Three or more Bonus Wilds.

When do those respins stop? When a winning combination appears.

How many Free Spins do three Scatters award? Ten.

What advances the tower? Each Bonus Wild appearing during the feature.

What happens at the top? Remaining Free Spins apply ×2 to all wins.

Is New Zealand availability confirmed? No.

Official source

• Quickspin: Rapunzel’s Tower
• Quickspin: linked Rapunzel2 supplier reference sheet

Bottom line: distinguish locked base-game Wilds from tower-progress Wilds, then apply ×2 only after the summit is reached.

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.