Dragon Chase — Wildfires descend while 15 pearls build four jackpot tiers

Dragon Chase by Quickspin is a 3×5 slot with 20 bet lines. The official page describes two separately configured versions and an operator-specific or local jackpot, so jackpot values cannot be treated as universal game constants.

Wildfires move down one position

The Wildfire feature can trigger randomly in the base game or Free Spins. It adds one to five Wildfire symbols on any reel. Each symbol moves down one position after every spin until it leaves the board.

Up to ten Wildfires can be present at once, and a new Wildfire does not replace an existing one. Quickspin states that these symbols are saved separately for each bet option. Changing stake therefore should not be assumed to preserve the same Wildfire state.

Free Spins

Bonus Scatters on reels two, three and four award ten Free Spins. If Bonus Scatters land on reels two and four during the feature, three spins are added. Further Wildfires can enter, and any that remain after the last Free Spin carry back into the base game.

Dragon Pearl Respin

Three Jackpot Scatters open a 15-position respin board and award three spins. Each Dragon Pearl has a random coin value from 0.5× to 7× the bet level. New pearls lock and reset the remaining counter to three.

The feature ends when the counter reaches zero or all 15 positions are filled. Four to seven collected pearls award MINI, eight to eleven MINOR, twelve to fourteen MAJOR and all fifteen the progressive GRAND. Pearl values pay in addition to the jackpot. The public page says the chance of the GRAND increases with bet size, but it does not publish local jackpot amounts.

The readable source does not provide an RTP figure and does not confirm availability at a New Zealand operator.

Frequently asked questions

Two configurations, two records

The provider page describes Wildfire and Dragon Pearl Respin systems and notes that versions can be configured separately. Do not assume every deployment includes identical jackpot behaviour. Save the version name, help file and operator jackpot terms before merging the systems into one review.

The confirmed base layout is 3×5 with 20 lines. Wildfires, Free Spins and the 15-cell Pearl board have different counters and should be recorded independently.

Wildfire coordinates by bet option

Wildfire can add one to five symbols and allow up to ten on the board. Each moves down exactly one position after a spin until leaving. Assign an ID, reel, row and bet option to every fire. On the next spin, update the row and remove it once it exits.

Quickspin says states are saved separately for each bet option. If the stake changes, close the current map and load the one associated with the new option. Do not claim that switching stakes erases or duplicates a fire without checking the display.

New Wildfires do not replace existing ones. If a coordinate is already occupied, the live help must explain placement. Do not invent collision behaviour.

Free Spins carry-back

Scatters on reels two, three and four award ten spins. During the bonus, Scatters on reels two and four add three. Record the counter before and after the addition and distinguish it from the three-spin Pearl counter.

Wildfires can enter during Free Spins and any remaining after the final feature spin carry into base play. Save their IDs and final coordinates before the transition, then compare the first returning base board.

Pearl board entry

Three Jackpot Scatters open the separate 15-position board with three respins. Every new Pearl locks and resets the counter to three. A respin without a new Pearl reduces the counter; the feature ends at zero or a full board.

Create a fixed 15-cell map. Record every Pearl’s coordinate and coin value from 0.5× to 7× the bet level. Do not merge equal values into one entry because the collected count determines the jackpot tier.

Jackpot tiers

Four to seven Pearls correspond to MINI, eight to eleven to MINOR, twelve to fourteen to MAJOR, and all fifteen to the progressive GRAND. The coin values pay in addition to the tier award under the provider description.

Count locked Pearls before naming the tier. Three or fewer do not fit a published jackpot band in the accessible copy, though their coin values may still be relevant under the live rules.

The actual jackpot amount is operator-specific or local. Do not copy a number from another casino, currency or screenshot. Save the meter displayed for the active account and time.

Worked Pearl example

Suppose the board starts with three triggering Pearls and three respins. A new Pearl arrives on the first respin, locks and restores the counter to three. Two empty respins reduce it to one; another new Pearl restores it again. When three consecutive respins add none, the feature ends.

If the final count is five, the stated tier range is MINI, plus the sum of recorded coin values. The example explains the reset logic, not a likely outcome or real jackpot amount.

RTP, bet and jackpot checks

The readable page does not publish RTP. The live help should show version, RTP, stake range, payline values, bet-option mapping, Wildfire rules and Pearl settlement. The operator terms should identify jackpot funding, currency, reset value and eligibility.

Quickspin says the chance of GRAND increases with bet size, but the accessible page does not publish probabilities. Do not transform that statement into an odds table.

New Zealand access

The global provider page does not confirm a New Zealand operator or local jackpot. Verify territorial terms, signed-in catalogue, game version and jackpot conditions. A provider demo does not establish account eligibility.

Do not bypass a regional restriction. Cashier and verification rules require operator evidence.

Mobile and accessibility

Wildfire IDs and downward movement must remain readable on the 3×5 reels. The Pearl board should expose all 15 cells, coin values, collected count and respin counter without horizontal overflow.

Use icons or text in addition to colour for locked Pearls. After interruption, compare Wildfire maps by bet option, Free Spins counter, Pearl board, jackpot meter, round ID and balance.

Dispute package

For Wildfire issues, save bet option, fire IDs, coordinates before and after each spin and carry-back state. For Pearl issues, save every cell, coin value, counter reset and final tier. Add provider, version, stake, currency, time, balances and round ID.

Contact authenticated support. Never disclose passwords, one-time codes, private keys or seed phrases. Request the server event log and timestamped jackpot amount.

Responsible-play interpretation

Stored Wildfires and a growing Pearl count can look like accumulated cash, but both remain game states until settlement. A higher stake may change stated GRAND chance, yet it also increases money at risk. Do not raise a bet to chase the progressive tier.

Set fixed session and loss limits. Keep jackpot meters out of budget decisions and use breaks or exclusion tools if collection progress encourages continued play.

Common errors

The three-spin Pearl counter is not the same as ten Free Spins. Wildfires move down one row and are stored by bet option; they are not locked Pearls. Jackpot tier depends on Pearl count, while the coin-value sum is a separate payment component.

The progressive GRAND requires all 15 positions under the published rule. An operator meter is not a universal Quickspin amount.

Final checklist

• Confirm 3×5 and 20 lines.
• Assign each Wildfire an ID and bet option.
• Move fires down one position per spin and cap simultaneous state at ten.
• Use ten Free Spins and the reel-two/reel-four three-spin addition.
• Carry remaining feature Wildfires back to base play.
• Map all 15 Pearl positions and reset the respin counter on every new Pearl.
• Apply jackpot bands by collected count.
• Keep coin values and jackpot tier separate.
• Verify RTP, version, local jackpot and New Zealand access independently.

Editorial conclusion

Dragon Chase requires two ledgers because the systems answer different questions. The Wildfire record tracks position and bet option; the Pearl record tracks locked count, coin value and respin counter.

The review is complete only when it refuses to turn a local progressive meter or unverified configuration into a universal claim.

Wildfire movement table

For each fire, store ID, bet option, entry spin, reel, initial row, current row and exit spin. The one-position downward move can then be verified after every board evaluation. If several Wildfires occupy the same reel, keep separate IDs.

Changing stake should load the map associated with the selected bet option. Screenshot both maps before claiming that a state disappeared. The provider wording supports separate storage, not a transfer from one option to another.

Free Spins counter arithmetic

Begin with ten. Subtract one after each completed feature spin. When the qualifying Scatters appear on reels two and four, add three. Maintain this counter separately from Wildfire quantity and the Pearl respin meter.

If multiple Scatter pairs appear, use the deployed help to determine how many additions apply. The public overview establishes the reel condition but does not answer every duplicated-symbol edge case.

Pearl value calculation

Every locked Pearl displays a coin value from 0.5× to 7× the bet level. Record the value at landing and sum all collected Pearls once. Keep half-unit precision. Then add the jackpot tier amount under the operator rules.

Do not multiply the tier award by the Pearl count or assume the top 7× value on every cell. Coin values and progressive meter are separate settlement components.

Counter-reset example

A board with two respins remaining lands a new Pearl. The counter returns to three, not four or five. A subsequent empty respin lowers it to two. This reset pattern continues until zero or all cells fill.

The example is deterministic bookkeeping and says nothing about the chance of a Pearl landing.

Progressive meter evidence

Save the visible MINI, MINOR, MAJOR and GRAND amounts immediately before entry and at settlement. Note currency and whether the display labels the amount fixed, local or progressive. The product page says jackpot configuration can be operator-specific.

If the meter changes during the feature, the operator terms should state whether the entry, trigger or settlement value applies. Do not decide from animation alone.

Game-version separation

The source describes separately configured versions. Preserve the exact version title and lobby identifier. A Wildfire-focused deployment may not share every jackpot detail with another. Merge facts only after the game sheet proves they coexist.

This is especially important for RTP. A percentage from one configuration cannot be attached to all Dragon Chase variants.

Content-design guidance

Use a 3×5 movement diagram for Wildfires and a separate 15-cell board for Pearls. Never overlay them as though the Pearl feature occurs on the reel grid. Two counters should use distinct labels and icons.

On mobile, the jackpot table can stack by count range. Long amounts must wrap without losing currency labels.

Direct reader answers

Can a Wildfire replace an existing one? Quickspin says new ones do not replace existing fires. Does switching bet preserve one common map? The states are saved separately by bet option. Do remaining bonus fires vanish? The provider says they return to base play.

Does fifteen Pearls award GRAND? Yes, under the published tier structure. Is the displayed amount universal? No; local or operator terms determine it.

Final quality gate

The article passes when each fire can be moved row by row and each Pearl can be reconciled by cell, value and counter reset. It fails when it mixes the three counters or presents a foreign jackpot as a New Zealand offer.

Date every source and keep missing RTP or access information explicitly unavailable.

Operator questions before funding

Ask which Dragon Chase configuration is deployed, whether jackpot values are local or networked, which bet levels map to saved Wildfire states and what happens to a pending progressive feature after disconnection. Request the current game sheet rather than a generic lobby description.

The cashier currency and jackpot currency also need labels. A GRAND shown in another currency should not be converted into an NZD promise using an undated rate.

Editorial comparison note

When comparing Dragon Chase with another collect-and-respin title, use the 15-cell counter reset and tier bands. When comparing it with a persistent-Wild game, use the one-row movement and bet-specific storage. Avoid ranking either mechanic as more profitable without matching RTP and probability evidence.

Publication layout

Place the Wildfire timeline and Pearl board in separate panels. Include the four count ranges in a table and label the progressive amount as operator-specific. On mobile, each panel should stack and preserve the counter labels.

The final page should make it impossible to confuse the three-spin Pearl counter with the three-spin Free Spins addition. Clear labels are part of factual accuracy.

Closing reader guidance

Track the fire map when selecting a bet and the Pearl board when the jackpot feature starts. Do not change stake or chase a tier because a prior state looked close. Verify the local rules, establish a limit and treat every published feature as an outcome mechanism rather than stored value.

Final source review

Open the provider page and verify one-to-five new Wildfires, ten simultaneous maximum, one-position movement, separate bet-option storage, ten Free Spins and the reel-two/reel-four addition. Then verify the 15-cell board, 0.5×–7× coin range, reset-to-three rule and four jackpot bands.

Any jackpot amount, RTP or local access statement must come from the deployed operator sources. Keep the review date visible because progressive terms and catalogue availability can change.

Concise final answer

Dragon Chase is not one collection feature. It is a moving-Wild state attached to reel play and a separate hold-and-respin board attached to jackpots. Readers who keep those ledgers separate can understand the game; readers who merge them are likely to misread counters and payments.

For the final page, include a visible “version-specific” label beside every jackpot statement and never show a decorative meter as a current amount. Test the two ledgers on mobile and preserve the official source link. This ensures the article remains accurate even when a local progressive changes after publication.

Record the final review timestamp and currency with the saved meter.

What is the layout? Three rows, five reels and 20 lines.

How many Wildfires can be present? Up to ten.

How many Free Spins are awarded? Ten.

What starts the Pearl feature? Three Jackpot Scatters.

How many pearls award the GRAND? All 15.

Is New Zealand availability confirmed? No.

Official source

• Quickspin: Dragon Chase

Bottom line: keep bet-specific Wildfires, Free Spins and the 15-position Pearl board in separate records.

For future revisions, retain the dated trigger grid and feature-state record beside the version number. That evidence shows whether a changed description reflects a genuine game update, an operator-specific configuration or an unsupported third-party claim.

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.