Geisha's Revenge rules, multiplier windows and RTP

Geisha’s Revenge is PG Soft catalogue ID 1702123, code geisha-revenge. The current English file is version 1.0 r4, updated 13 August 2026. It uses five reels with five separate rows on reel one and six rows on reels two through five, producing between 240 and 6,480 ways.

PG Soft records 96.78% RTP, high volatility and a 5,000× maximum. The game centres on five multiplier windows aligned with reel-one rows. Their behaviour differs between the paid game and Free Spins, so persistence must be tracked carefully.

Verified configuration

Field	Official value	Evidence scope
Identity	1702123 · geisha-revenge	Current catalogue
Document	1.0 r4 · 13 August 2026	English rules file
Layout	Reel 1: 5 rows · reels 2–5: 6 rows	Variable symbol sizes
Ways	240–6,480	Base bet 20
RTP	96.78%	PDF and catalogue agree
Volatility	High	Supplier classification
Overall hit rate	28.59%	PDF summary
Maximum win	5,000× bet	Round stops at cap
EUR reference range	€0.20–€100	Not an NZD limit

The return is allocated as 69.54 percentage points to the main game and 27.27 to Free Spins. The reported hit rates are 28.19% and 0.40% respectively. These are model-level statistics, not a schedule for when an individual feature will appear.

Ways and symbol footprint

Some symbols can occupy two to four spaces. The rules treat each large symbol as one symbol when calculating a payout. A four-space image is therefore not four independent matching symbols. Record its footprint, but count it according to the ways calculation shown in Help.

Wild substitutes for all symbols except Scatter and appears only on reels two through five. Since Wild does not appear on reel one, it cannot itself activate one of the five left-side windows. The activating result must contain a winning regular symbol in the corresponding reel-one row.

Multiplier windows in the paid game

At the start of each main-game spin, all five windows are inactive. After wins are paid, any winning symbol located in row one, two, three, four or five of reel one affects the aligned window:

• an inactive window becomes active;
• an already active window increases by 2×;
• multiple qualifying rows can affect different windows in the same spin.

At the end of the spin, wins are multiplied by the sum of the current window values. This is additive, not a chain where every window multiplies the next. A replay should preserve the reel-one rows that took part in each collapse, the window state before activation and the displayed total after the last cascade.

Because main-game windows reset at the beginning of the next paid spin, a large total cannot be carried forward. The animation may keep attention on the left rail, but the settlement record should show whether the factor belonged to the current spin or to a previous one.

Example of a window ledger

Suppose rows one and four on reel one contribute to the first collapse. Mark those two aligned windows as active and leave the other three inactive. If row four contributes again after the collapse, increase only the fourth window by 2×. A later win on row two activates the second window; it does not alter rows one or four. At settlement, add the five displayed window values exactly as the client presents them.

This example is a recording method, not a forecast of values. The source does not assign a guaranteed starting factor to a newly activated window in the extracted text, so the loaded display is decisive. Never fill a missing number from memory or from a different regional build. Capture the window rail immediately after every paying collapse and before the next animation covers it.

For Free Spins, continue the same five-column table across spin boundaries. Add a separate row for the remaining-spin counter and any retrigger. If a connection resumes with different values, stop and compare the last server-history entry rather than continuing to wager. This produces a usable chronology for support without relying on a long screen recording.

Also record any large symbol spanning multiple spaces as one payout object. Its footprint may touch several rows visually, but only the winning reel-one position or positions shown by the engine determine which windows change. The ways total and window rail should be read together.

Free Spins trigger and persistence

Three Scatters anywhere award ten Free Spins. Each additional Scatter adds two spins, and the feature can retrigger. The five windows start inactive when Free Spins begin, then use the same row-based activation and +2 increase rule.

The crucial difference is persistence: values in the windows remain until the entire Free Spins feature ends. A qualifying symbol on reel one can therefore build a window across later spins. At the end of each free spin, that spin’s wins are multiplied by the sum currently displayed.

A good feature log has five columns, one for each row. After every spin, write “inactive” or the shown factor, plus any retrigger. This avoids reconstructing an additive total from the celebration screen. If two rows increased in one collapse sequence, record both before moving to the next spin.

Feature Buy and cap

Version 1.0 r4 documents a Feature Buy menu. The supplier file does not provide one universal price; the client displays the cost before confirmation. That price must be captured from the loaded version and currency. A sponsored link on this site is not a buy button for Geisha’s Revenge and is not labelled as a demo.

If main-game or feature winnings reach 5,000× the bet, the spin ends. The cap limits settlement; it does not state the probability of reaching the amount. High volatility is a broad session characteristic rather than a prediction for a chosen stake.

RTP and configuration identity

The PDF and catalogue both display 96.78%, which reduces ambiguity for the reference version. It still does not prove that every operator deploys the same configuration. Record the Help-screen value, version text and time of check.

The default PDF range is €0.20 to €100, built from bet sizes 0.01, 0.1 and 0.5 across ten levels. Those EUR values should not be presented as NZD stakes. Currency conversion, rounding and local limits belong to the authenticated client.

Mobile layout and evidence

The supplier lists iOS, Android, HTML5, macOS and Windows and gives 1080×2340 as the portrait reference. On a narrow screen, the five multiplier windows, reel-one row boundaries and variable ways count should remain visible. If a large symbol covers multiple cells, verify that the history view identifies it as one symbol.

For an interrupted Free Spins session, compare the restored five-window state with the last completed round in history. The persistent values and remaining-spin counter are more useful than a screenshot showing only the final win banner.

Availability boundaries

An official global listing establishes the title and its source material, not its presence in a New Zealand operator lobby. This review makes no claim that 22Bet or another sponsored destination offers the game locally.

A supplier preview, if accessible, can demonstrate controls and terminology. It does not establish a real-money account, NZD support, withdrawals or local authorisation. Those questions require separate operator evidence.

Who may prefer this structure

Geisha’s Revenge may appeal to readers who like feature progress that can be written as five visible values. The row-to-window relationship gives a clearer audit trail than a purely random multiplier banner.

It is less suitable for someone who prefers fixed symbol sizes, low volatility or a bonus without persistent state. The variable footprint and collapse rounds demand careful replay reading.

Verification sequence

1. Match ID 1702123 and code geisha-revenge.
2. Confirm version 1.0 r4 and 96.78% RTP.
3. Record which reel-one rows join each win.
4. Add active window values rather than multiplying them together.
5. Distinguish one-spin main-game windows from feature-wide persistence.
6. Save the trigger board, round ID and account settlement.

FAQ

How many ways does Geisha’s Revenge use?

The checked rules show a range from 240 to 6,480 ways.

How do multiplier windows activate?

A winning symbol in a reel-one row activates its aligned window or increases an active value by 2×.

Do paid-game multipliers persist?

No. The windows reset at the start of every main-game spin.

What triggers Free Spins?

Three Scatters award ten spins; each extra Scatter adds two, and retriggers are allowed.

What are the RTP and cap?

PG Soft states 96.78% RTP and a 5,000× maximum for the checked reference version.

Is access in New Zealand verified?

No. The source confirms the game, not local operator deployment.

Sources

• PG Soft, Geisha’s Revenge Game Information, version 1.0 r4, updated 13 August 2026.
• PG Soft official catalogue record for ID 1702123, checked 8 October 2026.

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.