Rabbits, Rabbits, Rabbits!: Wedding Bonus rules and paytable guide

Rabbits, Rabbits, Rabbits! is an Endorphina slot built on five reels, three rows and ten paylines. The supplier page checked on 8 October 2026 lists 96.05% RTP, high volatility and a €0.10–€60 reference stake range. Its defining event is the Wedding Bonus, a hold-style collector triggered when Mr Rabbit and his fiancée appear together on reels one and five.

Those published details describe the supplier build, not availability or limits at a New Zealand operator. A player should confirm the exact title, version, currency, RTP and help file after the game loads. The euro range must not be relabelled as an NZD range.

Published configuration

Field	Provider value
Grid	5×3
Paylines	10
Provider RTP	96.05%
Volatility	High
Bet reference	€0.10–€60
Bonus trigger	Mr Rabbit on reel 1 and fiancée on reel 5
Collector size	15 positions

This snapshot is useful for identifying a deployment. It is not a session forecast. If the loaded information panel gives another RTP or wager ladder, record the screen and treat it as a separate configuration rather than blending the two.

Base-game line reading

Ordinary wins should be checked against the ten-line map. Start at the leftmost reel, follow one active path at a time and note the symbol count. A matching cluster that does not sit on a published line is not automatically a win.

The dollar sign with rabbit ears is the Wild. Endorphina says it appears only in the main game and substitutes for all other symbols. Five Wilds are published at 18× base bet. The car is the next highlighted ordinary symbol, with five cars paying 10× base bet. Remaining values belong to the active paytable.

“Base bet” needs its live definition. It may not equal the total amount shown for all ten lines. Before translating a multiplier into account currency, save the wager panel and compare one settled line with round history.

Wedding Bonus trigger

The two character symbols have positional roles: Mr Rabbit must land on the first reel and his fiancée on the fifth. Their simultaneous appearance triggers the Wedding Bonus. This is not described as a three-Scatter trigger, so importing Scatter logic from another title would be wrong.

Capture the complete triggering grid. It should show both bookend characters, the total stake and the transition into the bonus. If only one character appears, the public rule does not support a trigger. The loaded help remains decisive if animation obscures a reel position.

Beds, hats and hearts

The Wedding Bonus uses a 5×3 field. Beds can reveal one or more baby rabbits; hats conceal additional bronze, silver or gold awards; hearts keep the feature moving. Beds and hats remain locked after landing, while a heart is associated with continued spins rather than a retained cash object.

These roles should not be merged. A bed is the route to the baby-rabbit count, whereas a hat carries its own concealed reward. A heart affects continuation. When documenting a round, label each newly landed object by type and coordinate.

The provider page states that each hat can award up to 100× total bet. That ceiling belongs to a hat award and should not be presented as the whole feature maximum. Equally, “up to” describes a limit, not a typical outcome.

Attempt counter and completion

The bonus begins with three attempts. A new bed or hat resets the counter to three. If no qualifying object arrives, the counter falls. The feature ends when the counter reaches zero or when all 15 positions have been filled.

A simple audit table needs five columns: spin number, attempts before spin, new locked item, attempts after spin and occupied positions. This reveals whether a bed or hat reset was applied. Hearts should be noted separately according to the current help because their continuation behaviour is not the same as locking a new object.

Do not count an animation twice. If a bed opens to reveal several baby rabbits, it is still one occupied grid position but may increase the rabbit total by more than one. The screen-fill condition concerns positions, while the rabbit award concerns the revealed count.

Baby-rabbit reward scale

Endorphina publishes a reward range from 2× to 4,000× total bet based on the number of collected baby rabbits. The public page does not expose every intermediate step in a plain table. Therefore, only the endpoints and the dependency on rabbit count can be reported from that page.

For a real round, capture the final number of baby rabbits and the displayed award before leaving the summary. Do not infer an intermediate multiplier by linear interpolation. A bed containing multiple babies may move the count farther than the number of beds suggests.

The 4,000× figure is an upper published reward in this mechanic, not a promise that filling all 15 cells automatically returns that amount. The active help should be used to connect any specific count to a specific award.

Worked collector audit

Suppose the opening bonus display shows three attempts. A hat lands in the upper-left position: record one locked cell, the revealed hat award and the reset to three. The next spin produces nothing, so record the counter reduction. A bed then lands and reveals two baby rabbits: record one additional occupied cell, two rabbits and another reset.

Continue until the summary appears. Add hat awards only once, keep the rabbit-count award separate and compare their displayed combined value with round history. If the summary uses total-bet multipliers, multiply by the documented total stake, not an assumed per-line value.

If the sequence ends with empty cells, the likely cause should be a zero counter; if all cells are occupied, note the completion route. This evidence is more reliable than reconstructing events from memory after animations finish.

Risk and optional controls

The supplier lists Classic Risk, with up to ten doubling decisions on an eligible settled win. Risk is a separate voluntary step after a result. It does not increase the stated Wedding Bonus ceiling and should not be included when describing the underlying feature payout.

Endorphina also lists Bonus Pop for the title. Such options can depend on jurisdiction and operator configuration. Confirm whether it is present, read its price and changed conditions, and never assume the ordinary trigger probability or RTP remains identical after selecting it.

Declining an optional control provides the cleanest first audit. Once the standard feature has been documented, any paid shortcut or post-win decision can be tested as a separate path.

RTP, volatility and practical limits

The published 96.05% RTP is a theoretical long-run return for the identified setting. It cannot predict when the wedding characters, a hat or a high rabbit count will appear. High volatility signals a broader distribution pattern, not a guarantee of large prizes.

The provider’s €0.10–€60 range is a catalogue reference. An operator may offer other currencies or steps. New Zealand availability cannot be inferred from the supplier page, and currency conversion does not establish an approved local minimum or maximum.

Set a spend and time ceiling before a test. Collector animations can make a feature feel longer than the number of paid rounds suggests, so preserve both elapsed time and round count.

Mobile and evidence checklist

On mobile, confirm that the first and fifth reels, attempt counter, all 15 bonus positions and final summary remain visible without an overlay. Test how to open history before committing a stake. Rotate only if the game supports it without resetting the feature.

Before play, record:

• exact title and supplier;
• version and published RTP in loaded help;
• account currency and total stake;
• ten-line map;
• Wedding Bonus trigger wording;
• bed, hat and heart definitions;
• available optional controls;
• access date and operator domain.

For a support query, add the round ID, trigger screenshot, chronological collector table and final settlement. This gives the operator enough information to distinguish a missed rule from a technical fault.

Common interpretation errors

• Calling the two character symbols ordinary Scatters.
• Treating every heart as a permanently locked cash object.
• Counting multiple baby rabbits as multiple occupied cells.
• Presenting 100× per hat as the entire bonus maximum.
• Assuming 4,000× follows automatically from a full grid.
• Applying a base-bet line value to total stake without checking units.
• Including Risk outcomes in the base feature paytable.
• Claiming New Zealand availability from catalogue presence.

Final assessment

Rabbits, Rabbits, Rabbits! is easiest to verify when the feature is divided into trigger, counter, occupied cells, rabbit count and hat awards. Each layer has a different job; collapsing them produces misleading explanations.

The official page supports the 5×3 layout, ten lines, 96.05% RTP, high volatility, positional trigger and published reward ceilings. The current in-game help must still confirm the complete paytable, intermediate rabbit awards, optional controls and the configuration offered to the account.

Official and related sources

• Rabbits, Rabbits, Rabbits! official product page
• Endorphina 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 Endorphina, 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.