Mighty Arthur — two full-height Wilds do different jobs

Mighty Arthur by Quickspin uses two 3×1 special Wild symbols. They share the same full-height form, but their landing positions and effects differ.

Arthur and Merlin

The Arthur Wild appears only on reel three in the base game and Free Spins. When full, it expands onto adjacent reels and turns those positions Wild.

The Merlin Wild may appear on reels one through five. It creates between two and six additional Wild symbols on valid random positions. Do not treat those added Wilds as another Merlin stack.

Mystery Nudge and Free Spins

In the base game, a landed Arthur or Merlin Wild has a chance to nudge into a full stack. During Free Spins, either one always nudges into its complete 3×1 form.

The bonus requires three Bonus symbols placed on reels one, three and five and awards ten Free Spins. “Anywhere” applies within those specified reels, not across any three columns.

Evidence limits

The short HTML overview omits numerical stakes and RTP, while its linked supplier sheet provides reference fields discussed below. A complete payline layout and an active New Zealand deployment remain unverified.

Frequently asked questions

Verified feature map

Quickspin describes two special Wild symbols, each three positions high and one reel wide. Arthur appears only on reel three in the base game and Free Spins. Once complete, he expands into adjacent reels and makes those positions Wild. Merlin may appear on any of the five reels and, when complete, places between two and six additional Wilds on valid random positions.

In the base game, either special symbol may use Mystery Nudge to become a full stack. During Free Spins, a landed Arthur or Merlin always nudges into its complete 3×1 form. Three Bonus symbols positioned on reels one, three and five award ten Free Spins.

The linked supplier sheet supplies reference RTP and euro stakes, not proof of the active operator configuration. A full payline map, contractual maximum, nudge probability and New Zealand availability still require deployed help or operator evidence.

Arthur and Merlin identity test

Begin every event row with the character name. Although both stacks have the same 3×1 dimensions, their placement and output differ. An Arthur row needs reel three, partial or complete state, nudge evidence and adjacent expansion. A Merlin row needs its landing reel, completion state and two-to-six generated Wild coordinates.

Do not identify a character only from colour or animation. Use the game’s symbol label or history. A full-height graphic on reel three could still require confirmation before applying Arthur’s expansion rule, while Merlin can also land on reel three under the published range of reels one through five.

Generated Wilds from Merlin receive ordinary coordinate IDs such as MW1–MW6. They are not new Merlin stacks, do not automatically nudge and should not generate another two-to-six placement event unless the live rules explicitly state otherwise.

Arthur’s reel-three restriction

Arthur’s source position is fixed to reel three. Capture all three vertical cells and the game mode. If an apparent Arthur appears on another reel, preserve the screenshot and check whether it is an expanded position, a different Wild or a visual effect rather than a direct landing.

When the full stack activates, record the adjacent reels and cells converted to Wild. The public description confirms adjacent expansion but the deployed help should define exact coverage, boundary behaviour and substitution exclusions. Do not label the entire board Wild without coordinate evidence.

Expansion is one feature event inside the round. Record the initial reel-three stack, resulting Wild mask, paylines affected and settled win. The animation alone cannot show the pay calculation.

Merlin’s random placement

Merlin can land across reels one through five. Once complete, he places between two and six additional Wild symbols on valid random positions. Record the number actually placed and every destination coordinate. Preserve occupied or excluded cells so “valid position” can be checked against the live help.

Two is the lower published output and six is the upper output. Neither is an average or guaranteed count. Do not state that six Wilds appear whenever Merlin becomes full, and do not add the Merlin stack’s three cells to report “nine generated Wilds”.

If an added Wild lands where another Wild already appears, the server log must show whether the placement was skipped, replaced or counted. Avoid inferring duplicate treatment from layered animation.

Mystery Nudge in the base game

A landed partial Arthur or Merlin has a chance to nudge into the complete 3×1 symbol. Save the initial visible portion, starting reel positions, nudge message and final full stack. This demonstrates that completion came from Mystery Nudge rather than a naturally landed full symbol.

The phrase “has a chance” means the base-game nudge is not automatic. A partial symbol that does not complete should not receive Arthur expansion or Merlin random-Wild effects. Do not publish a frequency without an official probability table.

Where only part of a stack is visible at the top or bottom, record direction and distance moved. The deployed rules should explain eligible partial states and whether all can nudge. One observed round is not enough to generalise.

Guaranteed completion during Free Spins

During Free Spins, a landed Arthur or Merlin always nudges into a complete 3×1 stack according to the provider description. “Always” concerns completion after the special symbol lands; it does not say that either character appears on every Free Spin.

Record the landed partial state and completed stack, then apply the correct character effect. Keep the ten-spin counter separate from nudge animation. A nudge is part of the current feature spin and should not add another spin unless the rules say so.

Do not turn guaranteed nudge completion into a claim of a certain payout. The resulting Wilds must still form valid wins under the deployed paytable.

Bonus trigger across reels 1, 3 and 5

The Free Spins trigger requires Bonus symbols on reels one, three and five. “Anywhere” refers to row position within those specified reels. Create a three-column trigger table and record one qualifying Bonus coordinate in each required column.

Three Bonus symbols on reels one, two and three do not match the published 1‑3‑5 pattern. Likewise, several Bonus symbols on one required reel do not replace a missing symbol on another. Use the final stopped grid, not anticipation animation.

Once verified, record the ten-spin award message and starting counter. Any retrigger rule must come from the deployed help because the public summary does not establish one.

Worked Arthur round

Suppose a partial Arthur appears on reel three in the base game and Mystery Nudge completes the 3×1 stack. The ledger records the partial cells, nudge movement, full reel-three state and adjacent positions turned Wild. The paytable then determines which of the documented paylines win.

If Mystery Nudge does not occur, the partial symbol remains subject to the normal rules and Arthur’s full-stack expansion is not applied. This example describes the decision path, not the probability or a typical payout.

During Free Spins, the same landed partial Arthur would complete under the published automatic-nudge rule. That difference should be visible in the mode column.

Worked Merlin round

Suppose Merlin lands on reel five, nudges to full height and places four Wilds. Record the stack independently from MW1 through MW4 and map each destination. Evaluate only the final grid, using the live paytable and valid line paths.

Do not rewrite the result as six added Wilds because six is the ceiling. Do not assign Arthur’s adjacent expansion to the Merlin stack. If a generated Wild participates in several lines, retain one coordinate linked to each relevant award.

The hypothetical demonstrates bookkeeping and does not claim a valid stake, RTP, local availability or expected frequency.

RTP, paytable and limits

Open the deployed help and collect layout, paylines or ways, symbol values, Wild substitutions, Arthur coverage, Merlin valid positions, nudge eligibility, Bonus trigger, starting Free Spins, stake range, RTP configuration and maximum exposure. Record version, operator and date.

RTP cannot be calculated from the two-to-six Wild interval or ten-spin award. A full stack also does not disclose the maximum payout without line values and feature caps. Leave unsupported fields unavailable.

If several RTP versions exist, report only the value shown for the tested deployment. Do not combine a return figure from one casino with feature rules or limits from another.

New Zealand availability

Quickspin’s global page confirms the feature description, not real-money access in New Zealand. Local proof requires operator country terms, eligible account access, a signed-in lobby listing and matching help. A demo or provider portfolio page is insufficient.

Currency, payments, identity checks and withdrawals are operator matters. They cannot be inferred from the game page. Date all local evidence because availability may change.

Do not recommend bypassing location or account restrictions. If access remains unconfirmed, state that and retain the mechanics guide.

Mobile and accessibility checks

At phone width, a full 3×1 stack must remain visible with reel number and character name. Arthur’s adjacent expansion and Merlin’s random placements should use persistent markers after animation. Portrait cropping must not hide part of a stack or the 1‑3‑5 trigger.

Keyboard focus should reach paytable, help and history. Reduced-motion mode must preserve the completed grid. Colour alone should not distinguish Arthur, Merlin and generated Wilds; use labels or icons.

After interruption, compare mode, character, partial or full state, generated coordinates, Free Spins counter, balance and round ID before another action.

Support evidence

Save provider, title, version, operator, date, stake, currency, balances and round ID. For Arthur include source stack, nudge state and expanded mask. For Merlin include source reel, nudge state, generated count and all destinations. Add the trigger grid for a Free Spins question.

Ask authenticated support for the server event record and configuration. Identify one disputed coordinate or transition. Never share passwords, authentication codes, private keys or seed phrases, and redact unrelated personal information.

Suitability and session control

Mighty Arthur may interest readers who like visibly different character mechanics and can follow a coordinate map. It may be unsuitable for anyone who treats a partial stack as evidence that completion is due or who raises stake to chase Merlin’s six-Wild ceiling.

Set stake, money and time limits before play. The player cannot select the character, nudge or random destinations under the published rules. A previous failed nudge does not make the next one more likely.

The end of a feature or ten-spin bonus is a natural point to stop and review. Do not treat generated Wilds as stored progress for later rounds.

Publication checklist

• Identify Arthur or Merlin before applying an effect.
• Keep both stacks at 3×1 in diagrams.
• Restrict direct Arthur landings to reel three.
• Allow direct Merlin across reels one through five.
• Record two-to-six generated Wilds as separate positions.
• Distinguish base-game chance from automatic Free Spins nudge.
• Verify Bonus symbols specifically on reels one, three and five.
• Record ten starting Free Spins without inventing a retrigger.
• Source RTP, stakes, paytable and maximum from live help.
• Confirm New Zealand access through operator evidence.

Editorial conclusion

Mighty Arthur is accurately explained only when symbol identity comes before size. Arthur’s full stack expands from reel three into adjacent positions; Merlin’s full stack places a separate random set of Wilds. Mystery Nudge changes completion probability by mode but does not merge the two effects.

The public page supports these mechanics and the 1‑3‑5 ten-spin trigger. It does not support invented RTP, limits, maximum exposure or local access. A character-specific ledger keeps the final article detailed without crossing that evidence boundary.

Character-state comparison table

For each inspected round, use six columns: mode, character, source reel, landed height, nudge result and final effect. An Arthur record ends with the adjacent Wild mask; a Merlin record ends with the count and coordinates of generated Wilds. A non-completing base-game partial ends with no full-stack effect.

This table exposes errors quickly. An Arthur row on reel five is probably an expanded position or misidentified symbol; a Merlin row listing “adjacent expansion” has borrowed the wrong mechanic. During Free Spins, the nudge result should show completion after a qualifying character landing, while the base-game row remains probabilistic.

Add a source column linking the headline rule to Quickspin and the detailed configuration to the deployed help. If the live version behaves differently, do not force it into the public summary. Preserve the version evidence and revise the claim narrowly.

Settlement reconciliation

After the character effect finishes, save the final board before line awards disappear. Mark every Wild coordinate and connect it to valid paylines or ways from the tested paytable. Keep one coordinate even when it contributes to several wins, then list the separate credited combinations in an award ledger.

For Arthur, distinguish the original three-cell stack from positions converted by expansion. For Merlin, distinguish the full source stack from MW-labelled added Wilds. This allows support to determine whether a disputed cell came from landing, nudge, expansion or random placement.

Compare the sum of documented awards with account history. If it differs, check substitution exceptions and settlement order before alleging an error. The visual number of Wilds alone cannot establish the correct total.

Maintenance record

Archive the provider description, in-game rules, paytable, screenshots and round histories under the same version and date. Recheck character placement, nudge wording, 1‑3‑5 trigger, RTP and maximum exposure after any update. Do not keep old numeric configuration solely to preserve article length.

Run word-count, exact-duplicate, internal-link and mobile checks after revisions. Ensure FAQ answers repeat only facts supported in the body and that editorial artwork remains labelled as illustration rather than game evidence.

The final page should let a reader classify an observed event without guessing: name the character, confirm full height, identify how completion occurred, apply only that character’s effect and verify settlement in history. That is the practical value of the review.

Final direct answers

Does a partial Arthur always expand in the base game? No; the published base rule gives a chance of Mystery Nudge completion. Does the same partial complete during Free Spins after landing? The provider says Arthur or Merlin always nudges fully in that mode. Can Arthur originate outside reel three? Not under the published direct-landing rule. Are Merlin’s added Wilds further Merlin stacks? No; record them as separate generated Wild positions.

Can three Bonus symbols on arbitrary reels award the ten spins? The stated pattern uses reels one, three and five. Does any of this prove that the game is available in New Zealand? No. Those concise distinctions should remain visible even if the interface uses similar full-height artwork for both characters.

How large are Arthur and Merlin Wilds? Three symbols high and one reel wide.

Where can Arthur appear? Only reel three.

Where can Merlin appear? Reels one through five.

How many extra Wilds can Merlin place? Between two and six.

What triggers ten Free Spins? Bonus symbols on reels one, three and five.

Is New Zealand availability confirmed? No.

Supplier reference and its limits

The linked official Mighty Arthur sheet identifies mightyarthur, a 96.94% total return and supplier volatility 3.90 on a one-to-five scale. Its euro reference is a 0.20 minimum, 100 maximum and 1 default stake. These are supplier fields, not confirmation of today’s signed-in operator build or a recommendation to use the default.

The return panel prints Base Game 33.10, Feature Game 34.11% and Free Game 29.73%. The base row lacks the percentage sign visible on the other rows; treating it as the same unit makes the three printed components sum to 96.94. Preserve that typography limitation rather than silently presenting a separately verified base percentage. These are model contributions, not three conditional session returns.

The sheet’s 621-times-bet result is explicitly labelled as observed in one billion spins. That finite sample is not a contractual payout ceiling. Its introductory description also says Arthur covers three reels; the coordinate example below uses that reference coverage without inventing a payline count or local casino access.

Coverage arithmetic: source cells are not generated cells

Imagine two separate stopped results, each with no other Wilds, and label rows top, middle and bottom. This is a bookkeeping example, not a claim that the two characters appeared together or that these results have equal probability. For Arthur, start with his complete three-cell stack on reel three. The supplier’s three-reel expansion covers that central reel and its neighbours, reels two and four. On the three-row mask used here, the finished coverage therefore occupies nine different coordinates.

The expansion contributes six newly converted positions, not nine newly generated positions. The original three cells already existed before the effect. Keeping those categories separate prevents the same central stack from being counted once as a landing and again as additional coverage.

Separate example	Original stack cells	Additional distinct cells	Finished Wild-mask cells
Full Arthur with the reference three-reel expansion	3	6 converted	9
Full Merlin with four verified, non-overlapping destinations	3	4 generated	7

For the Merlin example, suppose history confirms four valid destinations outside his source stack and confirms that none overlap. Seven is then the size of this particular final mask, but four is still the generated-Wild count. Reporting seven generated Wilds would incorrectly include the three cells belonging to Merlin himself. Nor does seven become an advertised fixed result: the published two-to-six output interval and the valid-position rules still apply.

If an actual placement overlaps a pre-existing Wild, the non-overlap assumption fails. Build the union of observed coordinates instead of adding counts mechanically. For instance, adding four event references to a three-cell source does not prove seven unique visible cells when two references address the same position. The server record must establish how that version handles the overlap; this guide does not invent a replacement or skipped-placement rule.

Finally, nine visible Wild positions versus seven is not a payout comparison. Different locations may complete different valid combinations, and substitution exclusions can change evaluation. Preserve the final mask and the actual award rows independently. Count source cells, newly affected cells and credited wins in separate columns, so a larger-looking Arthur effect cannot be mistaken for proof of better expected returns than Merlin.

Official source

• Quickspin: Mighty Arthur

Bottom line: separate Arthur’s adjacent expansion from Merlin’s random Wild placement, then check whether Mystery Nudge completed the stack.

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.