Pearl o' Plinko: Mermaid Cove — trace every pearl through the board

Pearl o’ Plinko: Mermaid Cove by Quickspin is an RNG Plinko game rather than a reel slot. Players select a bet per ball and launch between one and 100 balls. The board contains Award Pockets, Award Gates, Bonus Pockets, Portal Gates and Re-Launchers.

Verified configuration

The official sheet lists four RTP totals: 98.10%, 94.19%, 92.07% and 87.15%, all at volatility one out of five. Its reference bet-per-ball range is €0.10–€100, not confirmed NZD pricing.

The sheet reports maximum simulation results of 199x, 194x, 191x and 171x in roughly 100 million balls. Because the unit is balls rather than spins, preserve that wording when comparing the figures.

Gates, pockets and re-launchers

An Award Pocket ends the ball’s journey and pays its displayed multiplier. An Award Gate pays when the ball passes through and lets it continue. These are different events and can contribute differently to one run.

A Portal Gate transports the ball to its connected exit. A Re-Launcher creates three new balls from the top. The round history should show how the resulting awards combine; visual trails alone are not an auditable calculation.

Bonus progression

Each ball that finishes in a Bonus Pocket adds one ball to the next bonus. The bonus starts after all current balls complete their runs. The two documented destinations are Kraken Peninsula and Mermaid Cove, with the second positioned later on the pirate map.

Extra Bet costs 1.5x and adds another Bonus Pocket. The listed Buy Feature prices are 4x and 7x for direct entry to the first or second bonus. Market availability can differ.

Total stake and mobile checks

The screen can show a bet per ball while the user launches many balls. Confirm the total debit before approving the round. A €1 reference bet per ball with 100 balls is not a €1 total round.

On mobile, check that selected balls, price per ball, total cost and bonus count remain visible. Save the round ID and full history if portals, re-launchers or overlapping balls make an award difficult to reconstruct.

The related Fire & Bones guide has different bonus maps and buy prices. Do not import those values into Mermaid Cove. The Quickspin guide explains how to identify the deployed version.

One to 100 balls: calculate the round before launch

Mermaid Cove lets the user select a stake per ball and launch between one and 100 balls. The multiplication is the first material check. If the interface shows a stake of 0.50 units per ball and 40 selected balls, the round costs 20 units before any optional mode. The 0.50 figure is not the total deduction.

Write down three fields: price per ball, selected ball count and total round cost. The confirmation or main control should make all three visible. If the total is hidden behind an animation or abbreviated label, reduce the ball count and inspect the help before proceeding.

Changing the number of balls changes exposure, not the value assigned to each ball. It also does not make a particular pocket more likely because earlier balls missed it. Every result remains part of the game’s random process.

For an audit, assign a sequential identifier to every original ball. This may sound excessive at 100 balls, but the server history should provide an event list or round total. Manual tracking is most useful for a smaller test round used to understand the interface.

Reading an Award Gate event

An Award Gate pays when a ball passes through it and allows the same ball to continue. One path can therefore contain several payable events before its terminal destination. The gate value belongs to that ball’s journey and should be recorded even if the ball later enters a pocket.

Do not confuse a visual bounce near a gate with a recorded pass. Use the event history or the gate’s confirmed animation. A crowded 100-ball launch can make individual paths impossible to follow visually.

Store each gate event in order. Where values are shown as multipliers, retain the multiplier and base amount rather than converting repeatedly. At the end, calculate the ball’s gate subtotal and add the terminal event.

A gate award is not a new ball. It adds value while the current ball continues. Re-Launchers, described separately, are the feature that creates additional balls.

Reading an Award Pocket event

An Award Pocket is terminal. Once a ball enters, the displayed multiplier is awarded and that ball’s journey ends. It cannot then pass through another gate or enter a second pocket.

In the worksheet, the terminal destination column should contain one Award Pocket, Bonus Pocket, Re-Launcher or other documented ending event. This makes it easy to detect an impossible record where the same ball was accidentally counted twice.

The final pocket value is added to any gates already crossed by that ball. It does not replace the earlier gate subtotal. Compare the resulting per-ball total with the server event log before summing the whole launch.

Portal Gate transport

A Portal Gate moves the ball from its entry to the paired exit. The transport changes the remaining route through the board but is not automatically an award. Record the entry portal, exit portal and the next event after emergence.

The transported ball keeps its identity. Do not create a second ball in the worksheet simply because the animation disappears and reappears elsewhere. Only a Re-Launcher creates the documented three-ball addition.

Portal placement can make a path look discontinuous on a screenshot. A video is still weaker evidence than the structured round history, which should preserve the actual event sequence.

If a portal label or pairing is unclear on mobile, consult the game’s help screen before launch. Colour alone should not be relied upon to identify the connection.

Re-Launchers and the expanding ball count

When a ball reaches a Re-Launcher, three new balls begin from the top. The triggering ball’s route ends at that feature; the three new balls belong to the same paid round.

Use parent-child notation in a review. If original ball B7 triggers the feature, label the replacements B7-R1, B7-R2 and B7-R3. If the live rules allow later re-launch events, continue the notation so no generated path is omitted.

The total number of balls resolved can exceed the number purchased. That does not mean the account was charged again. Re-launched balls are a feature result and should remain tied to the original round ID.

When the final credit seems larger than the visible pockets from the initial launch, first check for Re-Launchers and Award Gates. Missing generated balls is a common reconstruction error in a rapid multi-ball display.

Bonus Pocket accounting

Every ball that ends in a Bonus Pocket contributes one ball to the next bonus stage. The bonus waits until all balls currently moving on the map have completed. This permits several bonus balls to accumulate before the transition.

Count successful landings rather than available pockets. An extra pocket supplied by Extra Bet is only another possible destination; it is not a bonus ball by itself.

At the end of the map, compare the counted Bonus Pocket landings with the transition screen. Preserve that starting count for Kraken Peninsula or Mermaid Cove. A mismatch should be investigated before evaluating the bonus awards.

Bonus Pocket landings belong to the same round as the paid launch. They are not free-spin coupons, and their count should not be represented as a cash multiplier.

Kraken Peninsula progression

Kraken Peninsula is the first named bonus destination. Balls earned through Bonus Pockets can enter it after the preceding map finishes, and the documented 4× Buy Feature provides direct access where enabled.

Start a fresh event table for the bonus map. Record the number of balls carried in, then follow its gates, pockets, portals and re-launch events according to the active help. Do not carry the coordinates of the base board into the bonus layout.

If Kraken Peninsula produces Bonus Pocket entries for the later stage, keep those counts separate from the awards already accumulated. A future Mermaid Cove ball is a progression state, not an immediate pocket payment.

The 4× price is the direct-entry cost relative to the selected base unit. It does not promise a four-times return. Confirm the actual account-currency deduction on the purchase screen.

Mermaid Cove progression

Mermaid Cove is the second documented bonus destination. It appears later on the map and can be reached through progression or by the 7× direct purchase where the operator exposes that option.

Record how entry occurred. A progression route begins with balls generated by prior Bonus Pocket events; a purchase begins with a ledger deduction and its stated starting configuration. Both routes need the active ball count before settlement can be audited.

Do not infer Fire & Bones rules from the shared Pearl o’ Plinko name. Mermaid Cove has its own two destinations and a 7× second-stage purchase, while the related title documents different maps and pricing.

Larger-looking pockets or a later map do not guarantee that a purchased round returns its price. The route remains random and should be reconciled ball by ball.

Extra Bet: added pocket, higher total cost

Extra Bet costs 1.5× and adds another Bonus Pocket. When it is active, first multiply the base round cost—price per ball times ball count—by the displayed mode factor. Confirm the final deduction shown by the interface.

The extra pocket changes the available board destinations. It does not award a bonus immediately and does not multiply ordinary Award Gate or Award Pocket values unless the help explicitly says so.

Compare Extra Bet and standard rounds only after recording ball count and active RTP. A 100-ball Extra Bet launch is not comparable with a ten-ball standard launch based on the final total alone.

Optional-mode availability can vary. If the live game omits Extra Bet, the global Quickspin sheet does not prove the control must be present for that operator or market.

Direct-entry prices and confirmation checks

Quickspin lists 4× for direct entry to Kraken Peninsula and 7× for Mermaid Cove. Before accepting, check the selected destination, stake unit, ball count if displayed, total price and active RTP.

A direct purchase should create one clear ledger deduction and one linked round. Re-Launchers and bonus progression inside that round are outcomes, not new paid purchases.

If the confirmation amount does not equal the displayed multiplier applied to the relevant base unit, cancel and inspect whether Extra Bet, multi-ball selection or another denomination remains active. Do not rely on a remembered cash value from an earlier session.

The provider source establishes that these routes exist in the product; only the logged-in operator can establish local availability.

Four RTP versions

The documented total RTP options are 98.10%, 94.19%, 92.07% and 87.15%. They are alternative configurations, not components. The same board art and feature names can appear with any one of them.

Open the information panel and save the exact RTP together with the Game ID. Quoting the highest published version without checking the deployment misstates the product actually available.

The one-out-of-five volatility rating is Quickspin’s catalogue classification. It does not guarantee frequent profitable rounds, especially when a user increases total exposure by selecting many balls.

Keep mode-specific return information from the active help where provided. Do not assume that every direct-entry or Extra Bet route shares an identical figure merely because the headline total is printed once.

Understanding the simulation figures

The game sheet reports largest observed results of 199×, 194×, 191× and 171× in samples near 100 million balls for the four configurations. Those figures describe supplier simulations, not a contractual maximum payout.

The unit matters: the sheet refers to balls, not complete multi-ball rounds. A round launching 100 balls contains many ball trials under one account deduction. Do not rewrite the statistic as “once per 100 million spins”.

An observed simulation maximum cannot be used to predict a personal ceiling or likelihood. The live paytable and any explicit maximum rule are the proper contractual sources.

Full round worksheet

Begin with Game ID, RTP, account currency, bet per ball, purchased ball count, Extra Bet state, direct-entry state and total deduction. Then assign identifiers to all original balls.

For every ball, record map, Award Gates, Portal movements, terminal event and award. Create child identifiers for each three-ball Re-Launcher. Count Bonus Pocket landings for the next-stage transition.

At each map boundary, reconcile the subtotal and number of carried balls. At final settlement, add gate and pocket awards from all maps and compare them with the round-specific casino ledger entry.

The worksheet should never contain wallet credentials or unrelated account data. A game dispute needs the round ID and event state, not a password or payment secret.

Mobile acceptance test

On a phone, verify that the ball count, price per ball and total cost remain visible before launch. Confirm that active Extra Bet or Buy Feature labels are not hidden beneath the board.

Open a completed round and check whether the history exposes gates, terminal pockets, re-launches and bonus transitions in readable form. Fast animation alone is inadequate for a 100-ball event.

If several trails overlap, reduce the next test to a single ball rather than trying to infer events from colour flashes. The server history is authoritative for the completed result.

New Zealand scope and source boundary

Quickspin documents Mermaid Cove’s mechanics, RTP options and reference euro range. It does not establish a New Zealand operator, NZD pricing, local legality or access to optional controls.

Confirm account eligibility, currency and terms directly with the operator. A public demo or provider page is not proof that a logged-in New Zealand account can play or purchase a bonus.

This separation also applies to withdrawals and verification. They are casino-account processes, not properties of the Plinko game.

Before publication, date the product-page and game-sheet checks. If the deployed help differs, describe the version conflict instead of blending the values. The live round record determines the actual ball count, mode and settlement used for a transaction; the supplier sheet remains the reference for the documented product family.

Frequently asked questions

Is this a reel slot? No. Quickspin describes it as an RNG Plinko game.

How many balls can be launched? The official rules list one to 100 in one go.

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

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

Is it confirmed in New Zealand? No. The provider page does not establish local operator availability.

Official sources

• Quickspin: Pearl o’ Plinko — Mermaid Cove
• Official game sheet

Bottom line: audit the total ball purchase first, then separate continuing gates from terminating pockets and transported or re-launched paths.

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.