Crown of Valor — Burning Wilds raise the multiplier inside each siege

Crown of Valor by Quickspin is an extremely volatile 5×5 cluster game. Wins need clusters of at least five matching symbols. Quickspin publishes maximum exposure of approximately 15,000× the bet, but the readable page does not provide a base RTP figure.

The game has two different forms of persistence that are easy to confuse. In the base game, an 18-step Wild Fire meter is stored for the selected bet level while the win multiplier resets after each paid spin. In Free Spins, there is no Wild Fire meter, but the multiplier persists until the bonus ends. A useful review explains those states separately rather than describing everything as “progressive.”

Verified specification and open fields

Quickspin confirms a 5×5 grid, cluster wins of five or more matching symbols, tumble mechanics, Burning Wilds, an 18-win meter, four-Wild Wild Fire event, tiered Free Spins triggers, persistent feature multiplier, one-spin retriggers and an 80× purchase. It labels the game extremely volatile and publishes maximum exposure of around 15,000× bet.

The readable page does not provide base RTP, stake range, cluster paytable, symbol distribution or New Zealand operator availability. These must come from the exact live help or official game sheet. “Around 15,000×” should retain the provider’s approximate wording rather than being converted into a false exact cap.

How cluster wins are formed

A qualifying result contains at least five matching symbols connected according to the game’s cluster rule. The public page establishes the minimum size but does not reproduce the full adjacency definition or award table. Use the live rules to determine whether diagonal contact counts and how larger clusters are paid.

Record the original 25-cell grid and highlight every symbol in the qualifying cluster. If two clusters win on one screen, keep them separate before calculating the total. A visually dense area of one symbol should not be counted unless it meets the active connection rule.

The cluster payment is the opening event in a tumble sequence. Its symbols are removed, but non-winning symbols remain in place until gravity fills the gaps. Preserve the before and after grids so later Burning Wild placement can be distinguished from ordinary replacement symbols.

Tumble sequence anatomy

After a winning cluster is removed, new symbols fall from above. Any newly formed cluster adds to the same paid spin’s result, and tumbling continues until no further win appears. No new wager is charged for the replacement stages inside that sequence.

Number each stage T0, T1, T2 and so on. T0 is the original settled grid; each later state follows a removal and refill. Record cluster coordinates, raw award, Burning Wild arrival, multiplier before settlement and multiplier after any participating Wild increment.

The distinction between paid spin and tumble matters for the Wild Fire meter. Every winning tumble advances the base-game meter, so one paid spin can produce several increments. Counting only the initial grid would understate progress; counting refills without wins would overstate it.

Burning Wild arrival

Every successful cluster win brings one Burning Wild onto the grid. The provider says it is placed in a random column above the remaining symbols. Keep the new Wild’s coordinate separate from Wilds already present.

Arrival does not automatically increase the multiplier. A Burning Wild must participate in a later qualifying cluster to boost the current multiplier by one. A Wild that appears but never joins a win remains visually important without causing the documented increment.

When several cluster wins occur in one tumble state, use the live history to establish how many Burning Wilds enter and in what order. The marketing wording ties one arrival to a successful cluster win, while the replay supplies the precise event sequence for the active build.

Base-game multiplier timeline

The multiplier begins at 1×. Each Burning Wild involved in a cluster win raises it by one, and wins in the current paid spin use the accumulated value. The provider says the multiplier remains at that value until the spin ends, then resets for the next base-game spin.

A correct ledger therefore records the multiplier at every tumble, not merely at the final screen. Suppose a sequence begins at 1×, a later cluster uses one Burning Wild and another stage uses a second. The displayed multiplier can rise through the sequence, while the next paid spin returns to 1×. This is an explanatory timeline, not a predicted result.

Do not multiply a settled history amount twice. If the server entry already reflects the accumulated factor, preserve the raw cluster award only when the history exposes it. Otherwise record the final credit and mark the intermediate calculation unavailable.

The 18-step Wild Fire meter

In base play, every winning tumble increases the meter by one. Eighteen winning tumbles fill it. Once full, Wild Fire places four Burning Wilds in random eligible grid positions, excluding existing Bonus Scatters and Wilds.

The meter advances by winning tumble, not by paid spin, cluster size or currency amount. A small cluster can add one step, while a long chain can add several steps. Record opening meter, number of winning tumble stages and closing meter for each spin.

When the eighteenth step is reached, capture the state before activation, the four added Wild coordinates and the reset. The meter returns to zero after it has been fulfilled and triggered Wild Fire. Do not carry an eighteenth completed state into the next spin as if activation were still pending unless the live history documents a delayed event.

Bet-level storage

Quickspin states that the meter is stored separately for each specific bet option. Changing stake can therefore reveal a different progress state rather than scaling the same meter. Record the exact wager alongside every meter reading.

If a player switches from one bet level and later returns, compare the restored meter with the last state at that same level. Do not combine progress from two wager settings in one 18-step count. The game interface should make the active stake and corresponding meter visible together.

This storage rule should not be treated as a reason to maintain several unfinished meters. Session and loss limits apply across all stakes. A saved gauge is game state, not stored monetary value.

A two-stake meter reconciliation example

Use separate identifiers for the bet options, rather than combining every visible gauge in one running total. In a hypothetical history, option A opens at 12 steps and records two winning base-game tumbles. Its closing count is 14. Switching to option B exposes that option’s own saved count; it does not transfer A’s 14 steps. Returning to A should be compared with A’s previous record, subject to the active game’s documented storage and session conditions.

Recorded option	Opening count	Winning base tumbles	Arithmetic before activation
A, first illustrated round	12	2	14
B, separate illustrated round	3	1	4
A, later illustrated round	14	4	18, then documented Wild Fire activation and reset

These invented counts illustrate record-keeping, not observed gameplay or a recommended stake change. Verify the actual activation sequence and four-Wild placement in completed history. A stored count is not a cash balance, and the arithmetic does not promise that any particular next spin wins or fills the gauge. The separate base-game multiplier still resets between paid spins; the meter worksheet must not silently carry that multiplier with it.

Wild Fire placement audit

On activation, four Burning Wilds are placed in random symbol positions, except positions already occupied by Bonus Scatter or Wild symbols. Save the pre-event and post-event grid to verify both the count and exclusions.

The four additions can influence subsequent clusters, but placement itself does not guarantee a win. Each Wild must join a qualifying cluster to affect the multiplier under the published rule. Record participation separately from presence.

If fewer than four visibly new Wilds appear, check whether the animation overlapped existing Wild positions, whether the replay exposes all placements and whether the event occurred on the correct game version. Use the server record before reporting an error.

Free Spins trigger table

Three Bonus Scatters in one spin award ten Free Spins. Four award 14, and five award 18. Keep the Scatter count and spin allocation in adjacent fields; the numbers are not interchangeable with the 18-step base-game meter.

Capture the trigger grid, any Scatter payment shown by the live paytable and the opening bonus counter. The provider text does not state that the meter carries into Free Spins—in fact, it explicitly says there is no meter during the bonus.

Natural entry with more Scatters changes the starting spin allocation. It does not establish a different RTP or guarantee that the feature will reach the published maximum exposure.

Persistent multiplier during Free Spins

The feature multiplier starts at 1× and persists throughout the bonus. Every winning tumble increases it by one. Any Burning Wild involved in a win adds another increment. Cluster winnings use the accumulated multiplier, which resets only when the Bonus Game ends.

This differs from the base game in two ways. The multiplier survives from one Free Spin to the next, and winning tumbles themselves increase it even when no Burning Wild participates. Use separate ledger columns for the tumble increment and the Wild-participation increment.

For each spin, record opening multiplier, number of winning tumbles, number of participating Burning Wild events, closing multiplier and settled credit. When a spin has no win, the existing multiplier remains available for later spins under the persistence rule; it does not reset merely because one feature spin is blank.

Bonus-symbol retriggers

Every Bonus symbol landing during the Bonus Game adds one Free Spin. This is a per-symbol rule in the provider copy, not a three-symbol threshold. Count each qualifying symbol and compare the remaining-spin counter before and after the consumed spin.

The retrigger does not directly increase the multiplier unless the same spin also contains winning tumbles or participating Burning Wilds. Keep counter change and multiplier change in different columns.

If several Bonus symbols land together, the expected addition follows their count under the published wording. Confirm the active help and server history, especially when the interface combines additions into one animation.

A complete feature ledger

A robust worksheet uses one row per Free Spin and nested entries for each tumble. At spin level, capture opening counter, Bonus symbols, closing counter, opening multiplier and closing multiplier. At tumble level, capture cluster coordinates, raw win if available, new Burning Wild, participating Wilds and settled amount.

This structure makes a disputed feature reproducible. It shows whether a multiplier increase came from a winning tumble, a Burning Wild or both. It also prevents the remaining-spin counter from being confused with the multiplier display.

If the game history provides only final amounts, preserve those and mark the internal split unavailable. Do not manufacture a formula from animations when the server does not expose enough detail.

Bonus Buy at 80× bet

The official page states that paying 80 times the selected bet buys instant entry to the Bonus Game. The purchase is available only from base play and triggers three to five random Bonus Scatters, which correspond to the documented starting allocations.

Before confirming, record the stake and total currency debit. The provider does not publish the probability of receiving three, four or five Scatters from the purchase. A handful of tests cannot establish that distribution.

Purchase availability can differ by market or operator. The international product page does not confirm that the control is enabled in New Zealand. Its absence should be recorded as a deployment fact, not “fixed” by directing readers to another jurisdiction.

An 80× purchase concentrates spending into one action. Compare the full debit with the pre-set session limit. It does not reduce the game’s extremely high volatility or guarantee a positive feature.

Maximum exposure and termination

Quickspin describes maximum exposure as around 15,000× bet. Preserve “around” because the source does not give an exact integer cap or detailed termination clause in readable copy. Do not replace it with a more precise number from an unrelated listing.

If a live round approaches or reaches its configured cap, use the help file and server history to see how remaining tumbles or spins are handled. Do not add hypothetical wins after the server settles the feature.

Maximum exposure is not RTP and does not indicate frequency. It only describes the published upper scale. The readable page supplies no probability of reaching it.

RTP and stake evidence

No base RTP or stake range is visible in the public copy used here. Capture both from the live game help for the precise operator, game ID, version and date. Some deployments may expose alternative RTP configurations, so one operator’s figure should not be presented as universal.

If purchase mode displays a separate RTP, attach it to that mode. Do not infer purchase RTP from price or average observed returns. Likewise, a currency stake range belongs to the operator deployment and may differ across currencies.

Until those primary fields are available, the review remains complete by stating their status clearly rather than inserting placeholders that look like facts.

Mobile presentation and accessibility

The 5×5 grid, base meter, current multiplier and remaining-spin counter must remain readable without overlap on a small screen. During Free Spins, the absence of the base meter should not leave an ambiguous display that appears frozen.

Burning Wild presence and participation need more than sound cues. A stable icon, outline or text event should show when a Wild joins a cluster and raises the multiplier. The 18-step meter should expose a numeric value for users who cannot distinguish colour changes.

The 80× confirmation requires a clear cancel action, full currency cost and keyboard or touch focus. After reconnecting, compare bet-specific meter or feature multiplier with the saved server state before continuing.

Common reading errors

The first error is counting paid spins instead of winning tumbles toward Wild Fire. The second is carrying the base multiplier to the next paid spin. The third is carrying the base meter into Free Spins. The fourth is forgetting that a bonus winning tumble increases the multiplier even without a Burning Wild.

Another mistake is treating every newly arrived Wild as an immediate multiplier increment. Participation in a cluster is the documented condition. Finally, 18 can mean the meter threshold or the largest natural starting-spin award; labels must remain attached.

An editorial numeric scan should flag any sentence where 18, 4, 80× or 15,000× appears without its mechanic.

Who may prefer Crown of Valor

The game may suit readers who like cluster cascades and visible state tracking. Base play offers a saved, bet-specific meter, while Free Spins offers a persistent multiplier that can be followed across the entire feature.

It may not suit anyone who finds extremely volatile outcomes uncomfortable or who is tempted to chase an almost-full meter. Progress on the gauge does not guarantee that the next paid spin will win, and a completed Wild Fire event does not guarantee a profitable result.

Choose a stake and loss limit independently of the meter position. Stored progress is not money and should not be used to justify exceeding a session boundary.

Interrupted-round procedure

If a base tumble chain disconnects, save the stake, opening meter, last visible grid and round ID. On restoration, verify the final meter and multiplier reset before another paid spin. If a bonus disconnects, also verify remaining spins, persistent multiplier and active Burning Wild positions.

Do not recreate the round manually or start a new purchase. Ask authenticated support for the server event log and settlement using the recorded ID. Share screenshots and public game data only; passwords and authentication codes are unnecessary.

If the client display differs from history, report both rather than choosing the larger amount. The server record establishes settlement while the screen capture documents a possible interface defect.

New Zealand availability and source scope

The official Quickspin page confirms the product and its general rules, not its availability at a New Zealand-facing casino. A dated operator lobby, accessible launch and live help panel are needed to verify that claim.

The same separation applies to Bonus Buy. A control documented globally may be disabled for a market. Do not use a foreign lobby or VPN result as proof of local access.

This article therefore explains how to evaluate the title if encountered, while keeping operator, territorial and currency claims outside the provider evidence.

Final publication audit

Verify that the article preserves the two state models: bet-specific meter with per-spin multiplier resets in base play, and no meter with a persistent multiplier in Free Spins. Check every trigger number, retrigger rule, Wild Fire count and purchase cost against the official source.

Remove any unverified RTP, stake range, exact cap, paytable value or New Zealand listing. Confirm that the artwork is labelled editorial. The page is ready only when a reader can reconstruct a tumble chain without confusing meter progress, Wild participation or feature multiplier persistence.

Tumbles and Burning Wilds

Symbols in a winning cluster are removed and replacements fall from above. New cluster wins are added to the current sequence until no new win forms. Every successful cluster brings one Burning Wild into a random column above the remaining symbols.

The multiplier begins at 1×. Each Burning Wild participating in a cluster increases it by one, and all wins in that spin use the accumulated value. In the base game the multiplier resets after the spin.

Wild Fire meter

Every winning base-game tumble advances the meter. Eighteen winning tumbles fill it and trigger Wild Fire, which adds four Burning Wilds to random eligible positions. The meter is saved separately for the selected bet level, resets after triggering and is not active during Free Spins.

Free Spins

Three Scatters award ten spins, four award 14 and five award 18. During the bonus, every winning tumble and every Burning Wild used in a win increases the multiplier. Unlike base play, the multiplier persists through the whole bonus. Each additional Bonus symbol adds one spin.

The page lists an 80×-bet purchase that triggers three to five random Scatters. Availability must be checked in the actual market. The source does not confirm a New Zealand operator offering the game.

Frequently asked questions

What is the grid? Five by five with wins from clusters of five or more.

What fills the Wild Fire meter? Eighteen winning base-game tumbles.

How many Burning Wilds does Wild Fire add? Four.

How many Free Spins can Scatters award? Ten, 14 or 18.

Is New Zealand availability confirmed? No.

Official source

• Quickspin: Crown of Valor

Bottom line: keep tumble count, stored meter, Burning Wild participation and persistent bonus multiplier distinct.

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.