NZ-NI-0693 · supplier source record
Rockstar paylines and bonus-round evidence
A restrained review of the original 2012 Betsoft title that publishes its mathematics but leaves the bonus-round mechanics to current in-game Help.
Supplier sources below. Operator eligibility needs a separate check.

Betsoft dates Rockstar to 12 January 2012 and publishes five reels, 30 paylines, 93.84% RTP, medium volatility and a 39.54% hit rate. The page includes imagery labelled Main Game, Big Win and Bonus Round, but provides no accessible feature-rule captions.
This means the bonus trigger, decisions and prizes cannot be stated as fact without the deployed Help document.
Verified specification
| Field | Official value | Live check |
|---|---|---|
| Listed date | 12 January 2012 | Exact revision |
| Reels | 5 | Row layout |
| Paylines | 30 | Line map |
| RTP | 93.84% | Active profile |
| Volatility | Medium | Studio label |
| Hit rate | 39.54% | Local definition |
| Bonus round | Confirmed visually | Trigger and rules |
Payline and paytable capture
Open Help before the first paid round. Save all 30 paylines, symbol values, matching direction, Wild behaviour and Scatter rules. Trace each winning route on the stopped grid.
The provider page does not disclose stake limits, maximum win or paytable values in text. Avoid borrowing values from another Rockstar-named game or an aggregator.
Record currency and stake unit so paytable multipliers can be reconciled with account history.
Bonus-round boundary
The official page confirms that a Bonus Round image exists but does not expose the trigger, starting state or settlement. Capture the actual instruction screen and all available actions.
If the user chooses among objects or outcomes, log every selection. If the feature plays automatically, do not imply skill. Preserve the feature subtotal and server round ID.
RTP and hit-rate reading
The 93.84% RTP is a theoretical long-run return. Medium volatility describes distribution, while 39.54% hit rate may include returns below stake. None predicts the next round.
Keep base stake, line wins, bonus award and final credit separate. A short session cannot validate the published percentage.
Mobile and continuity
Confirm that line controls, paytable and bonus instructions remain readable on a narrow screen. Focus states and final awards should remain visible without relying on concert animation.
After reconnecting, compare unfinished bonus state and balance with history. Replayed graphics are not evidence of a second credit.
Evidence checklist
- Match Rockstar and Betsoft.
- Confirm the 2012 edition.
- Verify 93.84% in Help.
- Capture all 30 paylines.
- Save Wild and Scatter exclusions.
- Preserve the bonus trigger screen.
- Record each bonus action and settlement.
- Keep bonus totals outside ordinary line awards.
- Leave stake limits and maximum win unavailable until verified.
- Do not claim New Zealand or 22Bet deployment from provider publication.
Worked record
Create a header with version, stake, currency and round ID. Use one row per paid line. When the bonus opens, start a second table containing the instructions, actions, interim values and final credit.
Compare the combined result with history. If a difference remains, check units and simultaneous lines before contacting support.
Building a complete rules record
Because the feature captions are blank, use the first lawful launch to document rules rather than chase an outcome. Capture title, version, RTP, lines, symbol table and bonus instructions together. List trigger count, actions, award units, substitutions, Scatter payments, retriggers and maximum-award wording. Mark omissions as “not shown.”
Thirty-line reconstruction
Draw stable coordinates and number all 30 lines. For every award, note line number, symbols, matching length, paytable multiplier and currency result. Identify Wild coordinates and substitutions. Sum simultaneous wins once and compare them with history after checking whether the table uses total bet, line bet or coin value.
Bonus evidence without assumptions
Save the exact moment the feature opens and its instructions before acting. Equal-looking choices do not prove equal probabilities. If collect-or-continue decisions exist, document presented values without suggesting a winning strategy. Retain interim totals and the final server credit.
Comparing public and deployed data
Check the public 93.84% RTP against active Help. If another figure appears, record operator, territory, currency and date; never average profiles. Medium volatility and 39.54% hit rate do not establish bonus frequency.
Mobile usability
Test both orientations. The line map, instructions and award must remain readable without clipping. Audio cues need visible equivalents, and selection cannot rely only on colour. Reduced motion should still reveal settlement.
Support package
A useful report contains build, round ID, stake, time, balances, stopped grid, instructions, actions and history. Preserve originals separately from annotated copies.
How to review a legacy title without inventing rules
Rockstar’s official page establishes a five-reel, 30-line Betsoft game with a listed date in 2012, a 93.84% RTP, medium volatility and a 39.54% hit rate. It also presents bonus imagery, but the public text checked for this review does not explain the trigger, award count, retrigger condition or special-symbol behaviour. The correct editorial response is to preserve that boundary, not to complete the rules from a similarly named title.
Start with an identity capture from the deployed Help panel. It should show the exact title, studio, RTP and line configuration. Add the operator domain, date, language and any build identifier. If the live panel provides a full feature explanation, store it as deployment evidence and describe only what it states. If the panel is missing or inaccessible, the feature details remain unavailable.
Videos and screenshots can demonstrate that an animation existed in a particular session, but they do not necessarily establish its mathematical rule. A still bonus screen cannot prove how it was triggered, whether a retrigger is possible or how symbols are valued. Use visual evidence to support a timeline, then use Help or official documentation for the rule.
Reconstructing the 30-line settlement
Before a paid round, record the total stake and whether all 30 lines are active by design. After settlement, trace each highlighted route against the line map. Write the participating symbols, count, paytable value and any substitution separately. If the interface shows only a combined award, use account history to confirm the total rather than distributing it across lines by guesswork.
The paytable capture should include ordinary symbols, Wild and Scatter definitions if present, bonus icons, bet units and any maximum-award wording. None of those values should be imported from another site merely because it uses the same promotional image. Older games can have multiple historical deployments, and an operator may retain a configuration after the public product presentation changes.
Create one row per paid round and link every dependent animation to that row. A bonus round, free-spin sequence or pick screen should not be counted as another paid wager unless history shows a separate stake. This distinction keeps the wager total, feature award and closing balance reconcilable.
RTP, hit rate and session expectations
The published RTP is a long-run theoretical percentage, not a return promised to one account. The 39.54% hit rate describes how often the mathematical model records a hit under its defined conditions; it does not say how many hits exceed the stake. Medium volatility is a broad distribution label and cannot forecast when a feature will appear.
These fields are useful for comparing documented configurations, but not for chasing a result. A sequence of losses does not make the next spin more likely to produce the bonus. A series of small hits does not prove the session is profitable. Compare opening and closing balances with total stakes if evaluating what happened.
Set time and money limits before opening the game. Do not revise them because stage lights, progress-style graphics or bonus imagery suggests that an event is close. Unless Help explicitly defines persistent progress, decorative states should be treated as presentation only.
Mobile and desktop evidence differences
On mobile, ensure the total stake, balance, Help control and all reel positions remain visible in the intended orientation. Open the line map and symbol table before full-screen mode. If a bottom browser bar overlaps controls, leave full screen and confirm the value before continuing. Rapid taps during an unresolved animation can also make the session record harder to read.
On desktop, browser zoom and overlays can hide line indicators or the final total. Keep one active game tab, make sure the complete grid is visible and save the history entry after any multi-stage result. The underlying evidence fields are the same on both devices even though their locations differ.
When a connection drops, allow the authenticated session to restore the server outcome. Do not assume that an unfinished animation means the wager was cancelled. Compare the round ID, stake and final balance; then contact support through the operator’s official channel if the records conflict.
Decision guide
Rockstar may interest readers looking for a conventional 30-line Betsoft format and willing to inspect an older title’s active Help before relying on a feature description. It is a poor candidate for someone who requires every bonus rule to be verifiable from a current public product page alone.
The central comparison points are therefore evidence quality, line structure, published RTP and the completeness of the deployed rules. Theme and age can help identify the game, but neither proves present availability in New Zealand. Operator access, stakes, paytable values and bonus details must all be checked in the account that actually loads the title.
Editorial conclusion
Rockstar’s official page is sufficient for identity and headline mathematics, not for a detailed bonus description. The correct article makes that limitation visible instead of filling the gap with inherited rules.
Readers can still verify a great deal: exact title, provider, date, RTP profile, volatility, hit rate and all 30 deployed paylines.
FAQ
What RTP does Betsoft publish?
93.84%.
How many paylines are listed?
Thirty.
Is a bonus round confirmed?
Yes, but its accessible public rules are incomplete.
Is the title new?
No. Betsoft lists it from January 2012.
Is NZ availability confirmed?
No.
Sources
- Betsoft, Rockstar, 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.
