Big Bad Wolf — every second Swoop turns another Pig Wild

Big Bad Wolf by Quickspin was released in 2013 and is described as high volatility. Quickspin publishes two RTP models, 90% and 97%, making the live configuration essential evidence before comparison.

Swooping Reels and Pig conversions

Winning symbols are removed through Swooping Reels and the round continues while new wins form. Every second Swoop turns one of the three Pig symbols Wild. Six consecutive Swoops convert all three.

Count only completed winning Swoops. The conversion threshold belongs to the active sequence and resets according to the live game rules when that sequence ends.

Blowing Down the House

Three Bonus Scatters award ten Free Spins. The Pigs Turn Wild feature remains active during the bonus. Moon symbols collected on the last reel can add Free Spins and provide a chance at a 2× multiplier.

The public page does not state the complete Moon threshold schedule, so the live help should be used for exact requirements and house-stage progression.

RTP and version checks

The 90% and 97% configurations are materially different. Record the live RTP, version, bet range, maximum-win rule and any market-specific feature changes before play.

Swooping sequence map

Winning symbols are removed and replaced under Swooping Reels. Number the starting grid S0 and each later stable state S1, S2 and onward. Record the win that causes every transition.

Only a new credited combination continues the chain and counts as a consecutive Swoop. A refill animation with no win closes the sequence. Keep one base stake for the entire chain.

At close, add every Swoop credit and compare the round total. The final non-winning board is useful evidence of termination even though it adds no value.

Pig conversion thresholds

Every second Swoop converts one of three Pig symbols to Wild. The thresholds are therefore two, four and six consecutive winning Swoops.

Maintain three Pig rows with conversion event and later Wild participation. Do not convert all Pigs after two. At six, all three should be Wild under the published rule.

The source does not specify selection order when several Pig types appear. Use the game animation or history to identify the converted Pig. Never choose the highest-paying one by assumption.

Converted Pig Wilds can create later wins and extend the same Swooping chain. Conversion itself is not a separate win.

Ten-spin feature entry

Three Bonus Scatters award ten Blowing Down the House Free Spins. Capture the trigger, ten-spin counter and opening house state.

Pigs Turn Wild remains active in the feature, so continue to count winning Swoops and conversions within each feature spin. A single Free Spin can contain several Swoop wins while consuming one spin.

Use subrows for tumbles or Swoops beneath each Free Spin. This distinguishes the spin counter from the internal consecutive-win counter.

Moon collection on the last reel

Moon symbols are collected from the last reel. They can award extra Free Spins and provide a chance at a 2× multiplier while the Wolf progresses through houses.

The accessible page does not publish exact thresholds. Record the table from live help before stating counts or awards. Do not borrow the Megaways version’s three- and six-Moon stages.

Keep Moon count, house stage, extra-spin credit and multiplier state in separate fields. A Moon landing does not automatically prove all four changed.

If the multiplier is awarded, use server history to determine when it applies. Do not apply 2× retrospectively to earlier feature wins.

Feature ledger

Begin with ten spins, 1st house state as shown, Moon counter and unconverted Pig set. For each feature spin, record Swoop wins, Pig conversions, Moons, extra spins, multiplier and credits.

Counter arithmetic should show one spin consumed plus any Moon award. Swoops within that spin do not consume additional Free Spins.

At feature end, reconcile all server credits with the summary and balance. Keep base trigger credit and feature credit separately before calculating the round total.

RTP comparison

Quickspin publishes 90% and 97% models. These are alternative deployments, not a range to average. The seven-point difference is substantial.

Capture the active value in help with Game ID and date. Do not assume 97% because it is higher or because an old review used it.

RTP does not predict Swoop length or Moon collection in a short session. It is a long-run model parameter.

Original versus Megaways

The 2013 game uses Swooping Reels and two RTP models. Big Bad Wolf Megaways uses variable heights, up to 117,649 ways, three RTP models and a persistent bonus multiplier.

Do not transfer the Megaways buy price, 96.44% feature RTP or Moon schedule to the original. Shared characters and house theme are not shared mathematics.

The exact title and Game ID should appear in every source record.

Mobile and interruption audit

The Swoop counter, Pig conversions, house state, Moon count and remaining spins should remain readable. On a small screen, last-reel Moons must not sit underneath controls.

After connection loss, restore the round and compare active feature spin, internal Swoop chain and multiplier state. History is stronger than missing animation.

Do not place another stake to test whether the prior chain settled. Open the ledger first.

Maximum and stake data

The public page does not print an overall maximum or stake range in readable copy. Capture those values from the live build and keep currency attached.

Do not label the 2× Moon multiplier as maximum win. It is a feature modifier. Likewise, ten Free Spins is an allocation, not a value guarantee.

If help is unavailable, leave these facts absent rather than importing them from a sequel.

Confirmed boundary

The source confirms 2013 release, high volatility, 90% and 97% RTP, every-second-Swoop Pig conversion, six-Swoop completion, ten Free Spins and last-reel Moon collection.

It does not confirm New Zealand operator access, exact Moon thresholds, bet limits or maximum in readable copy. Those remain primary deployment checks.

The resulting review is specific to the original title and preserves every counter needed to audit a real round.

Worked six-Swoop chain

Swoop one pays and starts the count. Swoop two pays, reaches the first threshold and converts Pig P1. Swoops three and four produce another pair and convert P2. Swoops five and six convert P3, leaving all three Wild.

Every step must be a credited Swoop. If Swoop five is followed by a non-win, the sequence ends before P3 converts. Do not continue the count into a later paid round.

This example illustrates thresholds only. Actual symbols, paylines and values must come from the live history.

Pig Wild settlement

When a converted Pig participates in a later win, identify the symbol it substitutes for and the credited combination. Keep P1, P2 and P3 labels so multiple conversions are not conflated.

A Pig can be Wild without creating a win. Conversion has no standalone cash value unless the paytable says otherwise. The credit arises from the resulting combination.

At round close, retain the conversion map with the server total. It explains how a long Swoop chain evolved.

Moon-stage extraction

Open live help and copy the exact number of Moons required for each house, extra-spin award and 2× multiplier chance. Record whether collection resets between houses.

The source says Moons appear on the last reel. Confirm the client does not count decorative moons elsewhere. Mark each collected Moon by feature spin and Swoop state.

If a threshold is reached mid-Swoop chain, preserve the server order of extra spins, multiplier and win settlement. Do not guess from animation.

Multiplier application

The provider says Moon collection gives a chance at 2×, not that every collection guarantees it. Record the actual award and timing.

When 2× is active, use history to identify which wins it multiplies. Do not apply it retrospectively to earlier houses or to the entire cumulative display unless the rules say so.

Keep house progress and multiplier as separate state fields even when one animation introduces both.

RTP evidence comparison

For a 90% build, label all round records 90%; for 97%, label them 97%. Do not compare observed short-session returns as proof that one configuration is working correctly.

If the operator changes RTP between checks, preserve both dated records. The title and artwork can remain identical while the theoretical model changes.

The provider page is the primary source for the two available models; the live help identifies which one the operator loaded.

Free Spins worksheet

Columns should include starting spins, Swoop count within the spin, Pig conversion, Moon count, house stage, 2× state, spin credit and ending spins.

A feature spin with several Swoops occupies several subrows but decrements the Free Spins counter once. Extra Moon spins are added separately.

At summary, reconcile all subrow credits with the feature total. Keep the base trigger stake and any base Swoop credits outside until full-round reconciliation.

Interface and history checks

The last reel must remain visible because Moon collection depends on it. The house-stage display should persist long enough to record or appear in history.

Converted Pigs should have a stable Wild marker that does not rely on sound. Reduced-motion users still need the final evaluated board.

If history omits Moon details, preserve the feature summary and visible stage changes but do not invent the missing count.

Final source package

Save official product page, live help, RTP screen, paytable, trigger, one complete Swoop chain, feature ledger and account credit.

Mark the check date and operator territory. Provider rules alone do not confirm New Zealand access.

The package should prove every published number and keep the unknown Moon table tied to live evidence rather than another wolf game.

Swoop counter recovery

If connection drops mid-chain, reopen the exact round in history. Record the last credited Swoop, current Pig conversions and final server total.

Do not infer that an unseen refill won. Only history can advance the consecutive count. A missing animation can still correspond to a settled result, but a visual gap is not evidence of another Swoop.

If the round is complete, close the sequence at the server’s final state. Do not place a new bet to continue an old counter.

House-stage worksheet

Create one row per house stage with entry Moon count, Moons collected, extra spins, multiplier outcome and exit state. Populate thresholds only from live help.

Link every stage row to feature spin and Swoop subrows. This preserves the order when a Moon lands during a multi-win cascade.

If the display shows a house collapse without a readable Moon count, record the observed transition and leave the internal threshold unavailable.

Pig conversion and RTP comparison

Use identical Swoop worksheets for 90% and 97% builds, but never combine their results as one configuration. Label each record at the top.

The mechanic thresholds can remain the same while symbol distribution differs. A shared six-Swoop rule does not make the two RTP models equivalent.

When publishing, place the active value near the article’s version date so readers do not overlook the distinction.

Final consistency scan

Every Pig conversion must link to an even Swoop count. Every feature must link to three Scatters. Every Moon claim must link to the last reel and live table.

Remove any purchase price, Megaways multiplier or 117,649-way statement accidentally imported from another wolf release.

Keep the narrative theme secondary to the auditable mechanics and version evidence.

Reconstructing a complete base round

Begin with stake, RTP and initial grid. List the first credited combination and the S0-to-S1 removal. Continue with one row per winning Swoop until the first non-winning state.

At Swoops two, four and six, insert the appropriate Pig conversion event. The converted Wild can participate only in later evaluated states, so do not add its effect to a win settled before conversion.

Sum every server credit and compare it with the round total. Preserve the final empty or non-winning transition as evidence that the chain ended.

Reconstructing a complete bonus spin

One Free Spin can contain multiple Swoops. Start with remaining spins and current house state, then nest Swoop rows beneath it. Record Pig conversion and Moons in event order.

When the internal chain ends, close the Free Spin, apply any documented extra-spin or multiplier changes and move to the next counter value. This prevents every Swoop from being counted as a separate Free Spin.

At the end of ten initial spins plus extensions, reconcile the feature total with the ledger.

Paytable verification

Capture ordinary symbol values, Scatter rule, Pig identities and Wild substitution from live help. The marketing page describes mechanics but does not expose every payment.

Use the paytable loaded with the active 90% or 97% configuration. If the same values appear in both, preserve evidence rather than assuming equality.

Do not reconstruct symbol payments from the later Megaways release. Its grid and ways model are different.

Moon multiplier audit

When a 2× award appears, record the Moon threshold and the precise first win using it. If the multiplier persists across spins or a house stage, mark its start and end.

If the live history shows only a doubled final amount, retain the visible multiplier and server credit without inventing a base subtotal.

The chance language means a completed collection does not automatically prove 2×. Record actual outcome.

Responsible content boundary

Explain the mechanic and evidence trail without suggesting that a long losing sequence makes six Swoops more likely. Each round is resolved by the game model.

Do not turn the 97% option into a claim of likely session profit. RTP is long-run theoretical return and the operator may load 90% instead.

These points belong once in the version discussion; they need not be repeated as generic warnings after every section.

Final operator verification

Confirm official domain, territorial eligibility, active RTP, stake range, maximum and game version. The provider page alone does not establish a New Zealand offering.

If an operator lists the title, capture the lobby entry and in-game help on the same date. A demo link or cached page is weaker evidence of current account access.

Attach those records to the mechanics source so operator and provider claims remain visibly separate.

On mobile, the current Swoop count, converted Pig symbols, remaining Free Spins and last-reel Moon collection should remain visible. A long cascade does not predict another win.

The source does not confirm New Zealand operator availability. Use the Quickspin catalogue guide for that distinction. Big Bad Wolf Megaways is a later variable-ways version with a persistent bonus multiplier and different RTP models.

Frequently asked questions

Which RTP models are published? 90% and 97%.

When does a Pig turn Wild? After every second winning Swoop.

When are all three Pigs Wild? After six consecutive Swoops.

What starts Free Spins? Three Bonus Scatters award ten spins.

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

Official source

• Quickspin: Big Bad Wolf

Bottom line: record the active RTP, Swoop count, Pig conversions and Moon progress as separate evidence states.

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.