Ze Zeus — Divine Squares reveal value in a fixed order

Ze Zeus by Hacksaw Gaming is presented as a six-reel, five-row cluster game. The official source confirms Super Cascades, Divine Squares and three Free Spins levels, plus a 10,000× maximum-win claim. It does not expose a readable RTP, stakes or complete paytable.

Super Cascades remove every matching payer

When a cluster wins, all regular paying symbols of that same type are removed from the grid, not only the symbols inside the winning cluster. New symbols then drop into the empty spaces. Squares behind winning symbols become Divine Squares.

Win to Win has a strict activation order

After all wins are complete, a Hand of Zeus activates Divine Squares. Reveals may produce Bronze, Silver or Gold Coins, Vessels of Wealth or Zap of Zeus symbols. Coins are bet-multiple cash values. Zap symbols then multiply adjacent Coins and existing Vessels. Vessels activate from top to bottom and left to right, collecting Coins and other Vessels. After the last Vessel resolves, other Divine Squares reveal again and the cycle repeats.

Three bonus levels change persistence

Three FS scatters trigger What If Zeus Was One of Us?; Divine Squares stay marked between spins until the Hand activates them. Four trigger Ze Zeus Take the Wheel, where marks persist even after activation. Five trigger Ze Zeus Might Superstar, guarantees a Hand on every free spin and removes Bronze Coins. Additional FS symbols can award more spins, with the exact schedule published in the official help.

Evidence limits

The provider page supports the grid, cluster mechanic, feature order, bonus tiers and maximum-win claim. A readable RTP, stake limits, full paytable, version identifier and New Zealand casino availability are not supplied.

Super Cascades remove by symbol type

When a cluster wins, identify every regular paying symbol type in that result. Remove all visible copies of those types, including matching symbols outside the original cluster. Mark every removed coordinate before replacements fall.

Do not remove FS symbols, special objects or another regular type merely because it is adjacent. The qualifying type list comes from the evaluated cluster.

The output grid becomes the input to the next cascade. Preserve every state until no new win appears.

Creating Divine Squares

Positions behind winning symbols become Divine Squares. Assign each square a coordinate and generation number. A position can remain marked across several states depending on the active bonus.

The mark belongs to the cell, not the original symbol identity. A new symbol falling into that position does not erase its coordinate unless the mode’s reset rule says so.

Keep the Divine map separate from the list of symbols removed by Super Cascades.

Hand activation boundary

After all current wins finish, a Hand of Zeus activates Divine Squares. Save the terminal cascade grid and complete map before the reveal begins.

Do not activate the Hand after every individual cluster unless the deployed history shows that order. The provider description places it after the win sequence.

If no Hand appears in a mode where it is not guaranteed, preserve the marked map according to that bonus’s persistence rule.

First reveal: Coins and special objects

Divine Squares can reveal Bronze, Silver or Gold Coins, Vessels of Wealth and Zap of Zeus symbols. Record every coordinate, object type and displayed value before modification.

Coin values are bet multiples. Metal colour describes a class, but the actual number must come from the reveal or paytable.

Do not count a concealed square as a coin until it opens.

Zap of Zeus

Zap symbols multiply adjacent Coins and existing Vessels. Record the Zap coordinate, adjacency geometry, factor and every recipient’s pre- and post-value.

Do not apply Zap across the entire grid. Nor should it affect an object revealed only after the current Zap stage unless the live order explicitly allows it.

When several Zaps overlap, preserve chronological operations because repeated multiplication changes later Vessel contents.

Vessel activation order

Vessels activate top-to-bottom and left-to-right. Number them in this exact order before collection. Each Vessel collects Coins and other Vessels under the live rule.

An earlier Vessel can change the value available to a later one. Save the grid after each activation; do not calculate all Vessels from the original reveal state.

Mark collected objects to prevent duplicate credit.

Repeat reveals

After the last Vessel resolves, other Divine Squares can reveal again and repeat the cycle. Open a new reveal generation while preserving prior operations.

Within every generation, follow Coins and objects, Zap modifications, then ordered Vessel collection. Do not combine generations into one simultaneous board.

The final settlement requires the complete chronological ledger.

Worked reveal example

Suppose one generation reveals several Coins, one Zap and two Vessels. Apply the Zap only to adjacent eligible objects, then activate the upper or leftmost Vessel before the later one.

If another Divine Square opens after collection, start generation two and repeat. Add final values and apply the documented bet at the proper settlement stage.

The example supplies no invented amounts or probability.

Three-scatter bonus

Three FS scatters trigger What If Zeus Was One of Us? Save the trigger grid, initial counter and Divine map. Marked squares persist between spins until the Hand activates them.

After activation, use the live state to determine which marks clear. Do not retain them under the four-scatter tier’s stronger rule.

Record every new winning position added before the next Hand.

Four-scatter bonus

Four scatters trigger Ze Zeus Take the Wheel. Divine Squares persist even after activation. This is the key difference from the lower tier.

Copy the marked coordinate map forward through reveals and later Free Spins. New winning positions add to it; existing marks remain until feature end under the published rule.

Keep the mode name in every ledger row to avoid applying this persistence to the three-scatter bonus.

Five-scatter bonus

Five scatters trigger Ze Zeus Might Superstar. It guarantees a Hand on every Free Spin and removes Bronze Coins from the reveal pool.

Save all five trigger positions, initial counter and first guaranteed Hand. Record revealed coin classes to confirm Bronze is absent.

The guarantee concerns Hand activation, not a particular value or payout.

Bonus persistence comparison

The three tiers form a progression: marks wait until Hand activation; marks survive activation; then Hand appears every spin and Bronze is removed. Build a table with trigger count, mark reset, Hand guarantee and coin-pool change.

Do not infer higher expected return solely from these qualitative upgrades. RTP and feature probability are missing from the accessible page.

At feature end, clear all Divine marks.

Additional Free Spins

The provider says additional FS symbols can award more spins and publishes the schedule in official help. Record the exact scatter count and counter transition from the deployed version.

Do not import +2/+4 rules from another Hacksaw game if this title’s schedule differs. The live counter is authoritative.

Keep retrigger additions separate from cascade and reveal generations.

Cluster and reveal ledger

Use one row per primary spin with counter, opening Divine map, cascade states, new marks, Hand event, reveal generations, Zap operations, Vessel order and credit.

Nested cascades do not decrement the Free Spins counter. Persistence applies only according to the active tier.

At feature end, reconcile all spin settlements with the feature total and account history.

Bet definition and settlement

Coins are bet-multiple values. Record the full round stake and confirm the provider’s definition of bet. Do not confuse coin value, line stake or another denomination.

Preserve intermediate values after Zap and Vessel collection, then apply the bet in the live order. Compare with the 10,000× cap.

The cap is a ceiling, not an expected result.

RTP, stakes and version

The provider page does not expose readable RTP, stake range, default denomination or volatility. Collect them from the exact deployment with operator, currency, version and date.

If multiple RTP versions exist, publish only the tested one. Do not combine numerical fields from separate builds.

The bonus tiers and max-win claim cannot be used to calculate RTP.

New Zealand availability

The global page does not prove real-money access in New Zealand. Verify country terms, registration eligibility, authenticated catalogue and successful 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 30 cells, cluster removal, Divine marks, reveal objects, Zap targets, Vessel order and counters must remain visible. Test portrait and landscape modes.

Coin metal types need textual labels. Reduced-motion mode should preserve reveal generations and collection order. Keyboard focus must reach help, paytable and history.

After interruption, compare tier, Divine map, reveal stage, counter, balance and round identifier with server history.

Support-ready evidence

For cascade disputes, provide winning types and every removed coordinate. For Divine Squares, provide creation generation and persistence history.

For settlement, attach coin values, Zap recipients, ordered Vessels and repeat reveals. 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 Divine Squares can feel like stored value, but they exist only inside the active bonus and do not make a Hand or high coin due.

Set stake, spending and time limits before play. Do not increase stakes to chase the highest tier or 10,000× cap.

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

Publication checklist

• Remove every regular symbol matching a winning cluster type.
• Mark positions behind winning symbols as Divine Squares.
• Activate the Hand only after current wins finish.
• Reveal Coins and objects before applying Zap.
• Apply Zap only to adjacent eligible values.
• Activate Vessels top-to-bottom and left-to-right.
• Preserve repeat reveal generations.
• Apply the correct mark persistence for each bonus tier.
• Verify the deployed retrigger schedule.
• Verify RTP, stakes and New Zealand access from primary evidence.

Editorial assessment

Ze Zeus is governed by two ordered systems: Super Cascades create the Divine map, then the Hand resolves Coins, Zaps and Vessels in stages. Bonus tiers change how long the map survives and whether the Hand is guaranteed.

A rigorous review preserves those stages and reports 10,000× only as a cap. Missing RTP, stakes and local availability remain unclaimed until verified live.

Overlapping cluster types

One cascade state can contain several winning clusters, including more than one cluster of the same symbol type. Build a unique type list first, then remove every visible regular symbol belonging to those types once.

This prevents duplicate removal of a coordinate and ensures that matching copies outside all original clusters still disappear. Record every cleared position and every Divine Square created behind an actually winning symbol.

A non-winning copy is removed by Super Cascades but does not automatically create a Divine Square unless the live rule marks that position through a win.

Existing marks under new wins

A later winning symbol can occupy a position already marked Divine. Keep the coordinate once in the persistent map and add the later win to its history. Do not count two physical squares in one cell.

In the lower bonus tier, determine whether activation clears that mark from the next state. In higher tiers, preserve it according to the published persistence rule.

This distinction separates mark creation count from the number of unique marked positions available to the Hand.

Several Zaps in one generation

When more than one Zap appears, record each coordinate, factor and adjacency mask. If their target sets overlap, apply operations in the order shown by the game and carry the updated value into the next Zap.

Do not combine Zap factors into one number before identifying recipients. A Coin touched by two Zaps can evolve differently from a nearby Coin touched by one.

After all Zaps resolve, freeze the values before Vessel activation begins.

Vessel-to-Vessel collection

Because a Vessel can collect other Vessels, top-to-bottom and left-to-right order is essential. Give every Vessel an ID and store its opening value. When an earlier Vessel collects a later one, mark the recipient state exactly as shown by the game.

Do not allow a consumed value to reappear in a subsequent collector unless the live rules explicitly retain it. The ledger should show where every Coin and Vessel value ends.

This accounting prevents the same nested amount from being included twice in the final total.

Worked two-generation example

Generation one reveals Coins, a Zap and one Vessel. The Zap modifies adjacent values, then the Vessel collects under the published order. Another marked square reveals after that settlement, starting generation two with a new object set.

The reviewer does not apply the generation-two Zap retroactively to Coins already consumed in generation one. Each board state is closed before the next reveal.

This example explains sequencing without assigning invented amounts or probabilities.

Version comparison protocol

Attach every test to operator, build, currency and date. Compare cluster removal, Divine creation, Hand timing, Zap adjacency, Vessel order, tier persistence, coin pool and retriggers individually.

Archive one multi-cluster cascade, one overlapping-Zap reveal and one nested-Vessel sequence with the corresponding help. These reference rounds distinguish a genuine update from shortened animation.

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

Practical reader decision points

Before play, verify live RTP, complete stake, cap, country eligibility and responsible-play controls. During a spin, ask which types won, which cells became Divine and whether the Hand activation boundary was reached.

During reveal, track generation, Coins, Zap-adjusted values and Vessel order. During a bonus, add tier and mark persistence. These fields reconstruct settlement without suggesting a Hand or Gold Coin is due.

After feature end, clear the Divine map and apply the pre-set session boundary. Persistent marks are temporary feature state, not account balance.

Arithmetic review template

Write a disputed settlement in chronological blocks: cluster awards; full matching-type removal; Divine-map update; raw Coin and object reveals; Zap operations by adjacency; Vessel collections in grid order; later reveal generations; final bet application.

Compare every block with server history and the 10,000× cap. Do not move a later Zap ahead of an earlier Vessel or apply one Coin value in two generations.

RTP remains outside this round calculation because it is a long-run theoretical field rather than the result of one Divine board.

Final verification note

Before revision, reproduce the six-by-five grid, full-type Super Cascade removal, three tier triggers, Hand guarantee and Bronze removal in current official help. Confirm the current retrigger schedule rather than copying it from a related Hacksaw title.

Any field that cannot be reproduced should retain its source date and be labelled configuration-specific, not presented as verified availability or terms for New Zealand players.

A retrigger can change both duration and map rules

The current publisher page gives an additional-spin schedule for the first two bonus levels. In What If Zeus Was One of Us?, two simultaneous FS symbols add two spins and three add four. Four simultaneous FS symbols instead upgrade the active feature to Ze Zeus Take the Wheel and add four spins. In Take the Wheel, two FS symbols add two and three add four. The Superstar paragraph does not publish an equivalent additional-spin schedule. That omission is not evidence that it inherits the same table or cannot retrigger.

An upgrade is therefore not simply a longer stay in the original mode. Future map handling changes from marks waiting for Hand activation to marks surviving that activation. A four-FS upgrade is not the same as a five-FS base-game entry into Superstar: neither a guaranteed Hand on every spin nor removal of Bronze Coins follows from reaching Take the Wheel.

Worked countdown with a lower-tier upgrade

Use an invented state with two scheduled spins remaining in the lowest tier. This is an arithmetic illustration, not an initial-spin award, recorded play session or estimate of likely outcomes. Assume the next primary spin contains four simultaneous FS symbols and the active history applies the published upgrade. Consuming that scheduled spin leaves one; the four-spin award leaves five, now in Take the Wheel.

Hypothetical event	Counter before	Scheduled spin used	Spins added	Counter after	Active mode after event
Four FS in the lowest tier	2	1	4	5	Take the Wheel
Two FS on its next spin	5	1	2	6	Take the Wheel
Three FS on the following spin	6	1	4	9	Take the Wheel
No additional-spin event next	9	1	0	8	Take the Wheel

These four completed primary spins consume four scheduled entries and add ten: 2 − 4 + 10 = 8. Cascade drops, Coin reveals and ordered Vessel activations inside those spins do not each consume another scheduled entry. Likewise, the first four-FS event awards four extra spins once; it does not award four for the symbol count and a second four for the upgrade. The ending counter would incorrectly become nine at that first event if the consumed spin were forgotten.

Preserve the upgrade boundary without inventing precedence

For that first row, retain two map snapshots: one immediately before the upgrading event and one when Take the Wheel becomes active. Keep coordinate identities stable so a previously marked cell and the same cell after upgrade are not counted as two physical squares. The public description establishes the new mode’s persistence, but does not fully specify every ordering detail when a Hand activation and upgrade share one primary spin. Use the actual history to settle that boundary rather than assuming the upgrade retroactively changes an already completed reveal.

On later Take the Wheel spins, a Hand activation no longer means clearing the persistent map. Counter, mode and map are three separate fields: a counter increase does not create Divine Squares, and a retained square is not an extra spin or money already credited. This makes the worksheet useful for a duration or persistence dispute without predicting a bonus payout.

Frequently asked questions

What creates Divine Squares? Winning symbol positions after a cluster win.

When does the Hand activate them? After all current wins finish.

What resolves before a Vessel? Coin reveals and Zap effects.

Which bonus guarantees a Hand? Ze Zeus Might Superstar.

Is RTP published in readable form? No.

Is New Zealand availability confirmed? No.

Official source

• Hacksaw Gaming: Ze Zeus

Bottom line: read each reveal as Coins, Zaps and Vessels—not as one simultaneous event.

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.