Fire & Bones — trace every ball, gate and bonus pocket

Pearl o’ Plinko: Fire & Bones by Quickspin is a Plinko game rather than a reel slot. Balls launch from the top and move through pegs, Award Gates, Award Pockets, Bonus Pockets and Re-Launchers before two progressive bonus maps.

Verified configuration

The sheet lists RTP totals of 98.10%, 94.19%, 92.07% and 84.21%, volatility one out of five and a reference range of €0.10–€100. Largest simulated results in 100 million balls are 243x, 239x, 237x and 222x. This is product evidence, not New Zealand availability.

Read the path correctly

An Award Pocket pays its value and ends that ball’s journey. An Award Gate pays while the ball continues. A Bonus Pocket adds one ball to the next bonus after all current balls finish. A Re-Launcher creates three new balls from the top.

The route is physics-styled presentation governed by game mathematics. Past drops do not make an edge or pocket due.

Two bonus maps

Ship Graveyard is the first bonus and Fire Island the second. Each Bonus Pocket adds a ball to the next stage, while later progression offers larger award positions. Record how many balls enter each map; a visible Bonus Pocket without a landed ball does not count.

Extra Bet and Buy Feature

Extra Bet costs 1.5x and adds one Bonus Pocket, increasing bonus-entry opportunity. Buy Feature costs 4x for Ship Graveyard or 12x for Fire Island, launching balls directly into that bonus. Market availability varies.

The price buys a route, not a minimum return. Confirm the number of balls, active RTP and total deduction in the deployed help.

Evidence and scope

Save the round ID, number of launched and relaunched balls, gates crossed, final pockets and bonus-ball count. On mobile, make sure all pockets and values remain visible without relying on animation speed.

The provider does not establish a New Zealand operator, NZD or withdrawal rules. Compare the Quickspin guide before attributing account terms to the game supplier.

How a paid Plinko round is structured

A paid round begins when one or more balls are released at the top of the active map. Each ball travels through a field of pegs and can interact with award gates before eventually entering a terminating pocket or another documented feature. The settlement record must include all balls created during the same round, including balls added by Re-Launchers.

The moving animation is a presentation of the certified game process. A ball’s visible bounces do not establish a player-controlled skill element. There is no reliable way to infer a due pocket from earlier paths. Review the settled event list and round history rather than estimating probabilities from where a ball appears to travel on screen.

Keep the original paid ball count separate from the total number of balls resolved. If one ball reaches a Re-Launcher, three additional balls begin at the top. Those three belong to the original paid round and must be included when reconciling gates, pockets and the final credit.

The useful audit sequence is launch, gate events, terminal pocket or feature event, any re-launches, then bonus entry after all current balls have stopped. This sequence prevents a mid-animation Bonus Pocket from being mistaken for immediate bonus play while other balls are still moving.

Award Gates versus Award Pockets

An Award Gate pays its displayed award when a ball passes through it, but the ball continues down the map. One ball can therefore produce a gate award and later a pocket award. Record both events against the same ball identifier.

An Award Pocket is terminal: when a ball enters it, the pocket value is awarded and that ball’s journey ends. Do not expect the ball to continue into another pocket. The terminal nature of the pocket is the main accounting difference between the two award types.

For a multi-ball round, create one row per ball. Columns can include launch source, gates crossed, gate subtotal, final pocket and pocket award. Add the rows only after all movement has settled. This produces a transparent result without attempting to reverse-engineer the animated physics.

Displayed values should be read in the units defined by the live paytable, normally multipliers of the base bet. Convert to currency once using the documented stake. If the interface already displays currency, retain both the multiplier event and the credited currency result where available.

Bonus Pockets and delayed entry

A ball landing in a Bonus Pocket adds one ball to the next Bonus Game. The bonus begins only after all balls currently active on the map have finished. This delay allows more than one Bonus Pocket to be collected in a single paid round.

Count successful landings, not the number of Bonus Pockets visible on the board. A pocket is an opportunity until a ball actually terminates there. If two balls land in Bonus Pockets, the next stage should begin with two bonus balls under the documented rule.

Preserve the transition screen or round-history entry that states the number of awarded bonus balls. It is the bridge between the base map and Ship Graveyard or between bonus maps. If the count differs from your notes, review whether a ball merely passed near a pocket or was re-launched instead.

Bonus entry is part of the same round settlement. Do not treat the bonus balls as free promotional spins or as a separate wager. They were created by the outcome of the paid route or by an explicitly priced Buy Feature.

Re-Launcher accounting

When a ball enters a Re-Launcher, three new balls are released from the top. The original ball has completed its path at the Re-Launcher; the three replacements become new paths in the same round. Label them as children of the triggering ball so the total can be reconstructed.

Re-launched balls can themselves interact with gates, award pockets, bonus pockets and other features according to the active map. The official description should be followed for any limit or map-specific restriction shown in the live help. Do not assume an unlimited recursive chain solely from the three-ball wording.

The round total is not simply the final pocket values of the originally purchased balls. It includes gate awards and outcomes created by all documented re-launches. A transaction log is particularly useful on mobile, where several balls and flashes can overlap.

If a result looks inconsistent, count the number of launch events first. Missing one three-ball re-launch can explain several apparently unexplained awards in the final total.

Ship Graveyard: the first bonus map

Ship Graveyard is the first named Bonus Game. A standard route can reach it by collecting Bonus Pockets on the preceding map, while the documented Buy Feature can launch the feature directly for 4× the base bet. The number of balls entering the map remains the key starting fact.

Use a fresh per-ball table for Ship Graveyard rather than carrying base-map gate positions forward. The bonus has its own layout and award opportunities. Record every award gate, terminal pocket, additional Bonus Pocket and Re-Launcher encountered on this map.

If the first bonus creates balls for the next stage, store that count separately from awards already earned. The count is not yet a Fire Island cash value; it is the number of routes that will be resolved there after the current balls finish.

The 4× purchase is a route price, not a stated minimum payout. Its value lies in direct access to the first bonus configuration. Check the live confirmation for the actual stake deduction and number of starting balls before accepting it.

Fire Island: the later map

Fire Island is the second bonus destination and contains the later-stage award layout. The official materials describe larger award positions on the progression, but the page should not convert that into a guaranteed improvement for any single purchased round.

A standard route reaches Fire Island through successful Bonus Pocket landings in the earlier stage. The 12× Buy Feature provides direct access. Record whether entry came from progression or purchase because the starting screen and account deduction provide different evidence paths.

As with the other maps, count all balls, gates, pockets and re-launches. Do not add the 12× purchase price to the award or describe it as a multiplier won. It is the stake paid for that route.

When comparing Ship Graveyard and Fire Island, compare map structure and entry price, not a small sample of outcomes. The RTP configuration is a long-run property and individual Plinko paths remain variable.

Extra Bet configuration

Extra Bet costs 1.5 times the base stake and adds one extra Bonus Pocket to the active map. Before selecting it, verify the total amount displayed on the spin control. The label “1.5×” means the round costs 50% more than the base setting, not that all awards are multiplied by 1.5.

The additional pocket changes the map’s opportunity structure. It does not guarantee that a ball will enter that pocket or that a bonus will start. Record whether Extra Bet was active in every round used for comparison.

Do not infer the Extra Bet cost or effect from another Quickspin game. In Fire & Bones the documented effect is an added Bonus Pocket. Other titles use optional stake modes for unrelated Wild or scatter changes.

If the local interface omits Extra Bet, the provider page does not prove that the operator must expose it. Optional controls can depend on version and market configuration.

Buy Feature settlement checks

The 4× option enters Ship Graveyard and the 12× option enters Fire Island. A confirmation screen should identify the selected route, total price and starting state. Save that screen before accepting, especially if the account uses a currency other than the euro examples in the product sheet.

After purchase, verify that the ledger records one deduction equal to the confirmed total. All resulting balls and bonus events should appear under one round ID. A direct bonus purchase should not create an unexplained second charge when a Re-Launcher activates.

Market eligibility must be established in the operator’s live interface and terms. The supplier’s documentation proves that the product supports these modes, not that every account in New Zealand can access them.

Price each route against the session budget before selection. Because the documented purchases are relatively small multiples compared with many slot bonus buys, it is easy to click repeatedly; the lower ticket does not change the variability of individual paths.

RTP variants and simulation figures

Quickspin lists four total RTP configurations: 98.10%, 94.19%, 92.07% and 84.21%. The same title and artwork can be deployed with different values. Open the in-game help and record the active percentage rather than assuming the 98.10% configuration.

The game sheet also reports the largest outcomes observed in provider simulations of 100 million balls: 243×, 239×, 237× and 222× for the respective configurations. These are simulation observations, not contractual maximum payouts and not predictions about a player’s next round.

The volatility rating is one out of five in the supplied sheet. That comparative rating does not mean every round returns a small award, nor does it remove the possibility of losing the paid stake. Use it only as the provider’s classification within its own catalogue.

RTP should be recorded alongside mode. Base play, Extra Bet and direct bonus entry can have separate help-table details in the deployed version. Do not average unlike modes into an invented single-session percentage.

A ball-by-ball review worksheet

Begin with Game ID, RTP, base stake, selected mode and initial ball count. Assign each ball an identifier such as B1, B2 and B3. For a re-launch from B2, use B2-R1 through B2-R3. This keeps the family of paths visible.

For each ball, record the launch map, every Award Gate crossed, gate subtotal, terminal destination and terminal award. If the destination is a Bonus Pocket, add one to the next-stage counter. If it is a Re-Launcher, create the three child identifiers.

When the active map finishes, reconcile its award subtotal and the next-stage ball count with the transition screen. Repeat the worksheet for Ship Graveyard and Fire Island as required. At final settlement, compare the total documented awards with the casino ledger credit and retain the round ID.

This worksheet is specific to Fire & Bones. Reel positions, paylines and scatter counts used in conventional slot audits do not describe a Plinko path.

Mobile visibility and accessibility checks

On a narrow screen, confirm that pocket labels and gate values remain legible without relying on transient animation. The interface should expose a help panel and round history that can be opened after settlement. Animation speed controls or a reduced-motion setting are useful where available, but they do not replace the result log.

Check that the total stake remains visible when Extra Bet or Buy Feature is selected. A mode button should not obscure the currency deduction. Rotate the device only if the operator supports it; otherwise use the documented portrait layout and zoom-independent text.

If colour is used to distinguish Bonus Pockets, Award Pockets and Re-Launchers, verify their labels as well. A result should not require colour perception alone to identify the event type.

Product facts versus casino-account facts

Quickspin can document the maps, ball events, mode prices and RTP families. It cannot establish who operates a casino account, whether that operator accepts New Zealand residents, which account currency is used, or how withdrawals are processed.

Check those commercial facts in the operator’s terms and cashier. A game visible in a public catalogue may be unavailable after login because of location, platform or account restrictions. Conversely, a locally deployed version may use a different RTP from the headline provider value.

Keep the product source and operator source side by side. This preserves a useful review of the game without turning a supplier page into an unsupported claim about local access.

Final settlement cross-check

After the last ball stops, compare three totals: awards accumulated at gates, awards from terminal pockets and awards carried through either bonus map. The sum should match the game-history total before conversion to the account currency. A difference often points to a missed gate or a re-launched ball rather than an unexplained extra pocket.

Record the account balance immediately before and after the round only as a secondary check; simultaneous account activity can make balance subtraction unreliable. The round-specific ledger entry and round ID are the primary evidence.

If the animation and history appear inconsistent, do not replay with a larger stake to test it. Save the ball worksheet, the active RTP, the mode and the server round reference, then ask authenticated support for the event log.

Frequently asked questions

Is this a reel slot? No. Quickspin documents a ball-and-peg Plinko format.

What does a Re-Launcher do? It launches three new balls from the top.

Which RTP totals are listed? 98.10%, 94.19%, 92.07% and 84.21%.

What are the bonus purchases? 4x for the first bonus and 12x for the second, subject to market availability.

Is it confirmed in New Zealand? No. Product documentation does not prove operator availability.

Official sources

• Quickspin: Pearl o’ Plinko — Fire & Bones
• Official game sheet

Bottom line: distinguish gates that pay while the ball continues from pockets that end its path, and count bonus-entry balls only after settlement.

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.