Twisted Lab — rotate the grid before reading the Ooze

Twisted Lab by Hacksaw Gaming is a five-reel, five-row game using 19 paylines. The official page identifies RotoGrid™, Oozing Beakers and two different bonus structures. It also publishes 4/5 volatility and a 15,000× maximum win, but not a readable RTP, stake range or full paytable.

RotoGrid resolves after the first win check

A RotoGrid symbol carries one to four 90-degree clockwise rotations. Wins from the initial drop are calculated before the first rotation. That order matters: the rotation can reposition symbols and break Beakers, but it does not rewrite how the opening drop was scored.

Oozing Beakers create reel-wide Wild zones

When rotation breaks a Beaker, its liquid falls to the bottom of that reel. Covered positions become Wild. Purple liquid has no multiplier. Blue Beakers add values, while Pink Beakers use multiplying values. If new liquid covers an existing Ooze position, values combine and the resulting multiplier applies to all Oozing positions on that reel. The official help lists the possible values; verify the deployed version before using them as a staking assumption.

Two bonus paths use different state

Three FS scatters trigger Unleash the Ooze! with 10 free spins and increased chances for RotoGrid, FS and Beaker symbols. The Twist of the Twisted! instead uses Blue and Pink Twisters, Collector symbols and three refilling lives. Blue Twisters rotate with RotoGrid; Pink Twisters also rotate at the start of every new free spin. A Collector gathers the current values, while uncollected Twisters remain until collected or the feature ends.

Evidence limits

The public source confirms the grid, win type, volatility, features and maximum-win claim. It does not publish a readable RTP, minimum or maximum stake, complete symbol paytable, release version or confirmed New Zealand casino availability.

Opening-drop settlement comes first

Twisted Lab evaluates the initial five-by-five grid before RotoGrid moves anything. Record all 19 payline wins, participating Wilds and opening credit. Only after that settlement should the first clockwise rotation be applied.

This prevents a symbol’s post-rotation coordinate from being used to calculate the opening grid. Keep one board image per state and a common round identifier.

If no RotoGrid appears, the round follows the ordinary evaluation and cascade rules shown by the deployed help.

Reading a RotoGrid symbol

A RotoGrid carries one, two, three or four 90-degree clockwise rotations. Save the displayed count and decrement it after each completed turn.

Four quarter-turns return the geometric grid to its original orientation, but intermediate breaks and Ooze changes can alter state. Do not skip directly to the final orientation.

Number every cell so symbols can be tracked as they move between rows and reels.

Rotation-state ledger

For each quarter-turn, store grid before rotation, moved coordinates, broken Beakers, new Ooze, combined values, wins and remaining rotations. The output of one turn becomes the input of the next.

Payline settlement order should follow the live help. Do not assume every intermediate orientation pays unless the game records a win check there.

Preserve the terminal board before the next paid round or bonus spin.

Breaking a Beaker

When rotation breaks a Beaker, its liquid falls to the bottom of that reel. Record Beaker colour, original coordinate, destination reel and every covered cell.

Covered positions become Wild. Liquid acts by reel after the break; do not spread it across adjacent reels without a published rule.

If multiple Beakers break on one turn, preserve event order or the combined state shown by server history.

Purple Ooze

Purple liquid creates Wild coverage without a multiplier value. Mark all covered positions and label the reel’s multiplier state as neutral rather than inventing 1×.

When later Blue or Pink liquid covers an existing Purple position, record the new combined state from the game. Purple’s absence of a value does not prevent the position from becoming part of a valued Ooze zone later.

Settlement still depends on the 19 paylines crossing covered Wild cells.

Blue Ooze

Blue Beakers use adding values. Record the displayed amount and current reel Ooze value before combination. Apply the provider’s addition order and store the closing value.

Every Oozing position on that reel uses the resulting multiplier when participating under the live rules. A position on another reel does not inherit it.

Do not multiply two Blue values together or apply a Blue amount as a cash award by itself.

Pink Ooze

Pink Beakers use multiplying values. Record the prior reel value, Pink factor and post-combination result. If no valued Ooze exists, the live help must define how the factor starts.

Do not substitute an assumption from another game. Preserve the actual display and configuration.

After combination, all Oozing positions on that reel share the resulting multiplier under the provider description.

Overlapping liquid

When new liquid covers an existing Ooze position, values combine. Use a chronological reel ledger because adding then multiplying may differ from multiplying then adding.

Track coverage and reel value separately. A new Beaker can extend the set of Wild cells and change the multiplier in one event.

Avoid counting the same covered cell twice when different liquid animations overlap.

Worked rotation example

Suppose a two-turn RotoGrid rotates after the opening win check. The first turn breaks a Blue Beaker and covers two cells on reel four. The second breaks a Pink Beaker on the same reel, extending coverage and multiplying its current value.

The ledger saves opening grid, first Blue state, second Pink state and final payline settlement. It does not apply Pink before Blue or rotate the board 180 degrees in one undocumented step.

Illustrative states explain order without promised values.

Unleash the Ooze entry

Three FS scatters start ten Free Spins. Save the trigger grid, starting counter and version. The mode increases chances for RotoGrid, FS and Beaker symbols, but the public page does not quantify those increases.

Open one rotation and Ooze ledger per primary Free Spin. Determine from live help whether any liquid state persists between spins.

Do not decrement the main counter for nested rotations.

Free-spin extensions

Record every additional FS event and counter transition from the deployed rules. The accessible summary names increased FS chance but does not provide a complete readable extension schedule.

Do not invent additions based on another Hacksaw title. Use only the live counter and official help.

Keep extensions separate from RotoGrid’s one-to-four rotation count.

Twist of the Twisted entry

This mode uses Blue and Pink Twisters, Collector symbols and three refilling lives. Save the trigger, initial lives and all starting Twister coordinates and values.

Uncollected Twisters remain until a Collector gathers them or the feature ends. Maintain stable IDs and values across feature states.

A successful qualifying event can refill lives according to the deployed counter; record every reset.

Blue Twisters

Blue Twisters rotate with RotoGrid. Record their position before and after each grid turn, displayed value and collection state.

They do not receive the extra start-of-spin rotation attributed to Pink unless the live help states otherwise.

Copy uncollected Blue IDs forward until collection or feature end.

Pink Twisters

Pink Twisters rotate with RotoGrid and also at the start of every new Free Spin. Record the start-of-spin movement before other feature events.

This extra movement distinguishes Pink from Blue. A screenshot after movement needs the prior state to prove the transition.

Keep value changes and position changes in separate ledger columns.

Collector symbols

A Collector gathers current Twister values. Record every collected ID, its value at that moment and the resulting subtotal. Mark those Twisters consumed if the game removes them.

Do not include uncollected symbols elsewhere on the grid. If multiple Collectors land, preserve event order and updated remaining set.

Compare the collection with the lives counter and final settlement.

Refilling-lives termination

The bonus begins with three lives and ends after the required sequence without a Twister or Collector landing. Record lives before and after every feature state and the event responsible for any refill.

Animation alone does not reset the counter. Use persistent display and server history.

At termination, settle collected values and handle uncollected Twisters according to the live rules without inventing a credit.

Payline and multiplier settlement

Obtain all 19 line paths, symbol values, Wild substitutions, Ooze arithmetic and Collector rules from the deployed help. For each win, identify Oozing positions and their reel multiplier.

Keep base line award and multiplier application separate. Sum feature credits and compare with account history and the 15,000× cap.

The cap is a ceiling, not a likely outcome.

RTP, stakes and version

The provider page gives 4/5 volatility and 15,000× maximum but no readable RTP or stake interval. Record those missing fields from the exact game with operator, currency, version and date.

If multiple RTP configurations exist, publish only the tested one. Do not combine numerical fields across builds.

Volatility 4/5 is a provider scale, not a prediction for a session.

New Zealand availability

The global page does not prove real-money access in New Zealand. Verify country terms, registration eligibility, authenticated catalogue and 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 25 cells, orientation, rotation count, liquid coverage, reel multiplier, Twister positions, lives and counters must remain visible. Test portrait and landscape modes.

Liquid colours need text labels and operations. Reduced-motion mode should preserve quarter-turn order. Keyboard focus must reach help, paytable and history.

After interruption, compare mode, grid orientation, Ooze ledgers, lives, balance and round identifier with server history.

Support-ready evidence

For RotoGrid, provide every pre/post rotation grid and remaining count. For Ooze, provide Beaker colour, coverage, prior reel value and result.

For Twisters, add position history, collection IDs and lives transitions. Include operator, version, stake, currency and round identifier.

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

Session controls

Persistent Ooze and uncollected Twisters can feel like stored value. They exist only inside the active feature and do not make another Collector or RotoGrid due.

Set stake, spending and time limits before play. Do not increase stakes to chase a Pink combination or the 15,000× cap.

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

Publication checklist

• Pay opening-grid wins before rotation.
• Apply one-to-four clockwise quarter-turns individually.
• Record Beaker colour and reel coverage.
• Treat Purple as Wild coverage without multiplier.
• Apply Blue as addition and Pink as multiplication.
• Keep coverage and reel value separate.
• Track Pink’s extra start-of-spin movement.
• Collect only documented Twister values.
• Reconcile three-life transitions from the live counter.
• Verify RTP, stakes and New Zealand access through primary evidence.

Editorial assessment

Twisted Lab is defined by sequence: opening settlement, quarter-turn movement, Beaker break, Ooze combination and later payline evaluation. The collection bonus adds a separate position-and-lives ledger.

A rigorous review records every orientation and reports 4/5 volatility and 15,000× only in their source context. Missing RTP, stakes and local availability remain unclaimed until verified live.

Coordinate transformation worksheet

Number the 25 grid cells by reel and row, then assign each a second coordinate after every clockwise quarter-turn. A worksheet should show old position, new position, symbol identity and whether a Beaker broke during movement.

This prevents the same symbol from being treated as newly landed after rotation. It also proves which reel receives falling liquid, because the Beaker’s destination is evaluated in the rotated state rather than its opening coordinate.

For two or more turns, chain the mappings instead of calculating directly from the opening board; intermediate Ooze can change later settlement.

Combining Blue and Pink values

Maintain an expression for each reel’s Ooze multiplier. A Blue event appends an addition; a Pink event appends multiplication in the order resolved by the game. Keep parentheses exactly as the live display implies.

Do not group all Blue values first and Pink values second if they arrived in another sequence. The same set of numbers can produce a different result when operations are reordered.

Store the expression and final value beside the coverage mask so every Wild cell on that reel can be audited consistently.

Several Beakers on one rotation

If one quarter-turn breaks several Beakers, record each colour, source and destination before changing the reel ledgers. Use the event order exposed by animation or server history.

Two liquids can cover the same cell while affecting one shared reel multiplier. Count the cell once in the coverage mask but preserve both value operations.

If the live client resolves them simultaneously, save the combined before-and-after state and avoid inventing an unseen intermediate award.

Version comparison protocol

Attach each verification to operator, build, currency and date. Compare grid rotation, initial-win timing, Beaker values, liquid operation order, bonus triggers, Twister movement and lives reset individually.

Archive one multi-turn RotoGrid, one mixed Blue/Pink Ooze reel and one Collector event with the matching help. These reference rounds distinguish real product changes from a visual redesign.

If primary sources conflict, retain both dated states. Do not merge RTP or stakes from one build with Ooze values or bonus rules from another.

Practical reader decision points

Before play, verify live RTP, complete stake, country eligibility, maximum exposure and responsible-play controls. During a round, ask what the opening grid paid, how many turns remain, which Beakers broke and what each reel’s Ooze expression is.

During the collection bonus, add Twister IDs, movement source, collected status and lives. These fields reconstruct settlement without suggesting a Collector is due.

After feature end, clear orientation, Ooze and Twister ledgers and apply the pre-set session boundary. Uncollected values are not account cash.

Final verification note

Before updating the article, reproduce the one-to-four rotation range, Purple neutral state, Blue addition, Pink multiplication and Pink start-of-spin movement in the current official help. Confirm the 19 paylines, 4/5 volatility and 15,000× cap remain attached to the same build.

Any field that cannot be reproduced should retain its source date and be labelled configuration-specific rather than current New Zealand operator evidence.

Preserve every supporting capture, grid coordinate and arithmetic worksheet with the corresponding round identifier for later editorial review.

Keep dates visible.

Frequently asked questions

What is RotoGrid? A symbol that can rotate the full grid one to four times by 90 degrees.

When are initial wins paid? Before RotoGrid activates.

What does Purple Ooze add? Wild coverage without a multiplier value.

How does the Twister bonus end? When its three refilling lives expire without a Twister or Collector landing.

Is RTP published on the source page? No readable RTP is shown.

Is New Zealand availability confirmed? No.

Official source

• Hacksaw Gaming: Twisted Lab

Bottom line: audit the drop, rotation and Ooze combination as three separate stages.

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.