Lucky Mischief by PG Soft: Summoning Wild rules and RTP

Lucky Mischief is listed by PG Soft under catalogue ID 2175036 and code lucky-mischief. The official description identifies a five-reel, five-row slot where Summoning Wilds create additional Wilds. In Free Spins they can award multipliers up to 100x; a separate Summoning Wild feature transforms adjacent symbols before wins are paid.

The API record checked on 8 October 2026 publishes a maximum RTP of 96.75% and headline maximum of 5,000x. An operator may load another profile, so live help remains decisive.

Verified catalogue facts

Field	PG Soft API
Catalogue ID	2175036
Code	lucky-mischief
Grid	5×5
Maximum RTP field	96.75%
Headline maximum	5,000×
Feature multiplier	Up to 100×
Main mechanic	Summoning Wild

The record does not expose full paytable, volatility, stake range or exact trigger counts in readable description. Those facts remain live-help questions.

Summoning Wild

A Summoning Wild can summon additional Wild symbols during any spin. Record the original symbol, every created Wild and the grid before ordinary wins are calculated.

Do not count an animation spark as a new Wild. Use the final transformed grid and server history.

Adjacent transformation feature

During the Summoning Wild Feature, all symbols adjacent to every Wild—including Summoning Wilds—transform into Wilds before wins are paid. The official description makes order important: transformation first, settlement second.

Map all Wild coordinates and surrounding cells. Where zones overlap, the same cell becomes Wild once; it is not a separate cash award for each source.

Free Spins multipliers

The catalogue states that Summoning Wilds appearing during Free Spins can award multipliers up to 100x. It does not provide the full value table or combination rule in the retrieved description.

Capture each displayed multiplier and whether several factors add, multiply or apply independently according to live help. Never borrow the rule from another PG Soft game.

Maximum RTP

The maxrtp field is 96.75%. Because it is explicitly a maximum field, do not state that every casino build uses it.

Record the percentage shown in the launched game with operator, version and date. Preserve a difference as configuration evidence rather than an error by default.

Maximum win

PG Soft lists 5,000x. Confirm the bet unit and cap procedure in deployed rules. The separate 100x feature multiplier is not the same as the total-game cap.

Neither number indicates probability. Do not frame the maximum as an expected outcome.

Trigger evidence gap

The API description does not state exactly how Free Spins or the named transformation feature begin. A useful review must not invent Scatter counts, purchased options or random-trigger rules.

Open feature help and record the trigger, initial counter, retriggers and any purchase menu. If inaccessible, keep them unavailable.

Paytable review

Capture regular symbol values, Wild substitutions and any exclusions from live help. On a 5×5 grid, also identify whether wins use lines, ways, clusters or another system.

Do not infer the win system from the visual arrangement. The official description only calls it a video slot.

Stake and currency

The catalogue record does not establish minimum wager, maximum wager or NZD support. Verify total bet before play and identify the unit used by 100x and 5,000x claims.

A provider redirect can show a generic bet type but not an operator’s account limits.

Mobile review

On mobile, all 25 positions and transformed cells must remain visible. Check that multiplier labels, feature counters, balance and total bet do not overlap.

After rotation or interruption, compare the summoned Wild set with round history. A replayed transformation is not another award.

Round ledger

Save opening balance, stake, round ID and original grid. Add the Summoning Wild position, created symbols, transformed adjacency zones, winning combinations, multiplier stage and final credit.

For Free Spins, nest transformation sequences beneath each child spin and reconcile the feature total once.

Overlapping zones

When several Wilds are close, draw one cell map. Mark every unique adjacent cell affected. A cell inside two zones still holds one Wild symbol after transformation.

If live rules assign extra behaviour for overlaps, record that explicit rule. Do not assume duplication from visual intensity.

Version record

Store ID 2175036, code, catalogue date, live build, language and operator. Compare trigger, adjacency definition, multiplier set, RTP and cap separately when updated.

The API timestamp can identify catalogue freshness but does not prove the exact operator release moment.

Common mistakes

Do not present 96.75% as guaranteed deployed RTP. Do not turn 100x into the maximum win or apply it to every Wild. Do not invent a Free Spins trigger.

Avoid claiming the preview proves New Zealand access or calling a sponsored link the official demo.

Responsible boundaries

Expanding Wild patterns can create near-complete grids, but they do not change the independence of later paid rounds. Set a loss and time limit before play.

If a feature purchase exists in the live build, treat its full price as a separate wager and check any alternative RTP.

Support questions

Ask for active RTP, stake range, win system, Summoning trigger, adjacency definition, multiple-factor order and cap handling. Include game ID and round IDs.

For territory, use the operator’s terms. Do not bypass controls.

Short answers

What is the catalogue ID? 2175036.

What is the maximum RTP field? 96.75%.

How large can the headline win be? 5,000x.

What can Summoning Wilds do? Create extra Wilds; a named feature also transforms adjacent symbols before settlement.

What is the feature multiplier ceiling? Up to 100x in Free Spins, according to the API description.

Is NZ availability confirmed? No.

Final assessment

Lucky Mischief is a transformation game whose accuracy depends on event order. Record the pre-feature grid, every created Wild, adjacency changes and final multiplier rather than judging only the finished screen.

The API provides strong identity, maximum-RTP and cap evidence. Detailed triggers, stakes and settlement require live help.

Transformation worksheet

Number the 25 grid cells and capture the state before Summoning. Mark the original Summoning Wild, every additional Wild it creates and every cell transformed by adjacency. Use one mark per final Wild even when two source zones overlap.

Next record the winning system and ordinary award from the transformed grid. Add each feature multiplier in the order shown by history. The worksheet should finish with the same amount credited by the server.

Feature-counter evidence

Because the public description does not state the trigger or initial spin count, the first verified feature round is important. Save its entry message, triggering event, counter, stake and parent ID. Do not generalise from an animation without matching help.

For every child spin, retain pre-transformation and post-transformation grids. If Summoning creates another Summoning Wild, use the live event sequence to determine whether expansion continues or stops.

Multiplier review

The “up to 100x” claim establishes a ceiling within the described Free Spins mechanic, not a complete value set. Record actual values and how multiple factors combine. A 100x display does not override the 5,000x overall cap.

If an operator exposes an alternative RTP or feature purchase, store that configuration as one coherent row. Do not pair its RTP with a multiplier rule captured elsewhere.

Accessibility and mobile state

The transformed cells must be distinguishable without relying only on orange flame or purple glow. Check text or icon labels, reduced-motion behaviour and history access at mobile width.

After rotation, compare the exact Wild set and feature counter. If state is lost visually but server history is intact, note the interface defect separately from settlement.

Update checklist

Recheck ID, code, RTP maximum, cap, grid, win system, Summoning trigger, adjacency, Free Spins entry and multiplier ceiling. Archive the prior evidence when a material field changes.

A renamed feature does not necessarily mean new arithmetic. Compare state transitions rather than promotional headings.

Practical reader questions

Can the full wager be seen? Does live help state RTP? Are transformed cells and factors visible? Can the result be reconstructed from history? Is New Zealand account access verified independently?

If any answer is missing, label it clearly. Precision is more useful than filling every table cell.

Worked verification scenario

Imagine a spin begins with one Summoning Wild near the centre. Capture the untouched 5×5 grid first. When the feature creates further Wilds, number each new symbol in animation order and shade only the cells that the interface records as transformed. If two Wild zones touch the same cell, count the resulting cell once unless the rules explicitly award a separate event. This produces a reproducible state map instead of a memory of flashing effects.

Next, copy the credited combinations and their base values from history, followed by each displayed feature factor. The official API says Free Spins multipliers can reach 100x and the overall published cap is 5,000x, but it does not tell us that a particular round will approach either ceiling. The worked record should show what actually happened, not reverse-engineer an exciting number from the promotional maximum.

Close the review by checking wallet movement, parent and child round IDs and the final feature summary. If the sum differs, preserve the evidence and ask support rather than editing the worksheet until it matches. That procedure tests transparency without pretending a small sample proves frequency or return.

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.