Dragon's Domain — Dragonfire refills charged Wild multipliers

Dragon’s Domain by Hacksaw Gaming uses six reels, five rows, all-scatter wins and cascades. The provider publishes a maximum win cap of 10,000× bet.

Charred Land

Charred Land symbols are substituting Wild multipliers that arrive with three charges and initial values of 2×, 3×, 4×, 5× or 10×. Participation in one or more wins removes a charge before the next cascade. Every cascade increases every Charred Land multiplier on the grid by one. Multiple participating values add before application.

Dragonfire

After the board settles with no more wins, Dragon symbols breathe fire in a cross from their position. Paying symbols hit by the fire disappear. A hit on Charred Land refills its charges. A Gold Dragon carries 2×, 3×, 4×, 5× or 10× and multiplies the Charred Land value it hits.

Dragon’s Lair and Hatchery

Three FS scatters start Dragon’s Lair with ten spins. Charged Charred Land persists between spins. Two extra scatters add two spins and three add four.

Four scatters start The Hatchery with ten spins. Only dead symbols, Dragons and Eggs appear. Dragonfire collects Eggs; Gold Dragonfire multiplies their value. Green Eggs publish values from 1 to 10, red from 20 to 40 and golden from 50 to 200. Each collected value is multiplied by the current bet.

Evidence limits

The source confirms mechanics and the 10,000× cap but not readable RTP, stakes or New Zealand availability.

Charred Land has two independent counters

Every Charred Land position needs a charge count and multiplier value. It begins with three charges and a value of 2×, 3×, 4×, 5× or 10×. Do not merge these fields into one number.

When Charred Land participates in one or more wins, one charge is removed before the next cascade. Several wins on the same settled grid do not automatically consume several charges; record the live transition.

Every cascade increases every Charred Land multiplier on the grid by one, including positions that did not participate in the prior win under the published wording.

Creating the position ledger

Assign each Charred Land coordinate a stable ID. Record starting value, three charges, every participation event, cascade increment, Dragonfire refill and Gold Dragon multiplication.

Copy the ledger between cascade states. When charges reach zero, use the deployed help to record whether the position remains, clears or changes state.

The visual flame effect is not evidence of value. Save the persistent labels and round history.

Add participating values

When several Charred Land positions participate in one all-scatter win, add their values before application. A 4× and 7× pair gives an 11× feature multiplier, not 28×.

Only positions forming part of the evaluated scatter result belong in that sum. Visible multipliers outside the win are excluded while still receiving any global cascade increment.

Keep base award, participating IDs, additive sum and final credit in separate columns.

All-scatter and cascade audit

The game uses six reels, five rows and all-scatter wins. Obtain the exact minimum count, symbol values and adjacency rules from the deployed paytable.

For every win, mark all participating symbols, remove them, decrement participating Charred Land charges and increment every Charred Land value when the cascade occurs. Record falling replacements.

The cascade chain ends when no new win appears. Dragonfire then resolves on the settled board.

Dragonfire cross mask

After wins finish, a Dragon breathes in a cross from its position. Draw horizontal and vertical rays through the grid and record every hit coordinate.

Paying symbols hit by fire disappear. Charred Land is not treated as an ordinary paying symbol; its charges refill under the published rule.

If several Dragons act, preserve their event order and updated board between fires.

Refilling charges

A Dragonfire hit on Charred Land refills its charges. Record the charge count before impact and restored state after the event. The accessible description establishes refill but not partial arithmetic; use the live display.

Do not change the multiplier value merely because charges refill. Charge and value ledgers are separate.

A later cascade can still increase the refilled position’s multiplier by one.

Gold Dragon multiplication

A Gold Dragon carries 2×, 3×, 4×, 5× or 10×. When its fire hits Charred Land, multiply that position’s value by the displayed Dragon factor.

Record pre-value, Gold factor and post-value. Do not add the Dragon factor. A 7× land hit by 3× becomes 21× under the multiplication rule.

If the same fire also refills charges, record both transitions independently and in the order shown by the game.

Worked cascade and fire example

Suppose C1 begins at 3× with three charges and C2 at 5× with three. Both participate in a win, so their values add for settlement and each loses one charge. A cascade increases both values to 4× and 6×.

After the chain ends, ordinary Dragonfire crosses C1 and refills its charges. A Gold Dragon with 2× later crosses C2, multiplying its value according to the event.

Illustrative values explain state transitions and are not promised outcomes.

Dragon’s Lair entry

Three FS scatters trigger ten Free Spins. Save the trigger grid, initial counter and every charged Charred Land coordinate at feature start.

Charged Charred Land persists between primary spins. Copy both charge and value states forward under the live rules.

Two extra scatters add two spins and three add four. Record counter transitions separately from cascades and fire events.

Persistent bonus ledger

Use one row per primary Free Spin with starting land map, cascade states, charge consumption, value increments, Dragonfire changes, ending map and settlement.

Do not decrement the main Free Spins counter for nested cascades. Preserve only documented persistent positions between spins.

At bonus end, clear the map and reconcile the feature total with account history.

Hatchery entry

Four scatters trigger The Hatchery with ten spins. This mode contains dead symbols, Dragons and Eggs. Save the trigger and starting counter.

Dragonfire collects Eggs, while Gold Dragonfire multiplies their value. Record every Egg coordinate, colour and displayed value before fire.

Keep this collection ledger separate from Dragon’s Lair Charred Land states.

Egg value bands

Green Eggs publish values from 1 to 10, red from 20 to 40 and golden from 50 to 200. Verify the exact displayed number; colour supplies a range, not a fixed amount.

When ordinary Dragonfire collects an Egg, mark it consumed and add its value under the live rules. When Gold Dragonfire hits, record the multiplication factor and resulting value.

Each collected value is multiplied by the current bet at settlement according to the provider description.

Hatchery settlement

Maintain chronological rows for Egg reveal, fire source, collection or multiplication and final value. Prevent a consumed Egg from being credited twice.

At feature end, sum the documented collected values and apply the complete bet definition. Compare with history and any 10,000× cap.

The cap is a ceiling, not a forecast or typical return.

Comparing the two bonuses

Dragon’s Lair uses persistent charged Wild multipliers across ten spins. Hatchery uses a restricted board and coloured Egg collection. Their triggers differ by three versus four scatters.

Do not carry Charred Land into Hatchery or Egg bands into Dragon’s Lair. A comparison table should show trigger, persistent object, duration, fire effect and settlement.

Both require the exact live counter and paytable.

RTP, stakes and configuration

The official page does not expose readable RTP, stake range, default denomination or volatility. Collect them from the deployed game with title, operator, currency, version and date.

If multiple RTP versions exist, publish only the tested one. Do not merge a cap or Egg table with numerical fields from another deployment.

Confirm the game’s definition of bet before applying collected values.

New Zealand availability

The global provider page does not prove real-money access in New Zealand. Verify country terms, registration eligibility, authenticated catalogue and successful launch.

NZD support, payments, verification and withdrawals are operator facts. Source them separately and date the check.

A demo is insufficient. Do not advise bypassing location controls.

Mobile and accessibility checks

On mobile, all six reels, five rows, charge counters, multiplier values, cross masks, Egg values and feature counter must remain visible. Test portrait and landscape modes.

Charge and multiplier state need separate accessible labels. Egg colour needs numeric text. Reduced-motion mode should preserve cascade and fire order.

After interruption, compare mode, ledgers, counter, balance and round identifier with server history.

Support-ready evidence

For Charred Land, provide position ID, charges and values through every win, cascade and fire. For Gold Dragon, include factor and pre/post value.

For Hatchery, provide Egg colour, number, fire source and collection history. Add operator, version, stake, currency and round identifier.

Never share passwords, one-time codes, private keys or seed phrases. Ask authenticated support for server events.

Session controls

Persistent charged positions can feel like stored value, but they exist only inside the active feature. A depleted board or uncollected Egg does not make another trigger due.

Set stake, spending and time limits before play. Do not increase stakes to chase a recharge, Gold Dragon or 10,000× cap.

Mechanical knowledge supports accounting, not prediction. Use responsible-play controls and stop at the chosen boundary.

Publication checklist

• Track charges and multiplier values independently.
• Remove one charge after qualifying participation under the live transition.
• Increase every land value by one per cascade.
• Add participating values rather than multiply them.
• Draw the Dragonfire cross before changing cells.
• Refill charges on ordinary fire hits.
• Multiply land values by Gold Dragon factors.
• Keep Dragon’s Lair and Hatchery ledgers separate.
• Apply Egg values to the documented bet.
• Verify RTP, stakes and New Zealand access from live evidence.

Editorial assessment

Dragon’s Domain is a two-state audit: Charred Land has charge and value, and fire can affect either or both after cascades stop. Dragon’s Lair preserves that state across spins, while Hatchery replaces it with Egg collection.

A rigorous review records every transition and reports 10,000× only as a cap. Missing RTP, stakes and local availability remain unclaimed until the deployed version supplies primary evidence.

Multiple Charred Land positions on one scatter result

An all-scatter win can include several charged positions with different values and remaining lives. Build the participating set from the evaluated symbols, add those multiplier values once, and then apply the combined value in the paytable’s order. Update charges only after the award has been captured.

Non-participating Charred Land still receives the published +1 value increase when the win causes a cascade. This creates different histories: one position may lose a charge and grow, while another only grows. A single “board multiplier” field would hide that difference.

Keep coordinates and state transitions in a table so later Dragonfire affects the correct position.

Overlapping Dragonfire crosses

When several Dragons breathe fire, their horizontal and vertical masks can overlap. Record the first cross, apply its removals or refills, then use the updated grid for the next event if the live game resolves sequentially.

A Charred Land cell crossed twice may show two animations, but charge or value changes must follow the server event order. Do not apply a refill or Gold multiplication twice merely because two rays visually overlap unless both events are recorded.

Likewise, a paying symbol removed by the first fire cannot be removed again for a second independent credit.

Charge exhaustion review

For every charged position, store the initial three, each participation decrement and every refill. When the counter reaches zero, capture the exact state shown by the deployed game. The public overview does not fully describe the exhausted visual or its later eligibility.

Do not assume that zero charge deletes the multiplier immediately, nor that it continues substituting indefinitely. The live paytable and final grid supply that rule.

This explicit boundary prevents the article from inventing behaviour in one of the feature’s most important edge cases.

Worked Hatchery example

Suppose the board contains green 6, red 25 and golden 80 Eggs. An ordinary Dragonfire crosses the green Egg and collects its displayed value. A Gold Dragon carrying 3× crosses the red Egg, so the event ledger records its provider-defined multiplication. The golden Egg remains uncollected unless another cross reaches it.

At settlement, use the final recorded values and complete bet definition. Do not add the untouched golden value simply because it was visible.

The illustrative numbers lie within published colour bands but do not claim an occurrence rate or prize.

Version comparison protocol

Attach every review to operator, build, currency and date. Compare grid size, starting charges, starting value set, cascade growth, fire refill, Gold multiplication, scatter triggers and Egg bands individually.

Archive one complete cascade-and-fire chain, one Giant persistent Dragon’s Lair state and one Hatchery collection with the matching help. These reference rounds distinguish a genuine update from an animation redesign.

If primary sources conflict, retain both dated states. Do not merge RTP from one build with charge behaviour, stake limits or Egg rules from another.

Practical reader decision points

Before play, confirm live RTP, complete stake, payout cap, country eligibility and responsible-play controls. During an ordinary chain, ask which Charred Land positions participated, which only gained value, and which fire crosses changed charges or multipliers.

During Dragon’s Lair, add the persistent state at each primary spin. During Hatchery, ask which Eggs were actually crossed and collected. These questions reconstruct settlement without suggesting a Dragon or Gold multiplier is due.

After the feature, clear all position maps and apply the pre-set session boundary. Charges, Egg values and fire targets are temporary state, not account value carried into later rounds.

Arithmetic review template

For a disputed round, write the calculation in temporal order: base all-scatter award; sum of participating Charred Land multipliers; charge decrements; cascade-wide +1 changes; cross-shaped removals; charge refills; Gold Dragon multiplications; final settlement. Do not reorder events to maximise the outcome.

For Hatchery, replace the Charred ledger with Egg values, fire sources and collection status, then apply the documented bet once. Compare the expression with server history and any cap application.

RTP remains outside this reconstruction because it describes long-run theoretical return rather than one cascade or collection result.

Final verification note

Before publication, compare every stated range and trigger with the current official help rather than relying only on an older promotional page. Preserve screenshots of the three-charge starting state, one Gold Dragon factor and each Egg colour band.

If any field cannot be reproduced in the deployed build, label it as source-specific and retain the date. This keeps a mechanical change from becoming an apparent contradiction and prevents an unavailable configuration from being presented to New Zealand readers as current fact.

Frequently asked questions

How many charges does Charred Land start with? Three.

What increases its multiplier? Every symbol cascade.

What restores charges? A Dragonfire hit.

What starts Dragon’s Lair? Three FS scatters.

What starts The Hatchery? Four FS scatters.

What maximum cap is published? 10,000× bet.

Is New Zealand availability confirmed? No.

Official source

• Hacksaw Gaming: Dragon’s Domain

Bottom line: record charges and multiplier value separately after every win, cascade and Dragonfire event.

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 Hacksaw Gaming, 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.