NZ-NI-0692 · supplier source record
Rook’s Revenge cascade and multiplier guide
A source-led method for recording 25-line cascades and the free-spin multiplier without inventing trigger counts or paytable values absent from the public page.
Supplier sources below. Operator eligibility needs a separate check.

Betsoft lists Rook’s Revenge as live from 18 February 2014. Its official page confirms five reels, 25 paylines, cascading reels, 93.66% RTP, high volatility and a 38.06% hit rate. During free spins, cascading wins can build a multiplier up to 15x.
The public feature captions are otherwise blank. Trigger symbols, starting spins and the precise multiplier ladder must be read from the deployed Help.
Verified specification
| Field | Official value | Live check |
|---|---|---|
| Listed date | 18 February 2014 | Build revision |
| Reels | 5 | Row count |
| Paylines | 25 | Route diagram |
| RTP | 93.66% | Active profile |
| Volatility | High | Studio label |
| Hit rate | 38.06% | Local definition |
| Reel action | Cascading | Settlement order |
| Free-spin multiplier | Up to 15x | Ladder and reset |
Cascading paid rounds
Save the stopped grid before winners disappear. Circle every contributing payline, write the award and number the replacement state. Continue until no new win forms. All cascades belong to one paid round unless Help states otherwise.
Do not merge several cascade stages into one visual total. A later symbol may occupy the same coordinate as an earlier winner, so each state needs its own grid.
The complete paytable, Wild exclusions and stake range are not exposed in accessible public copy. Capture them from active Help and date the evidence.
Free-spin multiplier
Betsoft confirms that cascading wins during free spins can award a multiplier up to 15x. Record the multiplier before each spin, after every successful cascade and at feature end.
Current Help must define its starting value, increment, whether it persists between spins and whether it resets after a losing result. Do not assume a common cascade ladder.
For every multiplied award, keep the base cascade value visible before applying the displayed multiplier. A 15x label is a ceiling, not a guaranteed feature outcome.
Trigger and starting spins
The official overview confirms a Free Spins mode but does not state the accessible trigger or spin count. Record trigger symbols, coordinates, starting counter and any retrigger language from Help.
Keep trigger awards separate from feature wins. If additional spins appear, save the triggering grid and counter change. Never infer a retrigger from an extended animation.
RTP interpretation
The 93.66% RTP is the provider’s published long-run figure. High volatility indicates uneven distribution, and the 38.06% hit rate can include wins below stake.
Use columns for stake, initial line award, each cascade, active multiplier, free-spin subtotal and final credit. Short sessions can verify flow but not mathematical return.
Mobile evidence
On mobile, ensure all 25 lines, cascade stages and multiplier values remain readable. Reduced motion must still show which symbols cleared and the credited result.
After reconnecting, compare the active free-spin counter and multiplier with server history. Preserve the round ID if a cascade replays.
Audit checklist
- Match Rook’s Revenge and the 2014 edition.
- Confirm 93.66% in Help.
- Capture all 25 paylines.
- Number every cascade state.
- Record free-spin trigger and starting count.
- Save the multiplier before and after cascades.
- Verify the documented 15x ceiling.
- Keep base awards separate from multiplied totals.
- Record retriggers only when shown.
- Leave missing paytable and limits unavailable.
- Do not claim NZ or 22Bet access without operator evidence.
Worked cascade ledger
Number the opening board zero. Each cleared-and-replaced board becomes state one, two and so on. Add columns for line award, cascade subtotal and multiplier. During free spins, carry the displayed multiplier only as Help instructs.
At round end, total the recorded stages and compare them with history. Check stake units and simultaneous paylines before reporting any difference.
Cascade-state quality control
Use fixed coordinates for every reel position and redraw the full grid, not only changed symbols. A complete state preserves neighbours that can join the next line. Put server time and multiplier beside every grid.
When two paylines clear simultaneously, record them under one state. A replacement win begins the next state. This prevents simultaneous awards from being mistaken for consecutive cascades and incorrectly advancing the multiplier. If history groups values, leave the unresolved breakdown unavailable rather than allocating it proportionally.
Free-spin ladder verification
The provider confirms a 15x ceiling but not the accessible ladder. Copy every displayed step from Help. Record what happens after a non-winning free spin and whether the multiplier carries between spins.
If a cascade starts at one value and rises during the same spin, preserve each base award. The active rules determine whether the new multiplier applies immediately or later. Never apply the highest visible number retroactively.
Version and title checks
Match the Betsoft provider, 18 February 2014 listing, 25 lines and cascading behaviour. Operator lobbies can truncate the name, so save the title from Help and any build label. A different RTP profile needs its own territory and date.
Responsible interpretation
High volatility and a 15x ceiling make isolated wins visually prominent, but they reveal neither frequency nor expected feature value. Set limits before play and do not extend them because a cascade ladder appears close to its top.
Dispute package
Preserve stake, initial grid, every replacement grid, multiplier states, feature counter and final history. If the display differs only during animation but history settles correctly, describe a timing issue. If history differs, send the complete evidence and active rule to support.
Mapping one cascade from start to finish
Treat the first settled grid as the root of a cascade tree. Mark every winning symbol group on that grid, copy its award, then save the grid after removal and replacement. If the replacement creates another win, give it the next cascade number rather than calling it a new paid spin. Continue until a grid settles without a further cascade. This keeps the original stake attached to all dependent events.
The official description confirms cascading reels, but the live paytable remains necessary for symbol values and qualifying patterns. Do not infer a cluster size, line route or ways-to-win rule from the fact that symbols disappear. Copy the exact evaluation method from Help and use it consistently through the ledger.
During free spins, add a separate multiplier column. Betsoft states that the free-spin cascade multiplier can increase to 15x. Record the value shown before each cascade and after it resolves. “Up to 15x” is a ceiling for this mechanic, not a promised endpoint for every feature. A sequence that ends earlier is not evidence of an error unless the active rules say another step should have occurred.
What to verify before comparing versions
Confirm the title punctuation, Betsoft studio name, RTP, 25-line count, volatility label and hit rate inside the active build. The official catalogue values provide a primary reference, but a deployed Help panel determines which configuration the player is seeing. Preserve the date, operator domain and any version string so a later check does not overwrite the original observation.
For feature comparison, capture the trigger, initial free-spin award, retrigger wording, multiplier reset rule and maximum shown value. If one of those fields is not disclosed, leave it blank. Another review may describe a valid configuration from a different date or territory, but it cannot fill a gap in this build without matching evidence.
The same discipline applies to stakes and payout tables. A minimum stake from one operator should not be presented as a universal Betsoft limit. Currency conversion, coin values and account settings can alter the visible control range even when the game’s core mechanic is unchanged.
Mobile cascade usability
On a phone, watch whether the game keeps the cascade number, multiplier, remaining free spins, total stake and settled award legible at once. Animations can move quickly, so open history after a multi-stage result instead of relying on the last frame. Rotation or browser toolbars should not hide Help or the balance display.
If connectivity drops, do not place a replacement spin merely because the cascade animation disappeared. Re-enter through the authenticated lobby and compare the server round with the last saved cascade state. Include the time zone when reporting the event; several cascades can belong to one round identifier.
Suitable reader and responsible boundary
Rook’s Revenge is easier to understand for readers who enjoy documenting linked results and a rising feature multiplier. It is less suited to someone who wants each visual change to represent a separate paid decision. High volatility describes uneven distribution and does not make a long non-winning sequence predictive of the next cascade.
Choose the session limit before the paid spin and do not increase it because the multiplier appears to be approaching 15x. The multiplier is conditional on the feature sequence; it does not create a debt that the game must later repay.
Verdict
Rook’s Revenge is best reviewed as a state sequence rather than a single stopped grid. Its central verified distinction is the free-spin cascade multiplier reaching up to 15x.
The official page does not justify invented trigger counts, paytable values or local availability. Those remain deployment checks.
FAQ
What RTP is published?
93.66%.
How many paylines?
Twenty-five.
What is the published multiplier ceiling?
Up to 15x during free spins.
Is the trigger publicly detailed?
Not in the accessible product copy.
Is local availability confirmed?
No.
Sources
- Betsoft, Rook’s Revenge, official product page, checked 9 October 2026.
- Betsoft official games catalogue, checked 9 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 Betsoft, 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.
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.
