Big Bad Wolf Megaways — tumbles build Wilds before the moon stage

Big Bad Wolf Megaways by Quickspin uses six variable-height reels with up to 117,649 ways to win. Quickspin publishes three base-game RTP models—90%, 94% and 96%—so the live configuration must be checked before comparisons.

Ways and tumbles

When seven symbols land on each of the six reels, the game reaches 117,649 ways. Winning symbols are removed and replaced: symbols drop top to bottom in the drop area and move right to left in the slide area. Tumbles continue while new wins form, and each win is added to the sequence total.

After two, four and six tumbles, the first, second and third Piggy symbols convert into Piggy Wilds across reels two to five. Count completed tumbles, not visual cascades that produce no win.

Blowing Down the House

Three Moon Bonus Scatters in the base game award eleven Free Spins. The Win Multiplier starts at 1×, increases by one after each win and does not reset between the remaining Free Spins.

Collected Moon Scatters advance the feature: three add three spins and 5× to the multiplier; six add three spins and 10×; each Scatter beyond six adds one further spin. The live help should confirm whether the thresholds count within one spin or cumulatively for the version in use.

Buy feature and RTP

Quickspin lists a 90×-bet purchase for direct entry to Blowing Down the House and states a theoretical payout of 96.44% for that Buy feature. The control may not be available in all markets. Do not confuse the purchase RTP with the game’s selectable 90%, 94% or 96% base configurations.

Before play, record the live RTP, version, maximum win, bet range and Buy availability. On mobile, variable reel heights, tumble count, Piggy conversions, Moon count and persistent multiplier should remain readable.

Calculating the current ways

Megaways uses the number of active symbol positions on each of six reels. If every reel displays seven, the product is 7 × 7 × 7 × 7 × 7 × 7 = 117,649. A smaller reel-height combination produces fewer ways for that state.

Record reel heights before each evaluation rather than carrying the opening number through the tumble sequence. The layout can change when symbols drop and slide. The server history remains authoritative for credited combinations.

Ways are not fixed paylines. A matching symbol can occupy several positions on adjacent reels, and the number of contributing combinations follows the active grid. Do not draw ten or twenty conventional lines over the board.

The 117,649 figure is a maximum number of ways, not a maximum prize or a guarantee that every spin presents that many routes.

Drop and slide areas

Winning symbols are removed. New symbols fall from top to bottom in the drop area and travel from right to left in the slide area. Both movements belong to the same tumble system.

Number stable grids G0, G1 and onward. For each transition, record the credited way, removed cells, replacement direction and next stable state. Continue while the new state forms another win.

Only winning tumbles count toward the Piggy thresholds. A visual refill or slide with no new win closes the chain and should not advance the conversion count.

At round end, add all tumble credits and compare them with the sequence total. There is one ordinary stake for the parent spin.

Piggy conversion thresholds

After two, four and six winning tumbles, the first, second and third Piggy symbols convert into Piggy Wilds on reels two through five. Treat those as three thresholds on one sequence counter.

Create columns for tumble count, Piggy identity, reel and conversion state. At tumble two, mark the first conversion; at four, the second; at six, the third. Do not convert all visible pigs at the first threshold.

The provider wording does not fully explain ordering when several Piggy symbols are present. Use the game history and visual transition to identify “first”, “second” and “third” for the deployed build.

Converted Wilds can contribute to later tumbles in the same chain. Record their participation without increasing the counter unless the resulting board produces a server-recognised win.

Free Spins entry state

Three Moon Bonus Scatters in the base game award eleven Free Spins. The Win Multiplier begins at 1×. It increases by one after each win and does not reset across the remaining spins.

Save the trigger board, Scatter count, eleven-spin allocation and 1× opening meter. Use one row per free spin with subrows for every tumble win because several wins can occur under one consumed spin.

The phrase “each win” means multiplier progression may occur more than once during a tumbling spin. Capture the server event order. Do not raise the meter for a tumble state that produces no credit.

Apply the multiplier according to the live history timing. The provider states growth after each win, so a reviewer must distinguish the multiplier used for the current credited win from the value carried to the next evaluation.

Moon collection stages

Inside Free Spins, Moon Scatters advance staged awards. Three collected Moons add three spins and five to the multiplier. Six collected Moons add three spins and ten. Each Moon beyond six adds one spin.

The source language says “collect”, indicating a running feature count. Record the cumulative total after every spin. At three and six, mark the threshold award once. Do not repeatedly add the same stage on later spins while the count remains above it.

For a count moving from two to four, history should show the three-Moon stage and the fourth Moon’s state. The published text specifies extra-spin treatment only beyond six, so do not invent a separate award for counts four and five.

After six, each new Moon adds one spin. Write counter arithmetic separately from multiplier growth caused by wins; the Moon counter and win multiplier are different systems.

Feature ledger example

Suppose a feature spin begins with eight remaining and multiplier 4×. The spin is consumed, leaving seven. Two tumble wins occur. Record the first credit under the server’s active value, increase the meter by one, then record the second under the next value and increase again.

If the same spin takes cumulative Moons from two to three, add three spins and five to the multiplier at the stage shown by history. The closing counter becomes ten before any other award, while the multiplier carries both win increments and the +5 stage increment.

This example demonstrates bookkeeping only. Actual timing and amounts must come from the live record. Do not use it to predict results.

90× purchase and 96.44% route

Quickspin lists 90× bet for direct entry to Blowing Down the House and publishes 96.44% theoretical payout for that Buy feature. The figure belongs to the purchased route.

Capture selected base bet, 90× quoted cost, active ordinary RTP, purchase RTP, confirmation, debit and eleven-spin entry. The purchase should not be described as a 96.44% base game.

The control may be disabled by market or operator. The provider page does not confirm its availability in New Zealand. Natural entry remains a separate mechanic even where purchase is unavailable.

When calculating net movement, subtract the feature cost from gross credits. Do not call gross feature total a profit.

RTP version control

The standard game has 90%, 94% and 96% models. They are alternatives. Open the live help and record the loaded one with Game ID, operator and date.

Do not average the percentages or assume 96% because it is the highest. A lobby thumbnail and identical title do not prove the same mathematical configuration.

RTP is a long-run theoretical parameter. It does not predict tumble length, Moon collection or Piggy conversion frequency in a session.

If the operator page conflicts with in-game help, preserve both and use the game client for the played version while requesting clarification.

Mobile state verification

Variable reel heights must remain fully visible. Check that browser controls do not cover the top of a seven-symbol reel or the slide area. Tumble count and converted Piggies should be reviewable after animation.

During Free Spins, keep Moon count, remaining spins and persistent multiplier on screen. Reduced-motion or turbo modes must not remove access to the settled states and history.

After a network interruption, restore the same round and compare reel state, tumble sequence, Moon count, multiplier and remaining spins. Do not place another bet until the server result is known.

Source and title separation

Big Bad Wolf Megaways differs from the original Big Bad Wolf, Christmas Special, Pigs of Steel and LIVE. Shared characters do not create shared RTP, reels or bonus rules.

The source confirms variable Megaways, tumbles, Piggy thresholds, eleven-spin entry, persistent multiplier, Moon stages, three RTP models and purchase terms. It does not confirm New Zealand operator access, stake limits or an overall maximum win in readable copy.

Archive the official source, live help and Game ID. That record supports a detailed review without borrowing facts from another wolf title.

Current-way worksheet

Create six columns for reel heights. Multiply them to produce the current ways ceiling for that grid. Keep the product next to the server result, but do not use it to manufacture a payout calculation without symbol counts and paytable values.

After a tumble, enter a new row because heights can change. The slide area moves horizontally and the drop area vertically, so a screenshot should include both regions where the client separates them.

If all six reels show seven, confirm 117,649. A single reel at six reduces the product, and the headline maximum no longer describes that state.

Piggy register example

Start the tumble counter at zero. After the second credited tumble, note Piggy conversion P1. At four, note P2; at six, P3. Keep their reel positions and Wild participation on later boards.

If the chain ends at five, the third Piggy never converts in that round. Do not round the count upward because the animation suggests another cascade might have happened.

When a conversion helps create the next win, credit that win as the next tumble event. The conversion itself remains a threshold action, not a separate payout.

Multiplier sequencing

For every bonus win, record multiplier before settlement and after its +1 increase. Use the server breakdown to identify which value applies to the credited amount.

When a Moon threshold adds +5 or +10, enter that movement separately from the win increment. A spin can contain both, and combining them into one unexplained jump hides the source.

The multiplier persists between Free Spins. A losing spin leaves it at its current value; it does not reset to 1×.

Moon counter edge cases

Record each Moon object and cumulative total. Crossing three and six can occur during a spin that also tumbles, so preserve the event order from history.

Beyond six, each additional Moon adds one spin. Do not add another +10 multiplier at seven or eight. The six-Moon stage is awarded once.

If a single state jumps from five to seven Moons, the expected published components are the six-Moon stage plus one beyond-six spin, subject to the live server record.

Purchase reconciliation

For 90× entry, confirm the feature begins with eleven spins and the multiplier state described by the game. The purchase debit must equal ninety times the displayed base bet before any feature credits.

Keep the 96.44% buy RTP in the purchase record. Keep the ordinary 90%, 94% or 96% value in the base-game record. Never substitute one for the other.

If the button is unavailable, remove purchase instructions from operator-specific copy while retaining the provider-level description as conditional.

Final ledger close

Sum base-trigger credits, tumble credits and Free Spins credits according to server history. For purchased entry, show debit, gross credit and net movement separately.

Attach the ending balance and feature summary. If cumulative displays include the original bet or use coins, translate only with the client’s documented denomination.

Mark any missing sub-calculation unavailable. The final account credit can be verified even when animation-level allocation is not exposed.

Publication checklist

Confirm title, six-reel Megaways layout, RTP, stake range, purchase state, Moon wording and maximum-win rule. Date every deployment fact.

Ensure 117,649 is described as ways, not paylines or win multiplier. Ensure Piggy thresholds are counted by winning tumbles. Ensure Moon and win multipliers are different counters.

The final text should explain the model without promising a long tumble chain or implying that provider availability establishes New Zealand access.

Feature-stage reconciliation

Divide the bonus into stages: before three Moons, from three to five, at six, and beyond six. Store the multiplier and spin counter at each boundary. This makes threshold awards visible without repeating them.

Within every stage, list tumble wins in event order. A spin can have several multiplier increments while consuming only one Free Spin. Moon additions alter the counter separately.

At feature close, reconcile all event credits, the cumulative display and account balance. Keep the base-game trigger and any purchase debit outside the bonus subtotal until net movement is calculated.

Piggy-Wild contribution check

For each converted Piggy, record the first later win in which it substitutes. Use the live paytable to identify the symbol replaced and the server amount.

A conversion with no later win still belongs in the tumble history but contributes no independent cash credit. Avoid assigning value simply because the Wild appeared.

If several converted Piggies join one way, use the active reel heights and symbol counts. Do not reconstruct the result as a fixed payline.

Maximum and volatility fields

The accessible provider page does not publish an overall maximum or volatility label in the mechanic excerpt used here. Check live help and quote only the displayed version.

Do not use 117,649 as a maximum multiplier; it is a ways count. Do not use 96.44% as a volatility measure; it is the Buy-feature RTP.

These label checks prevent the most damaging numerical errors in a Megaways review.

Keep the final source record in bet multiples as well as currency. Bet multiples preserve the rule when an operator changes denomination, while the dated currency ledger proves the amount actually credited in the checked session. Both views are needed for a reproducible audit.

The provider page does not establish access from New Zealand. Compare it with the Quickspin catalogue guide. Big Bad Wolf LIVE is a separate communal-format product with different rules.

Frequently asked questions

What is the maximum number of ways? 117,649 when all six reels show seven symbols.

When do Piggies become Wild? After two, four and six winning tumbles.

What starts Free Spins? Three Moon Bonus Scatters award eleven spins.

Which RTP models are published? 90%, 94% and 96%; the Buy feature is separately stated at 96.44%.

Is New Zealand availability confirmed? No. Provider publication does not establish operator access.

Official source

• Quickspin: Big Bad Wolf Megaways

Bottom line: keep variable ways, tumble thresholds, Moon collection and multiplier growth in separate evidence columns.

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.