NZ-NI-0208 · source record 6 October 2026
Pineapple Crush — follow the multiplier through every tumble
The base multiplier rises per winning group, the bonus multiplier rises per removed symbol and persists between spins. Those are two different counting rules.
Supplier sources below. Operator eligibility needs a separate check.

Pineapple Crush by Quickspin is a five-reel, three-row tumbling game with 20 paylines. Winning symbols are removed and replaced, while a progressive multiplier follows different rules in the base game and Free Spins.
Verified configuration
The official sheet lists total RTP versions of 96.01%, 94.19%, 92.07% and 87.15%, all at volatility five out of five. Its reference stake range is €0.20–€100, which does not establish NZD limits.
In 100-million-spin simulations, the listed maximum results are 7,333.95x, 7,217.45x, 7,025.60x and 6,593.90x. Keep the decimal and simulation scope rather than turning them into a rounded promise.
Tumbling and multiplier rules
After a line win, the winning symbols disappear and new ones fall into place. In the base game, the multiplier increases by one for each set of winning symbols removed.
During Free Spins, it increases by one for every winning symbol removed and does not reset between bonus spins. One large cluster of removed symbols can therefore move the bonus multiplier differently from one base-game tumble.
Free Spins and retriggers
Three, four or five Scatter symbols award seven, ten or fifteen Free Spins. During the bonus, three, four or five Scatters add three, five or seven spins.
The Gamble decision can trade an existing trigger for a chance to move up one Scatter level, potentially reaching five. Losing forfeits the current spins. Retriggered spins cannot be gambled.
Feature buy
Quickspin lists a 100x Buy Feature for entry to Free Spins. It is an immediate cost, not a promised return, and availability must be checked in the live market version.
Mobile and history checks
On mobile, confirm the total stake, current multiplier, remaining spins and tumble sequence stay visible. For a disputed win, preserve the round ID and each removal stage rather than only the final animation.
Temple of Paw uses a closely related tumble framework but different scatter and gamble limits. Do not substitute one paytable for the other. The Quickspin guide explains version verification.
Fixed paylines before the tumble
Pineapple Crush begins on five reels, three rows and 20 fixed paylines. A standard win must follow an active line according to the paytable. Matching fruit elsewhere on the grid does not turn the game into an all-ways system.
Record the paid stake, initial symbols and winning lines before any symbols disappear. The first settlement state anchors the tumble chain and makes later replacements understandable.
Wild substitutions, Scatter symbols and ordinary paying symbols have different roles. The live paytable determines which symbols can participate in a line and which only trigger features.
One paid spin, several tumble states
After a line win, the winning symbols are removed and replacements fall into the empty positions. If the new grid wins, another removal and tumble follow. The chain ends on the first grid without another win.
All these states belong to one paid spin. Label them T0 for the initial result, T1 for the first replacement, T2 for the next and so on. The account should show one wager and one combined settlement.
A replacement can create a new line using symbols that were not adjacent in the previous state. Do not carry a winning pattern forward after its symbols have been removed.
Use round history to reconstruct the chain. A final screenshot contains only the last grid and cannot prove the preceding wins or multiplier steps.
Base-game multiplier: one step per removed winning set
In base play, the multiplier rises by one for each set of winning symbols removed. The unit is the winning set, not every individual symbol within that set.
If an initial grid contains one qualifying winning group and it is removed, the multiplier advances one step for the next tumble according to the displayed sequence. If another winning set is removed, it advances again. Follow the live counter rather than applying the new value retroactively.
Overlapping paylines can make the phrase “winning set” important. Store the group removal shown by the game, not the raw number of line entries in the win table.
The base multiplier resets for the next paid spin. It does not carry across unrelated wagers.
Free Spins multiplier: one step per removed symbol
During Free Spins, the counter increases by one for every winning symbol removed. A winning group containing six removed symbols therefore moves the multiplier six steps, not one.
The bonus multiplier also persists between Free Spins. Record the value at the beginning of a spin, each removed-symbol count during its tumble chain and the closing value carried into the next spin.
This produces faster growth than the base rule and is the central mechanical difference. Do not reuse a base-game worksheet that increments only once per group.
Apply the multiplier at the timing shown by the game history. The increase normally affects subsequent tumble evaluation rather than rewriting an award that was already settled, but the active paytable is authoritative.
Counting removed symbols accurately
For every bonus tumble, mark the coordinates removed and count unique symbols. A symbol that contributes to several overlapping lines is still one removed grid position for the multiplier step.
Create columns for starting multiplier, removed positions, increment, ending multiplier and tumble win. This prevents overlapping line records from inflating the symbol count.
Scatter symbols should be counted only when the documented bonus rule treats them as part of a winning removal. A Scatter used solely for retriggering is not automatically a multiplier increment.
When animation is too fast, use the server history rather than estimating the number of exploding fruit.
Three-Scatter entry
Three Scatter symbols award seven Free Spins. Save the initiating reel positions and transition screen. The feature starts with its persistent multiplier state as defined by the help.
Seven is the starting count, not a minimum number of winning spins. Empty Free Spins can occur and still consume the counter.
This trigger can be offered in the gamble route, allowing a risk for the four-Scatter tier. Record the current award before any decision.
Four- and five-Scatter entry
Four Scatters award ten Free Spins, while five award fifteen. These are direct starting tiers from the paid result and can also be reached through a successful gamble from the lower tier.
Write the actual trigger count and origin—natural or gambled. A ten-spin feature created by a successful gamble still needs the prior decision recorded because the original seven-spin award was placed at risk.
Five Scatters are the highest initial tier documented for Pineapple Crush. Do not import Temple of Paw’s six-Scatter gamble endpoint.
Retrigger additions
Inside Free Spins, three, four or five Scatters add three, five or seven spins respectively. These are additions to the remaining counter rather than a new separate feature.
Record the counter before the retrigger, the Scatter count and the counter after addition. The persistent multiplier continues through the extended feature.
Retriggered spins cannot be gambled under the official rule. A decision screen should not be expected after an in-feature Scatter event.
The added-spin values differ from the initial seven, ten and fifteen. Keep entry and retrigger tables separate.
Gamble decision
The gamble can move an awarded trigger up one Scatter level. A three-Scatter award can be risked for four, and four can be risked for five. Losing forfeits the current Free Spins.
Before choosing, the screen should show the current spins, target and loss condition. Capture those values. This is not a harmless animation or a way to add spins without risk.
If successful, update the route origin and starting count. If unsuccessful, the history should explain why no feature followed the original trigger.
Do not describe the gamble as affecting RTP or probability unless the active help publishes those figures.
Buy Feature at 100×
The provider lists a 100× purchase for direct Free Spins entry. The confirmation should display the base bet and final currency deduction. Verify the starting trigger state delivered by the active version.
The purchase is not a 100× award and does not guarantee a return equal to cost. It buys the feature route while preserving random tumble and multiplier results.
Market availability can differ. If the logged-in game omits the button, the global product page does not establish access for a New Zealand account.
Attach the purchase confirmation and resulting server round to the same evidence record.
RTP variants
The listed total returns are 96.01%, 94.19%, 92.07% and 87.15%. They represent alternative deployments. Artwork and mechanics can remain the same while the mathematical configuration changes.
Record the in-game RTP and Game ID. Do not assume the highest figure is active. The five-out-of-five volatility rating is separate and describes Quickspin’s high-variance classification.
Where the help gives mode-specific RTPs for the buy or gamble, store them separately. Do not average them into one invented number.
Simulation results
The sheet reports peak simulation results of 7,333.95×, 7,217.45×, 7,025.60× and 6,593.90× for the four configurations in 100 million spins. Preserve the decimals and the simulation label.
These are not contractual maximums or expected payouts. They cannot be converted into a claim that a similar result occurs once per 100 million player spins.
If the live help states a formal cap, that deployed rule is the appropriate maximum reference.
Round audit example
Suppose a bonus spin starts at 3× and removes five unique winning symbols. Record start 3×, increment five and carry 8× into the next documented state according to the game timing. If a subsequent tumble removes three symbols, record another three-step increase.
This example explains counting only; it is not a prediction. Actual award application must follow the active history, especially whether the new multiplier affects the current or next tumble.
For base play, the same five-symbol winning set would create one multiplier step because the unit is the removed set. That contrast should remain explicit throughout the page.
Complete worksheet
Start with Game ID, RTP, currency, stake, mode and trigger route. For each tumble, record grid state, winning lines, unique removed symbols, base or bonus increment rule, multiplier before and after, and award.
For Free Spins, add remaining-spin count, persistent multiplier and any Scatter additions. For a gamble, record offered tier and outcome. For a purchase, record confirmation price.
At settlement, compare the combined round total with the server ledger. Do not rely on account-balance subtraction where other activity can occur.
Mobile and title separation
On mobile, verify that the multiplier, tumble count, remaining spins and total stake remain visible. The history must be readable after animation ends.
Temple of Paw uses a similar engine but has cat-specific triggers and a six-Scatter gamble ceiling. Check the full title and Game ID before applying this page.
Quickspin proves the product rules, not New Zealand availability, NZD support or feature-purchase access. Confirm those operator facts separately and label the artwork as editorial illustration.
Resolving overlapping line wins
One grid can create several payable lines that share symbols. The paytable may list each line separately, but the tumble removes the underlying winning positions once. For multiplier growth in Free Spins, count unique removed grid cells rather than line entries.
Create a 5×3 coordinate diagram and shade every position removed after settlement. If one pineapple contributes to three lines, it receives one coordinate and therefore one per-symbol increment under the bonus rule. The line-pay subtotal still includes every qualifying payline according to the paytable.
For the base multiplier, the game defines the increment through removed winning sets. Use the event grouping shown by the history rather than trying to derive a group count from overlapping lines alone.
Scatter handling inside tumble chains
Scatter symbols determine initial and added Free Spins through their settled count. A Scatter appearing during an intermediate tumble should be assessed when the game evaluates that grid. Preserve the sequence rather than combining Scatter counts from several different states.
Three Scatters on one settled bonus state add three spins; a later state with another Scatter does not merge with the previous three to create a four-Scatter retrigger. Each evaluated result stands on its own.
Do not include a Scatter in the removed-symbol multiplier count unless it participates in a documented winning removal. Trigger evaluation and winning-symbol removal are different events.
Verifying timing of the multiplier
The most important audit question is when the increased multiplier begins to apply. Record the multiplier displayed alongside each tumble win and compare it with the value before removal. This shows whether the increment affects the next tumble, the current subtotal or another defined stage.
Avoid a hand calculation that applies the final multiplier to every win in the chain. A progressive meter can end high even though earlier wins were settled at lower values.
The server history should list the actual award per stage. Where it exposes only a final total, preserve screenshots of the displayed meter sequence and ask support for the event breakdown if necessary.
Publication fact checklist
Before finalising the article, verify the 20 lines, tumble behaviour, two different increment units, persistent bonus multiplier, three initial trigger levels, three retrigger additions, gamble ceiling and 100× purchase.
Check all four RTPs and retain the simulation wording. Date the provider page, sheet and deployed help. If the live Game ID differs, state the conflict rather than combining values.
The article should remain about Pineapple Crush mechanics and evidence. Casino payment terms, licences and local availability require their own operator sources and should not be filled in from the game’s tropical theme.
Final ledger reconciliation
At the end of the round, add the tumble awards using the multiplier shown for each stage, then compare the combined figure with the round-specific credit. Do not use the change in main account balance if another wager or adjustment occurred nearby.
For a bought feature, include the 100× debit and the feature credit as separate ledger entries. For a gambled trigger, include the decision outcome. This makes a low result, lost gamble or missing settlement distinguishable without relying on memory.
Archive the round ID, Game ID, RTP and source-check date together. Those fields allow a later product update to be separated from the version reviewed here.
Frequently asked questions
How many paylines are used? Twenty fixed lines.
What happens after a win? Winning symbols are removed and new symbols tumble into the empty positions.
Which RTP totals are listed? 96.01%, 94.19%, 92.07% and 87.15%.
Can Free Spins retrigger? Yes. Three to five Scatters add three, five or seven spins.
Is it confirmed in New Zealand? No. The provider page does not prove local casino availability.
Official sources
Bottom line: separate the per-winning-set base multiplier from the per-symbol bonus multiplier, and treat the gamble as a decision that can erase the trigger.
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.
Primary source and correction path
This guide separates documented product information from market availability. Check the official source and the game help inside the exact version offered before making a decision.
