NZ-NI-0541 · supplier source record

PG Soft game catalogue: titles, versions and primary-source checks

A practical map for finding exact PG Soft titles, matching catalogue IDs and separating studio data from operator availability.

Supplier sources below. Operator eligibility needs a separate check.

Original editorial artwork; it is not official PG Soft material.

PG Soft maintains an official games catalogue with search, list and grid views plus sorting by release date, volatility, RTP and maximum win. This hub explains how to use that catalogue without treating a studio listing as proof that an operator offers the same game in New Zealand.

The catalogue and its public data endpoint were checked on 8 October 2026. They are primary evidence for names, internal IDs, descriptions and selected headline settings. Account availability, currency, wager limits and the exact live help still belong to the operator deployment.

What the catalogue confirms

The official interface labels entries by game name and exposes columns for volatility, RTP, maximum win, languages and certification. It also provides release-date and value sorting. Those tools help identify a title; they do not establish local legality or a real-money launch.

PG Soft’s public API associates each entry with a numeric pgid, internal game code, description, headline maximum return multiplier and maximum RTP field. Save the ID whenever titles have punctuation, translations or similar sequels.

Exact-title workflow

Search the complete title first. Open the result and compare its ID, English name, game code and imagery. If a review or operator lobby uses a shortened label, do not assume equivalence until at least two identifiers match.

For example, this batch uses IDs 2140622 for Grimms’ Bounty: Princess & the Frog, 2175036 for Lucky Mischief and 2152563 for Touchdown Wins. The ID is more stable than punctuation or marketing copy.

Version evidence

A catalogue entry can change while an operator keeps an older approved build. Record studio ID, live game ID, visible version, language, operator domain and check date together. A newer catalogue timestamp is not proof that every integration updated simultaneously.

If two builds show different RTP or limits, publish them as separate dated configurations. Do not average them, choose the higher one or call one universal.

Where rules come from

The catalogue description is a starting point, not a complete paytable. It can confirm headline mechanics such as Collector symbols, Summoning Wilds or Free Spins multipliers. Exact trigger order, symbol values and settlement must come from the game’s own help.

Capture the help before a paid decision. Important pages include rules, paytable, RTP disclosure, wager controls, feature instructions and maximum-win treatment.

Reading the API carefully

The maxrtp field records the maximum RTP represented by the catalogue record; it may not be the profile loaded by a specific operator. The hrm field supplies a headline return multiplier, not a probability and not a prediction.

The descriptive gd text can summarise game geometry and features. Treat it as supplier copy and paraphrase it; never reproduce it as an independent review.

Release dates and current status

An API creation or release timestamp establishes when a record appeared in that feed, subject to the provider’s data conventions. It does not prove real-money availability in New Zealand on that date.

For “new” or “current” claims, recheck the API, catalogue card and live operator loader. Preserve the timezone and retrieval time.

RTP verification

Start with the catalogue maximum RTP, then open live help. Record the exact percentage, any alternative profiles and the build identifier. If live help differs, the deployed value is the relevant account fact.

RTP is long-run theoretical return. It cannot be converted into an expected result for one deposit, session or bonus round. General mathematics belongs in the site’s dedicated methodology rather than every game review.

Maximum win

A catalogue maximum such as 5,000x or 10,000x is a cap or headline maximum relative to the defined bet. It does not guarantee that result or describe frequency.

Check whether live help defines the multiplier against total bet, base bet or another unit, and whether reaching the cap closes a round or feature.

Volatility labels

PG Soft permits sorting by volatility, but a label remains the studio’s scale. It is useful for comparing its own games, not for predicting when a feature will occur.

When a precise label is absent from the accessible entry, state that it was not confirmed. Do not reverse-engineer volatility from theme or maximum win.

Mobile-first checks

PG Soft presents mobile-oriented games, yet a catalogue entry alone does not prove an operator’s implementation works well on every device. Test portrait and landscape, text scaling, safe-area padding, help access and history.

Verify that stake, balance, feature counter and multiplier values remain visible. After interruption, compare the resumed state with server history.

Demo boundaries

A provider redirect or public preview may demonstrate controls and terminology. It does not confirm real-money access, NZD support, KYC rules, deposits or withdrawals.

Never label a sponsored operator link as the official demo. Our calls to action lead to a sponsored destination and are marked accordingly.

New Zealand availability

The global PG Soft catalogue is not a New Zealand operator register. Confirm account registration, territory terms and authenticated lobby access separately.

Do not infer that a listed certification applies to a particular local operator or every title. Product validation and operator authorisation are different evidence layers.

Named guides in this site

Each guide owns one game intent and keeps rules, RTP, mobile evidence and feature explanation on one canonical URL.

Editorial record template

For every future PG Soft review, store exact name, pgid, game code, catalogue timestamp, maximum RTP, headline maximum, description, source URL and retrieval date. Add live operator, version, currency and actual help values only after direct verification.

This structure prevents a later editor from copying a value between similar titles or treating a catalogue maximum as a deployed setting.

Handling conflicts

If API, catalogue and live help disagree, show each dated claim and prefer live help for the tested account. Contact the provider or operator when the difference affects settlement.

Do not silently “correct” historical evidence. Add a change note explaining which field changed and which source now supports it.

Accessibility review

Catalogue search must work without pointer-only interactions, and title cards should expose names as text rather than image alone. A game help screen needs keyboard access, readable contrast and alternatives to colour-only states.

Record limitations as product facts. A visually attractive mobile layout can still be difficult to audit if the paytable or history is inaccessible.

Common mistakes

Do not claim that every PG Soft catalogue game is playable in New Zealand. Do not use maxrtp as proof of an operator profile. Do not create separate thin pages for one game’s RTP, demo and Free Spins.

Avoid mixing translated titles, IDs or similarly themed releases. Never describe a maximum multiplier as typical performance.

Publication checklist

Match exact title, ID and game code.
Save source and date.
Separate catalogue facts from deployed settings.
Verify live RTP and wager unit.
Keep one canonical guide per game.
Mark sponsored destinations clearly.
Check mobile help and history.
Do not promise NZ access or outcomes.

Final assessment

The PG Soft catalogue is strong identification evidence when its IDs and fields are preserved. Its limits are equally important: it cannot prove an operator’s territory, currency or active configuration.

Use this hub to find the right title, then move to the named guide and live help for rules-level analysis.

Catalogue-field dictionary

The public feed uses short technical keys. pgid is the stable catalogue identifier used in this project. gn is the displayed game name, gc is a compact game code, gd contains the descriptive summary, hrm carries the headline maximum multiplier and maxrtp contains the catalogue’s maximum RTP value. Asset collections point to covers, icons and marketing material; they are identification aids, not rules.

Always store the raw field and an editor-friendly label. Do not infer that a missing value means zero. Missing, empty and inaccessible have different meanings and should remain distinct in the evidence table.

Reproducible API check

Record the endpoint, retrieval time and language path. Search for the numeric ID rather than relying only on the name. Save the enclosing game object with enough context to preserve code, description and numerical fields.

When repeating the check, compare structured values rather than the order of catalogue cards. A title can move because the site changes its Featured sort without any rules revision. Release-date sorting and featured sorting answer different questions.

If a record disappears, do not immediately call the game discontinued. Check alternative language feeds, the website search and existing operator help. Report “not found in the checked feed” until the provider confirms status.

Name-normalisation rules

Preserve apostrophes, ampersands, numerals and subtitle punctuation from the primary English record. Create a URL slug separately using lowercase ASCII and hyphens. The slug is routing infrastructure, not the official name.

Keep known aliases in metadata, but choose one canonical page. If an operator omits a subtitle, use ID, code and imagery to determine whether it is the same build. Do not create a second article for a spelling variant.

Sequels require separate IDs and separate evidence. Similar art or a shared character does not justify merging their RTP, grid, features or maximum.

Building a rules evidence pack

Begin with a screenshot of the help header showing title, provider and version. Add the RTP page, paytable, wager screen, feature rules, maximum-win clause and round-history example. Name files with game ID and ISO date.

For a feature, capture the trigger grid, transition, counter, one complete child round and final summary. For collection or multiplier mechanics, include both before and after states and the calculation detail.

An evidence pack should allow another editor to reproduce the claim without opening an affiliate page. Promotional videos can illustrate theme, but they cannot replace the paytable.

Operator-deployment matrix

When comparing accounts, use one row per operator and build. Suggested columns are operator, territory, authenticated access, game ID, version, currency, minimum and maximum total stake, RTP, optional feature availability, check time and evidence link.

Never fill an empty operator cell with the studio maximum. Keep catalogue and deployment values in separate columns. This prevents a maximum RTP from being presented as the active percentage.

If the same operator has web and app integrations, test both only when necessary and label them separately. A mobile wrapper may use the same server build but that should be verified, not assumed.

Change classification

Classify updates as identity, presentation, configuration or rules changes. A new cover is presentation. A different RTP profile is configuration. A changed trigger or multiplier order is rules. A new numeric ID may signal identity change.

This classification determines how much of an article needs revision. It also stops an artwork refresh from resetting the publication date as if the game were newly researched.

Keep previous checked dates in the internal record. The public page can show the latest review while corrections explain material changes.

Search-intent boundaries

The provider hub answers “which PG Soft game is this?” and “where are the studio’s original sources?” A named review answers how one exact game works. Neither should become a general casino-ranking page.

Readers seeking bonus terms, crypto payments or account verification need dedicated guides. Short internal links are preferable to repeating generic advice across hundreds of game URLs.

Do not create a new URL solely for “PG Soft RTP” when the hub can explain field methodology and individual reviews hold exact values. Consolidation makes version updates safer.

Quality-control questions

Before publishing a new game, ask whether the title and ID match, whether every number has a primary source, whether configuration scope is explicit, whether NZ access is separately verified and whether two sponsored CTAs are clearly labelled.

Check that Title, Description and H1 are unique and describe the exact search task. Verify canonical, breadcrumb, Article schema, image alternative text and internal links after the static build.

Finally, test at 390-pixel width. Long subtitles, tables and IDs must wrap without horizontal overflow, and help-oriented content must remain readable before promotional elements.

Example source reconciliation

Suppose the API reports maximum RTP 96.75%, an operator help page shows 96.20% and a third-party review says 96.50%. Publish the first as catalogue maximum, the second as deployed account value and exclude the unsupported third-party number from factual settings.

If the API says a feature multiplier reaches 100x but live help describes a lower ceiling, record the build and ask support. Do not average 100 and the lower value. One may reflect a configuration or later version.

Maintenance cadence

Recheck a named game when its primary record changes, when a reader supplies credible contradictory evidence or when the operator updates the build. Avoid meaningless date refreshes that do not verify any field.

For the hub, periodically test catalogue URL, API reachability, sorting labels and existing internal links. Add named guides only after their source and complete article are ready.

Research log fields

The internal log should contain topic ID, canonical URL, editor, check timestamp, primary source, game ID, code, evidence status, unresolved questions and next review trigger. This is more useful than a vague “updated” label.

For unavailable fields, record where they were sought. That prevents the next editor from repeating the same dead end and distinguishes an omitted value from an unperformed check.

A practical catalogue session

Start with the studio catalogue in list view and search the exact title rather than a shortened nickname. Copy the displayed name, release ordering, volatility label, RTP field, maximum-win field, language list and certification entry into a dated worksheet. Then query the public catalogue API and match the human-readable title to its numeric ID and code. A result is considered matched only when the title and at least one stable identifier agree; similar artwork or a shared series name is not enough.

Open the named article from the hub and compare its facts with the worksheet. Catalogue-level maximum RTP belongs in a field labelled as such. An operator’s live help value belongs in a separate deployment field. If only the studio maximum is available, the article must not imply that a New Zealand account receives that configuration. This distinction is especially important when a search result displays one percentage without explaining its scope.

Finish by testing the internal path back to this hub, the responsible-gambling guide and the corrections page. The exercise should leave a compact evidence bundle: source URL, access time, title, ID, code, captured fields, territorial status and unresolved questions. That bundle supports a correction without forcing the next editor to repeat the whole discovery process.

What this hub deliberately does not rank

This page does not rank PG Soft titles by entertainment value, winning potential or popularity. Those judgements require audience data or personal preference that the official catalogue does not establish. Release order is not a quality score, maximum win is not a prediction, and high volatility is not evidence that one title is better than another.

The useful comparison is documentary: which identity fields are stable, which rules are described, which numbers belong to a specific build and which questions remain open until live help is inspected. That approach makes the catalogue navigable without turning technical metadata into a recommendation.

Publication gate for a new review

A proposed game page should remain unpublished until its canonical name, provider, source, identifier and intended search task are all fixed. The draft also needs a unique image, a single H1, useful alternative text, two clearly labelled sponsored routes, a responsible-play link and a correction route. Any numerical rule must point to the exact primary record that supports it.

The final editorial pass asks a simple question: could a reader use the page to identify the game and verify the deployed settings without trusting our prose alone? If not, the missing navigation or evidence should be repaired before adding the URL to this hub.

Latest rules guides

Majestic Treasures — 5×5 clusters, conditional gold-frame Wilds and separate cascade ladders.
Bali Vacation — Infinity Reels, a random No Poker event and retriggerable free spins.
Fortune Ox — a 3–4–3 line layout, shared outer reels and the full-board 10× condition.
Guardians of Ice & Fire — shaped 576-way base play and a 2,304-way dual-board feature.
Galactic Gems — twelve blockers, expanding ways and an extra-life bonus-respin system.
Raider Jane’s Crypt of Fortune — three-use sticky Wilds, 2,304 ways and feature persistence.
Mermaid Riches — mirrored reel heights, numbered Wilds and separate multiplier ladders.
Heist Stakes — centre-reel Wild conversion, 720 ways and feature multiplier timing.
Wild Bandito — Gold Framed conversion, 1,024 ways and a 12-spin feature.
Candy Superwin — awarded Wilds, 2×2 Big Candy formation and cluster multipliers.
Emoji Riches — reverse collapse behaviour, persistent special symbols and additive Wild multipliers.
Spirited Wonders — 256–10,000 ways, large-symbol counting and separate cascade ladders.
Legendary Monkey King — expanding reel heights, changing ways and an accumulating feature multiplier.
Buffalo Win — Infinity Reels, expanding stacked Wilds and persistent bonus-state evidence.
Supermarket Spree — eight-symbol combinations and additive x2–x50 multiplier rules.
Butterfly Blossom — transforming Caterpillar Wilds, finite cascade multipliers and the r5 free-spin rules.
Destiny of Sun & Moon — both-way combinations, separate celestial multipliers and the r4 maximum evidence.
Garuda Gems — 4,096 ways, three-Wild collection thresholds and the r.7 RTP profile.
Fortune Tiger — random selected-symbol respins, the full-grid x10 condition and matching 2,500x maximum figures.
Mask Carnival — shifting reels, different base and bonus multiplier steps, and +1 free-spin symbols.
Speed Winner — variable ways, additive multiplier symbols and the r2 maximum-win distinction.
Lucky Piggy — persistent Scatter Wilds, an increasing feature multiplier and counter extensions.
Win Win Fish Prawn Crab — 10,000 ways, a refillable lives system and continuing bonus multiplier.
Battleground Royale — centre-symbol transformation, a diamond grid and mandatory bonus conversions.
Rooster Rumble — numbered Wild durability, x2 bonus steps and a 10,000-way field.
Totem Wonders — ten fixed lines, paired side multipliers and Double Wild resolution.
Prosperity Fortune Tree — rising cascade factor, Angpau additions and a resetting bonus counter.
Wild Bounty Showdown — Gold Framed conversion, multiplier doubling and an 8x Free Spins reset.
Wild Coaster — changing ways, consumable Wild stacks and persistent feature positions.
Legend of Perseus — oversized-symbol counting, collected factors and retriggerable Free Spins.
Rave Party Fever — three activation spots, collapsing clusters and the 65-symbol Bonus Feature threshold.
Fortune Rabbit — ten fixed lines, prize-symbol collection and the documented eight-spin feature.
Midas Fortune — Gold-to-Wild conversion, additive Wild multipliers and persistent Free Spins state.
Diner Delights — anywhere wins, additive field multipliers and carry-over between winning free spins.
Alchemy Gold — sticky collapse logic, Gold transformations and the documented Free Spins multiplier ladder.
Lucky Clover Riches — Sticky Pay Anywhere, Clover outcomes and the r6 RTP profile.
Super Golf Drive — changing ways, Mystery conversion and the documented RTP conflict.
Mystical Spirits — three colour collectors and the combined multiplier product.
Songkran Splash — reel multipliers, 720 ways and the r4/catalogue RTP difference.
Hawaiian Tiki — expanding centre-reel Wilds and the advertised-versus-simulated maximum distinction.
PG Soft official catalogue
PG Soft public catalogue API
Responsible gambling guide
Corrections policy

Newly verified game guides

Circus Delight — 25 lines, doubled Wild wins and two-stage cannon selection.
Genie’s 3 Wishes — 243 ways, Wild Wishes and three distinct free-spin paths.

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.

Open the primary source ↗Report a correction