Dragon Shrine — one full Dragon stack starts the respin

Dragon Shrine by Quickspin is described by its developer as a 40-betline game built around the Dragon Stack Respin. The important reading task is to distinguish the base-game trigger from the version used during Free Spins.

Dragon Stack Respin in the base game

A stack of Dragon symbols must fill reel one to trigger the feature. “Stack” here means a complete reel, not one Dragon symbol or a partial group. The official page does not describe reel five as a base-game trigger.

That boundary is useful when reviewing a result: identify the current mode, check reel one and record whether the Dragon occupied every visible position. Do not infer a trigger from a dramatic animation alone.

Ten Free Spins from three Scatters

Three Bonus Scatter symbols in one spin initiate ten Free Spins. The official rules state that those Scatters can appear on reels two, three and four. This is a position-specific trigger rather than an anywhere-on-the-grid collection rule.

During Free Spins, a full Dragon stack on either reel one or reel five can activate the Dragon Stack feature. The second outer reel therefore matters only after the bonus begins.

RTP, stakes and New Zealand availability

The public Quickspin page does not expose a readable RTP value, stake range or paytable. Those fields must be checked in the help for the exact deployed version. The source also does not confirm that Dragon Shrine is available at a New Zealand casino.

Frequently asked questions

Verified mode map

Quickspin describes Dragon Shrine as a 40-betline title. In the base game, a complete Dragon-symbol stack filling reel one triggers the Dragon Stack Respin. The accessible description does not give reel five the same base-game role.

Three Bonus Scatters in one spin award ten Free Spins. The Scatters can appear on reels two, three and four. During Free Spins, a complete Dragon stack on either outer reel—one or five—can activate the Dragon Stack feature.

The public page does not expose readable RTP, stake range, reel height, symbol paytable, full respin behaviour, maximum exposure or New Zealand availability. These fields require the deployed help and operator evidence.

Full-stack verification

Record reel height from the live game and mark every Dragon coordinate on the trigger reel. A complete stack must occupy all active positions. A partial group, cropped illustration or nudge-like animation is not enough unless the game history confirms full-reel status.

Use DS1 for a reel-one stack and DS5 for a reel-five stack. Preserve source mode, stopped grid and feature message. This makes the outer-reel distinction visible before any respin result is interpreted.

Do not infer that a large Dragon graphic covers the complete reel. Match artwork to the actual cell boundaries and paytable label.

Base-game reel-one boundary

In the base game, inspect reel one only for the published Dragon Stack Respin trigger. A full Dragon stack on reel five should not be described as the same trigger without a deployed rule extending it.

Save the mode indicator because identical outer-reel artwork may appear during Free Spins. The mode, not visual symmetry, determines whether reel five is eligible.

If an apparent reel-five base trigger occurs, preserve version and server history and ask support. Do not silently rewrite the provider rule from one animation.

Base respin ledger

Once DS1 triggers, record starting counter or feature state, locked or transformed symbols, each respin grid and settlement. The public summary confirms the trigger but not all continuation and ending rules, so use the live help rather than inventing a fixed count.

Attach every respin to the original paid round. Verify no additional stake debit and reconcile final credit with account history.

If further Dragon stacks affect the sequence, record their reel, mode and counter change exactly as the deployed rules describe.

Scatter trigger on reels 2–4

Create three columns for reels two, three and four and mark the Bonus Scatter coordinates. The provider says Scatters can appear on these reels, but the deployed paytable should confirm whether one on each reel is required for the three-symbol trigger.

Do not count Dragon stack cells as Scatters unless the paytable explicitly permits substitution. Save the feature message and ten-spin starting counter.

Ten is a spin count, not RTP, multiplier or expected number of wins. Any retrigger rule must be sourced from the live version.

Free Spins outer-reel rule

During Free Spins, inspect both reel one and reel five. A complete Dragon stack on either can activate the Dragon Stack feature. Record DS1 or DS5 separately and preserve all cells.

Do not require both outer reels unless the live help states a separate dual-stack event. The public wording supports either outer reel. Likewise, a partial stack on each side does not equal one complete stack.

Keep any nested respin counter distinct from the remaining ten-spin feature counter. Server history decides whether a nested step consumes a Free Spin.

Worked base example

Suppose a full Dragon stack fills reel one in a paid spin. Mark all positions DS1, record the feature message and open the base respin ledger. Settle each subsequent state according to the live paytable.

A full stack on reel five in an otherwise similar paid spin is not labelled a verified base trigger from the public description. It belongs in the evidence log for further checking.

The example explains the mode boundary and does not claim feature length, payout or probability.

Worked Free Spins example

During one of the ten Free Spins, a complete Dragon stack fills reel five. Mark DS5, preserve the current feature counter and record the Dragon Stack event. If another event later appears on reel one, use DS1 and a separate timeline.

A large but incomplete Dragon on reel five does not trigger under the full-stack condition. Count active positions before updating state.

This example does not add an unsupported retrigger or counter value.

Forty-betline settlement

Obtain all 40 line paths and symbol values from the deployed paytable. For every respin or Free Spin, map Dragon Wild or stack participation and credited combinations. A full reel can support multiple lines but remains one stack event.

Where one coordinate belongs to several winning lines, link it rather than duplicating the cell. Compare award totals with account history.

Forty betlines do not reveal RTP, hit rate or maximum exposure. Those require certified configuration data.

RTP, stakes and maximum

Open live help and record version, reel height, 40 line paths, Dragon substitutions, base respin rules, Free Spins outer-reel behaviour, Scatter trigger, stake range, RTP and maximum exposure. Preserve operator and review date.

Do not calculate RTP from ten Free Spins or a full stack. Do not infer maximum payout from the number of active lines.

If multiple RTP versions exist, publish only the value displayed for the tested build. Avoid combining data across deployments.

New Zealand availability

Quickspin’s global page does not prove real-money availability in New Zealand. Verify operator country terms, account eligibility, signed-in catalogue and matching help. A demo or provider listing is insufficient.

Currency, payments, identity checks and withdrawals require operator sources. Do not infer them from global game availability.

Date the evidence and never recommend bypassing geographic controls. Mark local access unconfirmed when necessary.

Mobile and accessibility audit

At phone width, the complete outer reel must remain visible so a full stack can be distinguished from a partial one. Test reel one and reel five in portrait and landscape, including nested feature overlays.

Use written DS1/DS5 labels or patterns rather than colour alone. Keyboard focus must reach help, paytable and history. Reduced motion should preserve final stack and counter state.

After interruption, compare mode, outer stack coordinates, counters, balance and round ID before continuing.

Support evidence

Save provider, title, version, operator, date, stake, currency, balances and round ID. Add mode, stack coordinates, Scatter grid, feature counters, all respin states and final settlement.

For a missing trigger, specify reel and prove complete active-height coverage. Ask authenticated support for the server event and rule version.

Never share passwords, authentication codes, private keys or seed phrases. Redact unrelated personal data.

Suitability and session control

Dragon Shrine may suit readers who prefer a clear position-specific trigger. It may be unsuitable for anyone who treats a partial outer stack as near-certain progress or chases reel five outside the mode where it is eligible.

Set stake, money and time limits before play. The player cannot force a full Dragon stack or Scatter pattern under the published rules. A near-full reel has no stored cash value.

Treat the end of a respin or ten-spin feature as a review point rather than automatically starting another round.

Publication checklist

• Confirm the 40-betline version and active reel height.
• Require a complete Dragon stack.
• Restrict base trigger to reel one.
• Record three Bonus Scatters and ten Free Spins.
• Verify Scatter positions against reels two through four.
• Inspect reel one or reel five during Free Spins.
• Keep base and bonus Dragon Stack events separate.
• Source respin details, RTP, stakes and maximum from live help.
• Confirm New Zealand access through operator evidence.
• Test full-stack visibility on mobile.

Editorial conclusion

Dragon Shrine is primarily a mode-and-position audit. Reel one controls the published base trigger, while Free Spins expand eligibility to both outer reels. Full-height evidence is required in either case.

That distinction, combined with a 40-line settlement ledger and versioned help, produces a complete review without inventing missing counters, mathematical values or local availability.

Full-stack worksheet

Create one row for each active position of the outer reel and columns for base reel one, Free Spins reel one and Free Spins reel five. Mark Dragon, other symbol or inactive. A stack qualifies only when every active row in the relevant column is Dragon.

This worksheet prevents a cropped four-cell illustration from being called full when the live reel has another active row. It also shows that two partial stacks on opposite sides remain two partial stacks rather than one combined trigger.

Attach the feature message and round ID to the completed column. Artwork alone can document appearance, but the server state confirms that the game recognised the stack.

Scatter-position worksheet

Use separate rows for each Bonus Scatter and retain its reel and row. Compare the stopped grid with the live trigger rule. The public page identifies reels two, three and four as Scatter locations, while the deployed help should show the exact three-symbol arrangement.

If several Scatters appear on one reel, do not assume that they satisfy positions on missing reels. If a Wild appears, do not count it as a Bonus Scatter without an explicit substitution rule. Preserve the written ten-spin award.

The worksheet should also record any later Scatter during Free Spins, but no additional counter effect should be claimed without a documented retrigger rule.

Nested-feature counter reconciliation

When a Dragon Stack activates during Free Spins, open a child ledger under the current feature spin. Record Free Spins counter before the event, every nested respin state and the counter after the Dragon sequence settles. This shows whether the nested steps consume a feature spin or occur inside it.

Do not decrement both counters for one server event. Follow account history and the displayed rule order. If animation skips directly to the result, request the server log rather than reconstructing intermediate states.

The base Dragon Stack ledger has no parent Free Spins counter. Keeping the two layouts different makes accidental mixing harder.

Stack participation and substitutions

A full Dragon stack can affect many of the 40 betlines. For each winning line, record the Dragon coordinates that substitute and any symbol the Wild cannot replace according to the live paytable. Do not assume universal substitution merely because the graphic covers the reel.

The stack event and resulting paylines should be reported separately. Triggering a respin does not guarantee that the initial or following grid pays. Likewise, one stack may support several awards without being several trigger events.

Compare the sum of line credits with account history. Any discrepancy should preserve the game version and full grid for support.

Interruption and recovery

Before refreshing a stalled sequence, capture mode, DS1 or DS5 coordinates, feature counters, stake, balance and round ID. Re-enter through the authenticated lobby and wait for server restoration. Do not place another wager while the prior round is unresolved.

If the stack animation is missing after restoration, compare the settled grid and history. A skipped animation does not prove that the feature or payout was omitted. Conversely, an unsettled round should be raised with precise coordinates and timestamp.

Keep personal account data private. Share evidence only through authenticated support and redact unrelated fields in editorial screenshots.

Version maintenance

Archive the provider page, live game sheet, 40-line diagram, stack worksheets, Scatter trigger and round histories under one version and date. On update, recheck reel height, outer-reel eligibility, Free Spins count, RTP and maximum exposure.

Do not retain a former stake, RTP or trigger detail solely to keep article length. Mark changed fields with a new verification date and explain material differences between builds.

Run exact-duplicate, word-count, internal-link, metadata and responsive checks after every revision. Keep original artwork labelled as editorial illustration rather than game evidence.

Direct answers

Can a partial Dragon group start the feature? No; the published rule requires a stack filling the reel. Can reel five trigger in the base game? The public description does not say so. Can reel five trigger during Free Spins? Yes, as can reel one. Are ten spins awarded by three Bonus Scatters? Yes. Does the provider page state local New Zealand access? No.

These direct answers should match the body and FAQ word for word in meaning. They provide a quick check without erasing the evidence and limitations needed for a complete review.

Final evidence standard

A complete Dragon Shrine case contains the full stopped grid, active reel height, DS stack map, mode indicator, 40-line paytable, Scatter trigger where relevant, all nested states and final account credit. Every artifact should share the same round ID or clearly documented relationship.

With that package, an editor can verify the exact trigger and settlement. Without it, the page should describe the provider-confirmed mechanic but leave version-specific details unavailable rather than borrowing them.

How many betlines are published? Forty.

What triggers the base-game respin? A full Dragon stack on reel one.

What triggers ten Free Spins? Three Bonus Scatters in one spin.

Where can the Scatters land? Reels two, three and four.

Which reels can trigger the Dragon Stack during Free Spins? Reel one or reel five.

Is an RTP published on the public product page? No readable value is shown.

Is New Zealand availability confirmed? No.

Official source

• Quickspin: Dragon Shrine

Bottom line: use reel one as the base-game checkpoint, then expand the check to both outer reels only during the ten-spin bonus.

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.