Grimms’ Bounty: Princess & the Frog — Collector and RTP guide

Grimms’ Bounty: Princess & the Frog appears in PG Soft’s official API under ID 2140622 and code princess-frog. The supplier describes a three-reel, five-row connecting-ways game with Prize symbols up to 500x, Collector multipliers up to 10x and eight Free Spins from three Scatters.

The record checked on 8 October 2026 publishes a maximum RTP field of 96.77% and headline maximum of 10,000x. These are catalogue facts, not proof of the profile, stakes or availability loaded for a New Zealand account.

Verified catalogue record

Field	PG Soft API
Catalogue ID	2140622
Game code	princess-frog
Layout	3 reels × 5 rows
Win system	Connecting ways
Maximum RTP field	96.77%
Headline maximum	10,000×
Prize values	Up to 500× bet
Collector factor	Up to 10×
Free Spins	8 from 3 Scatters

The public description does not disclose a complete paytable, wager range, volatility label or full calculation order. Those fields must come from the live game help.

Connecting ways

Connecting ways differ from fixed paylines. A winning connection depends on matching symbols across the required adjacent reels or positions defined in help. Do not impose a standard ways count or adjacency rule without seeing the deployed paytable.

For an audit, capture all fifteen positions and the highlighted connection. Record ordinary award before any Collector action.

Prize symbols

PG Soft says Prize symbols can carry values up to 500 times the bet amount. A printed value is not automatically a cash award; the game description links them to Collector symbols.

Save every Prize position and value before collection. The live rules must show whether all visible Prizes, a region or another subset is collected.

Collector symbols

Collectors can award multipliers up to 10x. The catalogue tagline states that Prize and Collector symbols multiply wins, but it does not expose the complete sequence or rules for several Collectors.

Do not assume factors add or multiply together. Record each Collector, its displayed value, collected Prize subtotal and final server calculation.

Free Spins trigger

Three Scatter symbols trigger eight Free Spins according to the catalogue description. Save the trigger grid, total bet and initial counter. The source does not confirm retrigger rules in readable detail.

Inside the feature, document any altered Collector behaviour rather than inferring it from promotional wording. Every child spin should retain a link to the parent round.

Maximum RTP

The API field is explicitly the maximum RTP and shows 96.77%. This may represent the highest configured profile, not necessarily the operator deployment.

Open live help and record its RTP with operator, build and date. If lower or different, preserve both; do not describe 96.77% as universally active.

Headline maximum

The catalogue lists 10,000x. Verify whether the deployed rules define it against total bet and what happens when reached. A maximum is a ceiling, not a likely or expected return.

The separate 500x Prize value is not the same as the entire game’s maximum. Collection and multipliers can form a larger result subject to the cap.

Stake and currency gap

The retrieved record does not establish minimum or maximum wager, NZD support or default denomination. Capture these in the active game before converting multipliers into currency.

Check whether “bet amount” means total wager for the round. Never multiply a Prize value by deposit size.

Mobile and preview

The catalogue supplies mobile-oriented assets and a preview path, but a provider preview cannot prove real-money New Zealand access. It can help verify layout and terminology.

On a phone, confirm that all five rows, Prize numbers, Collector factors, balance, total bet and feature counter remain readable in portrait and landscape.

Round reconstruction

Record starting balance, total bet, round ID, grid and ordinary ways win. Then list Prize values, Collector events, factors and final credit. Do not add a displayed total twice.

For Free Spins, maintain a counter ledger and sum child-round settlements once. Compare the final feature total with wallet movement.

Source hierarchy

The API confirms identity and headline fields. The studio catalogue confirms that the title belongs to PG Soft. Live help decides deployed rules and settings. Operator terms decide territory.

A third-party review can help locate questions but cannot replace those primary sources when numbers conflict.

Version protocol

Store ID 2140622, code, API timestamp, live build, language and operator together. If the name punctuation or artwork changes, those identifiers help determine whether it remains the same game.

Compare RTP, Prize range, Collector ceiling, trigger and cap separately. Do not treat one changed field as a complete version replacement.

Common mistakes

Do not call 96.77% the guaranteed active RTP. Do not pay every Prize without a documented collection. Do not assume several Collector factors combine by the method used in another title.

Avoid claiming 10,000x is typical, presenting the provider preview as a sponsored-site demo or promising New Zealand access.

Responsible controls

Set money and time limits before play. Collectible values can create suspense but do not make the next round due. Keep the full total bet visible.

Stop at the planned boundary. A large uncollected Prize symbol has no stored value after its round closes.

Questions for support

Ask for active RTP, stake range, exact connecting rule, collection order, multiple-Collector treatment and cap procedure. Provide ID 2140622 and round IDs.

For local availability, request the operator’s territorial terms. Do not bypass access restrictions.

Short answers

What is the catalogue ID? 2140622.

What is the maximum RTP field? 96.77%.

What triggers Free Spins? Three Scatters for eight spins.

How large can a Prize value be? Up to 500x bet in the API description.

How large can a Collector factor be? Up to 10x.

Is NZ access confirmed? No.

Final assessment

Grimms’ Bounty is best reviewed as a collection sequence layered on connecting ways. Its identity and headline values are unusually clear in the official API, while detailed settlement still requires live help.

Keeping catalogue maximums separate from deployed settings produces a useful page without invented certainty.

Collector audit worksheet

Create one row per Prize symbol with reel, row, printed value and collection status. Create a second table for Collector symbols with position and factor. When settlement occurs, preserve the server’s order: identify eligible Prizes, establish subtotal, apply the documented Collector treatment and compare the final award.

If several Collectors appear, do not choose between addition and multiplication by intuition. Copy the calculation from live help or round history. Where the interface displays only a total, ask support for the component event record.

Connecting-ways map

Sketch the three reels as five vertical positions and mark every symbol involved in a credited connection. Note whether adjacency can move between rows and whether duplicate symbols on one reel create multiple ways. Those rules determine the count and must come from the deployed paytable.

Keep Scatter settlement outside the ordinary connection subtotal unless help expressly combines it. The trigger count proves feature entry; it does not reveal the cash value by itself.

Free Spins reconciliation

At entry, record the three-Scatter grid, parent round and initial eight-spin counter. For every child spin, capture Prize and Collector events plus counter before and after settlement. Add retriggers only if the live rules and counter demonstrate them.

At feature end, sum child credits once and compare with the summary and wallet movement. Do not add a summary to its own components. Clear temporary Collector state before the next paid round unless the rules explicitly preserve it.

Configuration-change review

On a future check, compare catalogue ID, code, maximum RTP, maximum win, Prize ceiling, Collector ceiling, trigger and grid. A change in one field should be documented without assuming all others changed.

Store one complete example round with its matching help revision. This reference makes it easier to distinguish a genuine rule update from a translated label or redesigned animation.

Reader decision points

Before play, confirm the active RTP rather than the API maximum, full currency stake, connection rule and Collector arithmetic. A reader should also know whether the game history exposes components and whether accessibility settings preserve Prize numbers.

If these fields cannot be checked, the rational action is to pause. A fairytale theme and catalogue listing do not compensate for missing settlement evidence.

A compact pre-play evidence card

Before committing funds, write down the title, ID 2140622, code princess-frog, deployed RTP, total stake, account currency and help revision on one card. Add three rule checks: how connecting ways are counted, how multiple Collectors combine, and whether Prize values are affected before or after the Collector factor. The official API supports the identity, 96.77% maximum RTP, 10,000x cap, 10x Collector ceiling, 500x Prize ceiling and eight-spin trigger statement; it does not replace the deployed paytable for arithmetic detail.

After a session, attach one ordinary round and one feature sequence to that card. A future reader or editor can then distinguish a changed configuration from a misunderstanding of the animation. If the card cannot be completed because help is missing, that absence is a practical reason to stop rather than an invitation to guess.

Official and related sources

• PG Soft official catalogue
• PG Soft public catalogue API
• PG Soft catalogue guide
• Responsible gambling guide
• Corrections policy

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 PG Soft, 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.