High Street Heist — break five glass rows before the bonus

High Street Heist by Quickspin changes from low-to-medium base-game volatility to a super-high-volatility Free Spins feature. The bonus opens all five rows and uses 1,024 ways on every spin.

Breaking the glass

Four-symbol-high stacks can land on every reel. When a full stack lands, it cracks the glazed middle rows unless that same row has already been opened in the current round, and one respin is awarded.

Opening all five rows starts ten Heist Free Spins. The useful record is row state, triggering stack and respin count. Do not count the same already-opened row twice within one sequence.

Heist meter and Diamonds

Inside Free Spins, no area is frozen. After four stacks, the meter resets, awards two extra spins and converts the lowest-paying remaining medium or Robber symbol to a Diamond.

When every Robber has been converted, filling the meter adds 1× to all Diamond symbols and awards another two Free Spins. Track conversion order and Diamond multiplier as separate fields.

Buy and evidence checks

Quickspin publishes a 111× buy price for instant Heist Free Spins and warns that availability varies by market. The readable public page does not print an RTP percentage, so check the live version instead of inventing one.

On mobile, all five row states, stack meter, converted symbols and 1,024-way field should remain visible. The theme and provider rules do not confirm New Zealand casino availability.

The expanding base-game grid

High Street Heist begins with glazed middle rows rather than the fully open five-row bonus field. A four-symbol-high stack can land on any reel. When it reaches a still-frozen row, that row cracks and the round receives one respin. The row remains open for the continuing sequence.

Treat the glass as persistent round state. Label the five possible rows from top to bottom and mark each as frozen or open before every respin. Next record the reel containing the four-high stack and the newly cracked row. This prevents a dramatic animation from being mistaken for more than one unlock.

Quickspin specifies that an already opened row is not cracked again in the same game round. A later full stack may therefore be visible without producing another row change. The correct evidence is the before-and-after glass map plus counter, not stack artwork alone.

The base game is described as low-to-medium volatility, while Free Spins are super-high volatility. These labels compare mathematical behaviour; they do not predict the next round or guarantee a certain number of glass breaks within a session.

From frozen rows to 1,024 ways

Opening all five rows starts ten Heist Free Spins. The bonus has no frozen areas and uses the complete 1,024-way field on every spin. The trigger record should include the final glass break, awarded spin count and first fully open bonus grid.

Ways are not fixed paylines. Use the deployed paytable to identify matching symbols on consecutive reels and let history show the credited ways. The five-row field can create many visible instances of a symbol, but not every group is necessarily a valid win.

Do not describe 1,024 ways as 1,024 guaranteed chances to win. It is the number of possible reel-position combinations under the game’s evaluation model. A spin can still return zero, and the provider does not publish a hit frequency in the readable page.

If a mobile layout crops the top or bottom row, the bonus cannot be audited accurately. Capture the complete grid or use the game’s detailed history, especially when a tall stack begins near a screen edge.

The four-stack Heist meter

Inside Free Spins, stacks feed a separate meter. After four stacks, the meter resets, awards two additional spins and converts the lowest-paying remaining medium or Robber symbol to the Diamond symbol. The meter is not the same as the glass state used for entry.

Create four fields for each free spin: stacks landed, meter before, conversion target and spins added. If multiple stacks appear, rely on history to identify how the counter advances. Do not infer one meter step from each reel unless the help file confirms that interpretation.

The conversion order matters. First identify which eligible medium or Robber symbol types remain. When the fourth stack completes the meter, record the specific type replaced by Diamond. On following spins, use the updated symbol set; do not continue paying or tracking the removed type as if it still existed.

The two added spins can be obscured by the simultaneous consumption of the current spin. Write the starting count, subtract one for play and then add the feature award. This arithmetic explains why the visible counter may rise by one rather than two.

Robber conversion and Diamond escalation

Once all Robber symbols have been converted to Diamonds, later completed meters enter the second state: each fill adds 1× to the value of all Diamond symbols and awards another two Free Spins. That is a different effect from the earlier symbol-type conversion.

Keep a conversion checklist for every Robber type. The transition occurs only when no Robber type remains. A board with no Robber visible on one spin is not sufficient proof; the persistent paytable or meter state must show that the type has been converted for the feature.

Track the Diamond multiplier independently from the stack meter. The meter can reset to zero while the Diamond multiplier persists or increases. At each completion, record the multiplier before, the +1× change and the value used in the next server calculation.

The provider wording says the increment applies to all Diamond symbols. It does not establish that the entire spin win is multiplied. Use the paytable and history to identify the affected component rather than applying the number to unrelated symbol wins.

A complete feature worksheet

Start with trigger route: natural glass clear or 111× purchase. Then record ten initial spins, open five-row grid and any initial state shown. Use one line per resolved spin plus extra lines for meter completion events.

Recommended columns are spin number, starting spins, stack count, meter movement, converted symbol, Diamond multiplier, extra spins, ways win and ending spins. Add the round ID and timestamp once for the feature, then attach screen records in the same order.

Suppose the counter starts at seven and the fourth stack completes during that spin. After the spin is consumed, six remain; the meter then awards two, producing eight. Recording only seven-to-eight would hide the two-spin award. The expanded ledger shows both operations correctly.

At feature end, add the ways credits and compare them with the displayed feature total and account ledger. A celebratory total can be cumulative. The balance movement is the final check for what was actually credited.

Buy Feature at 111×

Quickspin publishes 111 times bet for instant entry to Heist Free Spins. With stake unit B, the confirmation cost should be 111 × B. Save the selected stake and quoted cost before accepting; then verify one debit and the ten-spin open-grid state.

The control may not be available in all markets. The provider page does not prove availability to New Zealand users or at any named operator. Absence of the button is therefore not evidence that the game is incomplete.

The purchase price is not RTP and not a promised return. It buys the defined feature entry. The readable public page does not provide an RTP value, so the live help must supply both ordinary and purchase configuration details where applicable.

If the client changes stake when the purchase panel opens, recalculate the expected cost from the stake displayed on the final confirmation, not from the earlier base-game selection. Preserve the transaction as its own round for ledger reconciliation.

RTP and version checks

Because no percentage appears in the accessible Quickspin copy, this article does not assign one. Open game help in the exact operator build, search for RTP or theoretical return, and capture that screen with Game ID and date. Do not import a figure from a review, sibling game or media pack of uncertain version.

Also capture minimum and maximum stake only if the active client states them. Currency limits can vary by operator and denomination. A range observed in euros cannot automatically be relabelled in New Zealand dollars.

Version checks should be repeated when the operator changes platform or the game help changes. A title and artwork match do not prove identical mathematical configuration. The session record should tie every reported percentage to a specific deployed build.

Mobile interaction audit

Test whether all five glass rows remain distinguishable at normal zoom. The navigation, stake bar and browser controls must not cover top or bottom positions. During respins, confirm that locked-open rows remain visible and the counter does not move behind an animation layer.

In Free Spins, check the meter, its four-step progress, conversion announcement, Diamond multiplier and remaining spins in both orientations. Pause or reduce motion if supported and verify that persistent labels still explain the state after animation ends.

Open history directly after a conversion. It should identify the round and credit even if it does not reproduce every visual. If connectivity drops during a respin or meter completion, reload history before starting another paid round.

Paid entry needs a clear confirmation separated from the spin control. Keyboard focus and touch targets should make cancellation possible without accidental acceptance. Returning from the rules panel should not silently change stake.

What the source confirms

The official page confirms tall stacks, glass cracking, added respins, five-row trigger, ten Free Spins, 1,024 ways in the feature, the four-stack meter, staged Diamond conversion, +1× Diamond increments, two-spin additions and 111× purchase.

It does not publish a readable RTP percentage, stake range, maximum win, New Zealand operator list or NZD support. It also does not quantify stack or feature frequency. Those facts remain unclaimed until the active help or another primary document provides them.

This distinction lets the review be detailed without pretending the provider’s mechanic page is evidence for a local operator. Readers get an auditable state map and a precise list of deployment facts still to verify.

Glass-map failure cases

Three events can look similar but should be logged differently. A tall stack landing against a frozen row creates a crack and respin. A tall stack aligned with an already opened row does not reopen it. A partial stack does not satisfy the four-symbol-high condition. Save the full reel and row state so these cases can be distinguished.

If several reels display tall stacks in one settled state, the accessible description does not specify an independent respin for every visible stack. Use the server counter and history to record the actual award. Never multiply the feature text by the number of stacks without confirmation.

The five-row completion should be attached to the precise round that opened the last frozen row. Check that ten Heist Free Spins follow and that no paid wager is deducted for the transition. If the screen reconnects directly inside the bonus, history should still show the originating glass-clear event.

Diamond conversion register

Create a register listing each eligible medium and Robber symbol from the live paytable. Mark the lowest remaining candidate before every fourth-stack event and record the Diamond replacement afterward. This makes the published conversion order testable.

Once a type has converted, all later appearances must be interpreted according to the feature’s current state. A screenshot from the base game is not an adequate legend because the bonus paytable is changing. Save the live meter panel or history after each reset.

When the last Robber disappears, add a boundary marker. Meter fills before that boundary perform conversion; fills after it increase all Diamond values by 1× and add spins. Mixing these phases can cause a reviewer to expect a multiplier while an unconverted Robber still remains.

Comparing natural and purchased entry

Natural entry preserves the entire path of glass unlocks and respins. Purchased entry starts at the ten-spin Heist feature for the quoted 111× cost. Both routes should reach the same published bonus framework, but their ledgers differ before entry.

For natural entry, record one ordinary wager and the full unlock chain. For purchase, record the confirmation multiple and one feature-cost debit. Do not add a fictional value for the glass states skipped by purchase, and do not call the purchase a bonus from the casino; it is a game control where enabled.

Compare the first bonus state after entry: five rows open, ten spins shown and meter at the state recorded by the game. If a deployed help file states additional differences, attribute them to that version rather than assuming them from the marketing page.

Session and ledger close

At feature end, calculate three subtotals: ways wins before any conversion, wins after symbol conversion and wins after Diamond-multiplier escalation. The sum should match the feature total, subject to the exact presentation rules in history.

Next compare the credited total with the balance. If a purchase was used, keep its 111× debit on a separate line and calculate net movement only afterward. A gross feature total is not profit.

Store Game ID, version, displayed RTP, stake unit, entry route and timestamp. Those fields allow a later reviewer to distinguish a mathematical update from a recording error.

Questions for the live help file

Before publishing operator-specific details, use the deployed rules to answer a short list. Which RTP version is active? What are the currency-specific stake limits? How does history count several four-high stacks in one state? Which medium and Robber symbols participate in the conversion order? Does the Diamond increment apply to the symbol value shown in the paytable or another component? How are interrupted respins restored?

These are not gaps to fill with estimates. They are version-control questions created by the documented mechanics. Record the answer, screenshot location, Game ID and check date. If the help does not answer one, label it unavailable. This keeps the review stable even when an operator changes its client or denomination settings.

Repeat the check after a material client update. Preserve the previous capture rather than overwriting it, because a changed rule panel can explain why two otherwise similar session records show different configuration details.

Sticky Bandits Trail of Blood uses sticky Wild positions instead of glass rows. The Quickspin guide covers active-version checks.

Frequently asked questions

What opens a glass row? A four-symbol-high stack landing in that row state.

What starts Free Spins? Opening all five rows.

How many spins start the bonus? Ten.

What is the buy price? 111× the bet where available.

Is New Zealand availability confirmed? No. Provider documentation does not establish it.

Official source

• Quickspin: High Street Heist

Bottom line: preserve the five-row glass state and four-stack meter because they control different transitions.

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.