Orb of Destiny by Hacksaw Gaming: multiplier-reel evidence

Orb of Destiny is a six-reel, four-row Hacksaw Gaming title with 14 paylines, a published 10,000x maximum win and 3/5 volatility. Lady Fortune expands across a reel, carries a queue of multipliers and can remain for respins; Orb symbols add more values to every Fortune reel.

The official page was checked on 8 October 2026. It does not display readable RTP or stake limits, and it does not verify New Zealand operator access.

Public settings

Field	Official page
Grid	6×4
Paylines	14
Maximum win	10,000× bet
Volatility	3/5
Lady Fortune starting queue	1–3 multipliers
Queue maximum	5 multipliers per reel
Free Spins	10
RTP	Not shown in readable page copy

The game is line based. An expanded reel substitutes for paying symbols only when it participates in a qualifying route.

Lady Fortune reel

When Lady Fortune lands, one to three multipliers appear at the bottom of her reel. Orbs can extend the queue up to five. If the reel completes a line, the bottom value multiplies that line.

When several Fortune reels participate, their bottom values are added before application. Record each reel’s queue and the exact lines it completes.

Queue consumption

After all current wins are calculated, the bottom multiplier is removed from every Lady Fortune reel, whether or not that reel joined a win. This global consumption rule is easy to miss.

If at least one reel still has values, a respin follows and surviving Fortune reels remain. Reels with empty queues disappear with the other symbols. Continue until every queue is empty.

Orb additions

An Orb reveals one, two or three and adds that many random multipliers to all Lady Fortune reels on the grid, subject to the five-value maximum. It expands queue length, not necessarily the numeric size of an existing value.

Capture the Orb reveal and every queue before and after addition. When several Orbs occur, follow live event order rather than summing assumptions.

Lady Luck Free Spins

Three FS Scatters trigger ten spins. In this mode, every Lady Fortune reel starts with at least two multipliers. Two further FS symbols add two spins; three add four.

The minimum describes queue length on a landing Fortune reel. It does not guarantee that one appears on every spin.

Future Fortunes Free Spins

Four FS Scatters trigger ten spins. Every Fortune reel starts with the maximum initial three multipliers. The same +2 and +4 retrigger schedule applies.

Three starting values are distinct from the five-value queue cap, because later Orbs can add entries.

Bonus-buy menu

Where permitted, Hacksaw lists BonusHunt at 3x bet, Fortune’s Favor at 50x, Lady Luck at 100x and Future Fortunes at 200x. These are conditional options, not globally available products.

Check the live confirmation, cost and any separate RTP profile. Do not infer NZ availability from the portfolio page.

RTP and stakes

The accessible studio copy does not provide readable RTP, minimum wager, maximum wager or currency. Record those fields from the actual help panel with operator, version and date.

If the number cannot be found, state “unavailable”. Never reuse an RTP from another mystical or Hacksaw title.

Max-win interpretation

The provider publishes a 10,000x maximum win. It is a cap, not a typical outcome. Verify the total-bet definition and what the live game does when the cap is reached.

Do not confuse the five-entry queue cap with a 5x factor. Queue length and multiplier value are different fields.

Worked queue audit

Suppose two Fortune reels participate with bottom values 3x and 10x. The rule adds them to 13x for that line. After calculation, both bottom values are removed, even if a third Fortune reel did not join any winning line.

Record the remaining queues. If any still contain values, the next respin keeps those reels locked. This example explains order only; live values control actual settlement.

Mobile checks

On mobile, all four rows, 14-line map, each queue, bottom value and respin state must remain readable. Rotate during demo and compare resumed queues with server history.

Colour alone should not distinguish queue positions. A textual help view is important for accessibility.

Evidence pack

Save title, version, RTP if shown, currency, total bet, balances and round ID. Capture every Fortune landing, queue, Orb reveal, winning route, consumed bottom value and respin.

For bonuses, add trigger grid, main counter and retriggers. The final wallet credit must reconcile with the sequence.

Common mistakes

Do not multiply several Fortune values; add participating bottom values. Do not preserve a consumed value because its reel did not win. Do not remove a reel while its queue still contains entries.

Avoid inventing RTP, promising buy availability or presenting the 10,000x cap as expected performance.

Responsible play

Queued multipliers are temporary round state, not stored value for future paid spins. Set time and loss limits before entry and stop at the chosen boundary.

Direct feature purchases can multiply exposure. Treat each as a separate wager and check the full cost.

Support questions

Ask for active RTP, stakes, line map, multi-Orb order and the treatment of queues when the maximum win is reached. Include screenshots and round IDs.

For territorial access, rely on operator terms. Do not circumvent restrictions.

Queue worksheet

Create one row for each Lady Fortune reel and write its multiplier queue from bottom to top. Add a column for whether it joined a winning line. After settlement, cross out the bottom entry on every Fortune reel, including non-participating ones, and preserve remaining entries for the respin.

When an Orb lands, record its revealed one-to-three count and append the displayed random values to every eligible queue without exceeding five. Do not invent values for a concealed animation. If the order cannot be seen, use the post-event queue from history.

For several winning lines, calculate each line with only the Fortune reels it uses. A reel visible elsewhere on the grid is not part of that combination. Reconcile line totals before queue consumption.

Bonus counter audit

In Lady Luck, verify the two-entry minimum for newly landed Fortune reels. In Future Fortunes, verify three initial entries. Keep the main ten-spin counter separate from queue-driven respins, then add two or four spins only when the required FS count settles.

At feature end, sum final child credits once. Do not add the feature summary to those same components. Clear every queue from the worksheet; no value carries to later paid play.

Version protocol

Compare line map, queue sizes, Orb additions, removal timing, triggers, retriggers, buys and cap on every update. Add RTP and stake fields only when a primary deployed source exposes them.

Keep one complete queue lifecycle as reference evidence. If a redesign changes the display but not server order, describe the presentation change separately from mechanics.

Reader decision points

Before play, confirm total wager, live RTP, bottom-to-top queue order and accessible history. If the multipliers cannot be distinguished without animation or colour, the round may be difficult to audit on a phone.

The queue can create suspense, but remaining values are confined to the current round. They do not make another trigger more likely and should never justify exceeding the session limit.

Accessibility and evidence quality

Each Fortune reel should expose its multiplier queue in a form that does not depend solely on colour or animation. On a small screen, zooming must not hide the total bet, respin state or lower queue entry. If only the bottom value is announced, capture the expanded help before the next action.

For support, describe the failure as a state transition: the queue before settlement, value consumed, queue expected afterwards and actual display. This is clearer than saying the orb “paid incorrectly”. Include UTC time, operator, build, parent round and child respin ID.

A future editor should also verify whether a Fortune reel outside all wins still loses its bottom value. That specific rule is central to the lifecycle and must remain visible if wording changes.

Record that result with a no-win participating-reel example whenever possible.

Short answers

How many lines? Fourteen.

How are two Fortune values combined? Added when both reels join the same win.

What does an Orb add? One to three random queue entries to all Fortune reels.

How long do respins continue? Until all Fortune queues are empty.

Is RTP published here? Not in readable copy.

Is NZ availability confirmed? No.

Final assessment

Orb of Destiny is a queue-management game. Every Fortune reel needs a chronological list; Orbs add entries, settlements consume the bottom, and remaining values drive respins. That ledger resolves most ambiguity.

The public page confirms mechanics, cap and volatility. Live help must supply RTP, stakes and local access.

Official and related sources

• Orb of Destiny official product page
• Responsible gambling guide
• Corrections policy

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.