Fairy Gate — the two Orb reels sit outside the paylines

Fairy Gate by Quickspin has a 3×5 main board and two extra reels that activate for its Orb mechanics. Those side reels contain only Fairy Orbs and do not participate in paylines.

Fairy Wild Respins

The base-game feature can trigger randomly. When it begins, both extra reels remain active until the feature ends. Each Orb landing adds between two and five Wilds to the first five reels and awards one respin.

More than one Orb can land in a spin, so each must be resolved separately. The sequence ends on the first spin with no Fairy Orb.

Free Spins

Three Bonus Scatters in one spin award ten Free Spins. The two extra reels remain active, and Orbs can appear on every spin. They still add Wilds, but they do not add a respin in this mode. Free Spins cannot retrigger.

Evidence limits

The public page does not expose a readable RTP, payline count or stake range. It does not confirm Fairy Gate at a New Zealand casino.

Frequently asked questions

Verified rule set

Quickspin describes a three-row, five-reel main board accompanied by two extra reels used for Fairy Orb mechanics. The extra reels contain only Fairy Orbs and are excluded from normal paylines. In the randomly triggered base-game Fairy Wild Respins feature, both side reels remain active until the feature ends.

Each landed Orb places between two and five Wilds on the five main reels and awards one respin in the base feature. More than one Orb can land on the same spin and should be resolved separately. The sequence ends on the first spin where neither extra reel produces a Fairy Orb.

Three Bonus Scatters in one spin award ten Free Spins. The extra Orb reels stay active, and Orbs can appear on every feature spin. They still place two to five Wilds but do not add a respin. Free Spins cannot retrigger. The public page does not expose readable RTP, payline count, stakes, maximum exposure or New Zealand availability.

Main board versus Orb reels

Draw the interface as two layers: a 3×5 pay board and two narrow Orb-only reels. Give the side reels labels O‑L and O‑R rather than adding them as reels six and seven in the payline table. This prevents Orb symbols from being counted as normal line contributors.

The main-board coordinates should remain R1C1 through R3C5. When an Orb places Wilds, record their destinations only within those fifteen cells. The Orb’s own side-reel position is a trigger location, not a payline position.

A large animation may visually overlap the board, but the settlement map must preserve the separation. Use the deployed paytable to confirm line paths and never draw a winning line through a side reel.

Random base-feature entry

The provider describes Fairy Wild Respins as capable of triggering randomly in the base game. Record the paid spin, feature-entry message, active side reels and starting counter. Do not invent a Scatter or symbol combination as the trigger when the published overview says random.

Random entry does not mean that the feature is “due” after a number of losing spins. Without an official probability table, no frequency should be published. A short session cannot establish one reliably.

Once the feature begins, both Orb reels remain active until termination. Preserve that state through every respin and attach all events to the same paid round unless history says otherwise.

One Orb event

For a spin with one Fairy Orb, identify whether it landed on O‑L or O‑R. Record the number of Wilds generated—between two and five—and all main-board coordinates. In the base feature, then add exactly one respin to the counter.

Keep three facts separate: Orb count, Wild count and counter addition. One Orb does not mean one Wild, and five Wilds do not mean five respins. The Wild destinations are random valid positions under the deployed rules.

Evaluate the final main board only after all Wild placements from that spin have resolved. The Orb symbol itself remains outside paylines.

Multiple Orb sequence

When both extra reels land Orbs, assign IDs O1 and O2 and resolve each as a separate event. Record two independent two-to-five Wild outputs and, in the base feature, the respin addition associated with each Orb. Use the live history to confirm whether the counter receives two additions and in what display order.

If generated Wild destinations overlap, do not count the same board cell twice in the final mask. Preserve both attempted or displayed events only when the server log supports them. The deployed help must explain how occupied cells are treated.

The total visible Wild count may therefore be lower than the sum of raw Orb output labels if placements overlap or interact. Avoid calculating a maximum without the valid-position and overlap rules.

Base respin counter

For each feature step, record counter before spin, completed respin, Orbs landed, respins added and counter after settlement. This resolves apparent off-by-one differences when the interface deducts a spin before adding new ones.

The sequence ends on the first spin with no Fairy Orb. Save both side-reel results and terminal main grid. Do not continue merely because Wilds remain on the board; the published ending condition is Orb absence.

The public page does not state that Wilds persist between respins. Track each final board according to the live rules and avoid carrying a prior Wild forward by assumption.

Free Spins entry

Three Bonus Scatters in one spin award ten Free Spins. Record their main-board coordinates, award message and starting counter. The side Orb reels are then active for every feature spin.

Do not merge Scatter entry with the random base feature. They are different routes. The provider also states that Free Spins cannot retrigger, so later Scatter appearances should not be reported as an additional feature unless another documented rule applies.

Ten is the starting count, not RTP or a guaranteed number of wins. Keep the Free Spins counter distinct from the base respin counter.

Orb behaviour during Free Spins

An Orb in Free Spins still places between two and five Wilds on the main reels. It does not add a respin or extend the Free Spins counter. Record the Orb and Wild destinations, then leave the counter arithmetic limited to the normal completed feature spin.

This mode difference should appear prominently in any comparison table. A reader who sees the same Orb artwork in both modes might otherwise expect an extension. The mode label, not the symbol appearance alone, determines the counter effect.

When two Orbs land during a Free Spin, resolve both Wild-placement events separately but add zero respins for each. Use the server history to reconcile the final grid and win.

Worked base-feature example

Suppose O‑L lands one Orb and generates three Wilds. The ledger records three destination cells and adds one respin. On the next respin, both O‑L and O‑R land Orbs; record two events, their actual Wild counts and their counter additions. If the following spin shows no Orb, the feature ends.

This example demonstrates event structure, not likely frequency, actual counter display or payout. Wilds must still create valid combinations under the deployed paytable.

Do not infer that a two-Orb event always produces ten unique Wild cells. Each Orb’s upper range is five, while overlap and position rules remain version-specific.

Worked Free Spins example

Suppose a feature spin lands an Orb on O‑R and places four Wilds. Record the four board destinations and settled win. The Free Spins counter decreases according to the normal feature step and receives no Orb-based addition.

If both Orbs land, repeat the placement ledger for each but still add no respins. A later spin with no Orb does not end the ten-spin bonus prematurely; the no-Orb termination rule belongs to base Fairy Wild Respins.

The example separates identical symbol output from different mode-specific counter behaviour.

Paytable, RTP and limits

Open the deployed help and collect main-board paylines, symbol values, Wild substitution, valid Wild destinations, overlap rules, random base-feature operation, Orb resolution order, Scatter entry, stake range, RTP configuration and maximum exposure. Record version and date.

RTP cannot be derived from the two-to-five Wild range, ten Free Spins or counter extensions. Maximum exposure cannot be calculated by assuming two Orbs always generate ten unique Wilds.

If multiple RTP versions exist, publish only the one visible in the inspected build. Keep operator-specific stakes and configuration separate from the global provider summary.

New Zealand availability

Quickspin’s global page does not confirm Fairy Gate for real-money play in New Zealand. Verify operator country terms, eligible account access, signed-in catalogue and matching game help. A demo or provider listing is not enough.

Currency, payments, verification and withdrawals require operator sources. Do not transfer these facts from another market.

Date the check and never recommend bypassing location controls. If availability is unconfirmed, say so directly.

Mobile and accessibility audit

At phone width, both Orb reels must remain distinguishable from the 3×5 board. A cropped side reel can hide an Orb and make the counter change appear unexplained. Test portrait, landscape and reduced-motion states.

Label O‑L, O‑R and every generated Wild with more than colour. The final counter effect should remain visible after animation. Keyboard focus needs to reach help, paytable and round history.

After an interruption, compare mode, Orb reel state, unresolved Orb IDs, Wild mask, counter, balance and round ID before another action.

Support evidence

Save provider, title, version, operator, date, stake, currency, balances and round ID. Add feature mode, side-reel results, each Orb’s Wild count and coordinates, counter changes, terminal event and settlement.

For an extension dispute, specify whether the event occurred in base respins or Free Spins. That distinction determines whether an Orb should add one respin. Ask authenticated support for the server event log.

Never share passwords, authentication codes, private keys or seed phrases. Redact unrelated account information.

Suitability and session control

Fairy Gate may suit readers who like visible side-feature reels and can follow separate counters. It may be unsuitable for anyone who treats repeated Orbs as evidence that another is due or expects feature-spin Orbs to extend the counter.

Set stake, money and time limits before play. Orb appearance and Wild destinations are not player-controlled under the published description. A no-Orb ending is a settled feature condition, not a reason to increase stake.

Treat the end of the base sequence or ten Free Spins as a review point. Generated Wilds are round states, not stored progress.

Publication checklist

• Keep both Orb reels outside normal paylines.
• Record each Orb separately.
• Preserve the two-to-five Wild range per Orb.
• Add one respin per base-feature Orb according to the live counter.
• End the base sequence on the first no-Orb spin.
• Record three Scatters and ten Free Spins separately.
• Add no Orb-based respin during Free Spins.
• State that Free Spins cannot retrigger.
• Source RTP, stakes, paylines and maximum from live help.
• Confirm New Zealand access with operator evidence.

Editorial conclusion

Fairy Gate is best explained through a mode-aware Orb ledger. The side reels never become paylines, but each Orb can alter the main board. In base respins, it also extends the counter; in Free Spins, it does not. That single distinction prevents the most important interpretation error.

The public source supports layout, Wild range, termination and Free Spins rules. It does not support invented mathematical values or local availability. Keeping those limits explicit produces a complete mechanics review without borrowed facts.

Orb-resolution worksheet

Use one row per Orb, even when two appear on the same spin. The columns should contain mode, side reel, Orb ID, generated-Wild count, destination coordinates, counter addition and resulting board. In base Fairy Wild Respins the counter-addition field is one; during Free Spins it is zero.

After all Orb rows for a spin are complete, create one consolidated final-board row. This prevents intermediate placement masks from being evaluated as separate wins. If two Orbs target the same position, preserve the server-reported sequence and count the final cell once unless the game rules describe another treatment.

The worksheet also makes termination auditable. A base-feature row showing no Orb on O‑L and no Orb on O‑R is the published stopping event. During Free Spins, the same no-Orb side result merely means that spin receives no Orb-generated Wilds.

Counter arithmetic check

Record the number before a base respin, deduct the played respin according to interface order, then add one for every landed Orb. Some clients display the addition before the decrement; the final settled counter and server event log are decisive. Do not infer an error from one mid-animation frame.

For Free Spins, record the normal feature decrement and no Orb-based addition. If the counter increases, identify a different documented cause rather than attributing it to the Orb. The provider explicitly distinguishes the modes.

This arithmetic should be illustrated with labelled examples but never presented as a prediction of how many Orbs will appear. Feature duration remains random within the rules.

Maintenance and direct answers

Archive the provider description, deployed help, paytable, Orb screenshots and round histories under one version and date. Recheck side-reel behaviour, Wild range, base extension, Free Spins non-extension, RTP and maximum exposure whenever the build changes.

Do Orb reels contribute to paylines? No. Does one base-feature Orb add five respins when it produces five Wilds? No; it places two to five Wilds and adds one respin. Does an Orb extend Free Spins? Not under the published rule. Does a spin without an Orb end Free Spins? No; that termination belongs to base respins. Can the provider page prove New Zealand availability? No.

Before release, rerun word-count, exact-duplicate, link and mobile checks. Confirm the artwork caption identifies an editorial illustration and that every numeric FAQ answer appears with the same qualification in the body. The final page should let a reader reconcile Orb count, Wild count and counter effect without confusing the two side reels with the pay board.

Retain the completed worksheet with the round ID and final account-history credit. That evidence shows whether every Orb was processed once, whether the correct mode-specific counter rule was applied and whether the final main-board settlement matches the operator record.

What is the main layout? Three rows and five reels.

Are the two extra reels part of paylines? No.

How many Wilds can one Orb add? Between two and five.

What ends Fairy Wild Respins? A spin with no Fairy Orb.

How many Free Spins do three Scatters award? Ten.

Can Free Spins retrigger? No.

Is New Zealand availability confirmed? No.

Official source

• Quickspin: Fairy Gate

Bottom line: keep the two Orb reels outside the payline calculation and apply their extension rule according to the active mode.

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 Quickspin, 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.