Wings of Horus — Sun and Moon Orbs transform symbol groups

Wings of Horus by Hacksaw Gaming uses Wild substitution, Orb-driven symbol replacement and two related Free Spins modes. The progression bar behaves similarly in both bonuses, but the starting level differs.

Moon and Sun Orbs

The Moon Orb selects all instances of one random symbol. It replaces the selected positions and itself with a higher-paying symbol or Wild. The Sun Orb performs the same operation with two random symbol types. Because the selection happens by symbol type, the number of replaced positions can vary with the visible board.

Sacred Scripture

The low-paying symbols can spell HORUS horizontally. The provider says this Sacred Scripture result awards 500× the current bet. Treat it as a published feature rule, not an expected outcome or a statement about the game’s overall return.

Revenge Pharaoh Free Spins

At least three Free Spins scatters start ten spins. A gold progression bar rises with every new win. Filling it increases the purple Orb bar by one level and resets the gold bar. On the final drop, Moon or Sun Orbs appear according to the purple level, up to five. The purple bar begins at level one. Two additional scatters add two spins; three add four.

Rise Falcon Free Spins

At least four scatters also start ten spins and use the same progression and retrigger rules, but the purple Orb bar starts at level two. That starting state is the practical distinction to record before comparing the two modes.

Evidence limits

The official page documents these mechanics but does not expose readable RTP, stakes or New Zealand casino availability. The exact deployed paytable and version must be checked in-game.

Orb type determines the selection width

Moon and Sun Orbs share a transformation pattern but select different numbers of symbol types. Moon chooses one random type; Sun chooses two. The game then finds every visible instance of the chosen type or types, replaces those positions and the Orb itself with a higher-paying symbol or Wild, and settles the resulting board.

The number of transformed cells is therefore board-dependent. One selected type may appear twice on one result and many times on another. The source does not promise a fixed number of replacements.

Record the Orb identity before animation, the selected symbol names and every original coordinate. A final grid without that pre-state cannot prove which cells were transformed.

Auditing a Moon Orb

Save the stopped grid containing Moon and label its coordinate. When the game reveals the selected symbol type, mark all matching instances across the board. No second type should be added to the selection merely because another symbol animates.

Capture the replacement identity and the final grid. Verify that all selected positions and the Moon coordinate now contain the higher-paying symbol or Wild described by the event. Positions of other types remain outside this transformation unless another feature changes them.

The word “random” applies to the selected type. The article should not claim that a player can influence it through timing, stake or screen interaction.

Auditing a Sun Orb

Sun selects two random symbol types. Record both names separately, then combine their visible coordinates into one transformation mask. The Sun coordinate also belongs to the replacement event.

If the two types occur in different quantities, the total transformed-cell count will reflect the board. Do not advertise Sun as exactly double Moon; selecting two types can yield many different position counts.

After replacement, reconcile the final board through the deployed paytable. The provider overview does not publish selection probabilities or a fixed upgrade value.

Higher-paying symbol or Wild

The official wording permits two result classes: conversion to a higher-paying symbol or to Wild. Preserve the exact revealed identity. Do not automatically call every Orb result Wild.

“Higher-paying” requires the live paytable to verify rank. Record the original selected type, replacement and relevant symbol values. If two selected types have different starting values, the final replacement still needs to be read from the settled event rather than inferred.

A converted cell has no standalone prize. It matters through valid winning combinations on the resulting grid.

Worked Moon example

Suppose Moon selects a low symbol visible at four coordinates. The audit stores those four cells plus the Moon cell, records the revealed replacement and compares the five-position mask with the settled grid.

The resulting combinations are evaluated under the live paytable and matched to round history. The example does not assign an invented stake, prize or selection probability.

If another low symbol remains unchanged, that is consistent with Moon’s one-type rule.

Worked Sun example

Suppose Sun selects two symbol types with three and five visible instances. The pre-state mask contains eight matching cells plus the Sun coordinate. After the reveal, all nine feature positions show the documented replacement.

The reviewer then traces valid awards. The count of nine is specific to this illustrative board and is not presented as a standard Sun outcome.

Any cell outside the two selected types requires a separate rule before it can be included.

Sacred Scripture is a pattern rule

The low-paying symbols can spell HORUS horizontally. The provider publishes an award of 500× the current bet for this Sacred Scripture result. Verify the horizontal sequence on the stopped grid and record which cells supply H, O, R, U and S.

Do not treat a vertical, diagonal or scrambled set of letters as the published pattern unless the deployed paytable expands the rule. A partially completed word has no stated proportional award.

The 500× figure is a specific feature award, not the game’s RTP, average return or guaranteed session result.

Verifying the current-bet basis

Record the complete round stake before the spin and confirm how the live help defines “bet.” Apply the 500× rule to that documented unit when reconciling Sacred Scripture.

Do not multiply a line bet, coin value and total bet together unless the paytable explicitly requires that calculation. The account history should show the credited result under the operator’s denomination.

If the game applies an overall cap, preserve the cap rule separately. The provider page’s Sacred Scripture value does not by itself establish the maximum exposure across all features.

Revenge Pharaoh entry state

At least three Free Spins scatters trigger Revenge Pharaoh with ten spins. Save the trigger grid, scatter count, initial counter and purple Orb bar at level one.

The gold progression bar rises with every new win. Record its value before and after each qualifying result. When it fills, the purple bar increases one level and the gold bar resets.

Keep counter, gold progress and purple level in separate fields. They represent duration, current-level progress and final-drop Orb quantity.

What counts as a new win

Use the game’s credited result and progression animation to identify a new win. Several payline highlights on one stopped board may belong to one result rather than multiple progression events.

Record the gold-bar change after settlement, not during reel motion. If the bar does not move after a credited result, preserve the round identifier and live rule for support review.

The public description does not supply the number of wins required to fill each level. Transcribe the deployed meter instead of inventing thresholds.

Purple level and the final drop

On the final drop, Moon or Sun Orbs appear according to the purple level, up to five. Record the level before the final spin, the number and type of Orbs that actually appear and every transformation in order.

“Up to five” is a ceiling, not a promise that every bonus ends with five Orbs. Revenge Pharaoh starts at purple level one, and progression during the feature determines later state.

If several Orbs transform overlapping symbol groups, use the server event order. A cell changed by the first Orb may affect the board seen by the next.

Rise Falcon entry state

At least four scatters trigger Rise Falcon with ten spins. The progression and retrigger rules match Revenge Pharaoh, but the purple Orb bar starts at level two.

Record the four-scatter trigger and initial level before the first feature spin. This one-level head start is the verified structural difference; do not invent a different gold-bar threshold or Orb table.

Keep the mode name in every ledger row so screenshots from the two ten-spin bonuses are not mixed.

Comparing the two bonuses

Both modes begin with ten spins, advance the gold bar on new wins, raise the purple level when gold fills, reset gold after a level increase and use the final drop for Orbs. Both allow two extra scatters to add two spins and three to add four.

Revenge Pharaoh begins at purple level one after at least three trigger scatters. Rise Falcon begins at level two after at least four. A comparison table needs no invented claims beyond those fields.

The higher starting level does not prove a particular payout or expected value without mathematics for Orb distributions and feature frequency.

Scatter extensions

During either bonus, record every additional scatter on the stopped grid. Two add two spins and three add four. Save the counter before the result, the scatter count and the counter after settlement.

The public rule does not state an award for one extra scatter. Do not extrapolate a six-spin award for four scatters unless the live help publishes it.

Keep these duration extensions separate from purple-level progression. A scatter event changes the counter; a new win changes the gold bar.

A Revenge Pharaoh example

A verified three-scatter trigger opens ten spins at purple level one. Several credited results advance the gold bar. When it fills, purple moves to level two and gold resets. The final drop then uses the achieved purple level to determine the Orb state shown by the game.

The ledger stores each progression event and final transformations. It does not assume five Orbs or a particular award.

If two extra scatters appear during the feature, the counter increases by two in a separate event row.

A Rise Falcon example

A four-scatter trigger opens ten spins with purple already at level two. The same gold-bar method is followed. If no level increase occurs, the final drop still begins from the documented level-two state.

This illustrates the practical value of recording the starting bar. A screenshot of the final drop alone cannot show whether the level came from the mode’s head start or from wins earned during the bonus.

Again, actual Orb types and settlement come from the tested round.

Sequential Orb transformations

When several Orbs appear, create one event row per Orb. Store the board before selection, Orb type, selected symbol type or types, replacement identity and board after conversion.

The output of one event becomes the input of the next if the game resolves sequentially. Do not apply every Orb to the original grid unless the live history proves simultaneous resolution.

After the last transformation, evaluate the final winning combinations and reconcile the feature total.

Two sequential Moon events can transform seven unique positions, not eleven

Here is an invented transformation trace that tests event bookkeeping rather than game probability. Label three ordinary A positions a1, a2, a3, two B positions b1, b2, and two Moon positions m1, m2. These seven labels represent a hypothetical subset of the grid, not a published layout. Assume the active paytable permits B as the first higher-paying replacement and both displayed Orb events actually select the stated types.

First, Moon m1 selects A. The transformation mask contains the three A positions plus m1 itself, so four positions become B. The two original B positions remain B. Before the second event, the board therefore contains six B positions: the original two plus the four created by the first transformation.

Next, Moon m2 selects B from this updated state. Its mask contains all six current B positions plus m2, making seven positions. Suppose this second reveal replaces them with Wild. That outcome is hypothetical; neither a guaranteed Wild result nor a claim that the second Orb always selects the first replacement is intended.

Event snapshot	Selected ordinary type	Transformation set	Set size
Before Moon m1 acts	A	{a1, a2, a3, m1}	4
Before Moon m2 acts	B, now present in six positions	{a1, a2, a3, m1, b1, b2, m2}	7
Union of affected coordinates	Not another event	Seven distinct positions	7

Adding the two mask sizes gives eleven event-position references, not eleven distinct cells. The first four coordinates occur in both masks because their contents changed again. Assigning a new physical cell whenever its symbol changes would corrupt the grid size and any subsequent winning-combination reconstruction.

Applying the second Moon only to the original two B positions would also be wrong for this assumed sequential history. It would ignore the four new B instances created by m1. The input board for event two is the output board from event one. If an actual client instead documents simultaneous selection against one pre-state, its record needs that different timing; this example does not decide undocumented precedence between several visible Orbs.

Separate a position’s identity from its changing symbol

Retain each coordinate identifier through every transformation, with separate before-symbol and after-symbol fields. In the example, a1 is A initially, B after m1, then Wild after m2. That is one location with three states, not three locations or three independent awards.

Neither the four-position first mask nor the seven-position second mask establishes a payout. Evaluate the settled grid through the active paytable and retain the actual server credit. A transformation can change eligible combinations, but its cell count is not a multiplier or cash amount by itself.

This also separates Orb quantity from replacement quantity. Two Moon events can touch seven unique positions in this worksheet; it does not prove Sun always touches fourteen or that a five-Orb final drop guarantees a certain grid. Symbol populations and prior transformations determine each mask. Archive those populations before interpreting the bonus’s final purple level as a monetary result.

Paytable and settlement requirements

Obtain the grid structure, evaluation method, symbol ranks, Wild substitution and cap from the deployed help. These are required to verify “higher-paying,” Sacred Scripture and the final transformed board.

For every award, identify the participating cells and any Orb-created symbols. Keep base awards, feature multipliers or fixed Sacred Scripture credit in the order shown by the game.

Do not reverse-engineer RTP from a small collection of feature rounds.

RTP, stakes and numerical limits

The accessible official page does not expose readable RTP, minimum or maximum stake, default denomination, volatility or overall maximum exposure. Collect them from the exact live information panel with provider, operator, version, currency and date.

If multiple RTP versions exist, publish only the tested configuration. Do not combine stakes from one operator with mathematics from another.

The 500× Sacred Scripture award and five-Orb ceiling are feature rules, not substitutes for missing RTP or a complete maximum-win specification.

New Zealand availability

Hacksaw Gaming’s global page does not prove real-money availability in New Zealand. Verify operator country terms, registration eligibility, authenticated catalogue and successful game launch.

NZD stakes, payments, verification and withdrawals are operator facts. Source them separately and date the check.

A demo or portfolio page is not enough. Do not recommend bypassing location restrictions.

Mobile and accessibility checks

On mobile, the full horizontal HORUS pattern, Orb selections, gold bar, purple level and remaining-spin counter must remain visible. Test portrait and landscape orientations and ensure controls do not crop the edges.

Moon and Sun need labels beyond colour or glow. Selected symbol types and replacement identity should be communicated after reduced animation. Keyboard focus must reach help, paytable and history.

After interruption, compare mode, progress bars, counter, pending Orb event, balance and round identifier with server history.

Support-ready record

For an Orb dispute, include the pre-state grid, Orb type, selected symbol names, transformation mask, replacement and settlement. For progression, include every new-win event and both bars before and after.

For Sacred Scripture, provide the complete horizontal word, current bet definition and credited amount. For retriggers, provide scatter coordinates and counter transition.

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

Session controls

Progress bars can make an unfinished level feel like stored value. That state exists only inside the active bonus and does not justify extending paid play to reach another feature.

Set stake, spending and time limits before play. Do not increase stakes because a previous final drop showed fewer Orbs than hoped.

Mechanical understanding improves settlement review, not prediction. Use responsible-play tools and stop at the chosen boundary.

Publication checklist

• Treat Moon as a one-symbol-type selector.
• Treat Sun as a two-symbol-type selector.
• Include the Orb cell in each transformation mask.
• Verify the replacement as higher-paying or Wild through the paytable.
• Require horizontal HORUS for the published 500× rule.
• Start Revenge Pharaoh at purple level one.
• Start Rise Falcon at purple level two.
• Increase purple only after the gold bar fills and resets.
• Record two-scatter and three-scatter counter additions separately.
• Verify RTP, stakes and New Zealand access from the live deployment.

Editorial assessment

Wings of Horus combines a board-level transformation with a clearly staged bonus meter. Moon changes every instance of one selected type; Sun changes two types; Sacred Scripture has its own horizontal 500× condition. Those mechanics need separate evidence.

The bonuses reuse the same progression but begin one purple level apart. A rigorous review records each new win, gold reset, purple increase, scatter extension and final Orb sequence while leaving missing numerical configuration and local access unclaimed until primary live evidence is available.

Frequently asked questions

What does a Moon Orb select? All instances of one random symbol type.

What does a Sun Orb select? All instances of two random symbol types.

What is Sacred Scripture? A horizontal HORUS pattern from low symbols, published as 500× bet.

What triggers Revenge Pharaoh? At least three Free Spins scatters.

What triggers Rise Falcon? At least four Free Spins scatters.

How do the bonus modes differ initially? The purple Orb bar starts at level one in Revenge Pharaoh and level two in Rise Falcon.

Is New Zealand availability confirmed? No.

Official source

• Hacksaw Gaming: Wings of Horus

Bottom line: note the Orb type, selected symbol groups and purple starting level before interpreting the transformation sequence.

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.