Rise of Ymir — sticky giants feed one global multiplier

Rise of Ymir by Hacksaw Gaming uses five reels, four rows and paylines. The provider publishes a maximum win cap of 15,000× bet across all modes; that is a technical ceiling, not an expected return.

Ymir’s Conquest

A Ymir symbol is a substituting Wild multiplier. When several Ymirs participate in one winning combination, their displayed values are added before being applied. A landed Ymir sticks and starts a free respin after wins are evaluated. New Ymirs continue the sequence; it ends when no new Ymir appears.

Four sticky Ymirs on one reel merge into a Giant Ymir covering that reel. Their four values are added and used by every qualifying win containing the Giant.

Megamultiplier

If a Megamultiplier symbol lands while Ymir symbols are present, their values combine into one global multiplier for all wins while active. It also awards a respin, and new Ymirs during later respins add their values. In the base sequence it is removed at the beginning of the next round.

Three bonus routes

Dawn of Gods starts with ten Free Spins from three scatters and increases the chance of Ymirs with stronger values. Fury of Ymir starts from four scatters, also with ten spins, but keeps an activated Megamultiplier between spins until the bonus ends. Both award two extra spins for two additional scatters and four for three.

Five scatters start Fall of Ymir with three refilling lives. Volcanic Ymirs stick; Megamultiplier values can be consumed by green Orbs on one reel or golden Orbs across the whole grid. At the end, all remaining Volcanic Ymir values are added and multiplied by the bet.

Evidence limits

The source confirms the feature rules and 15,000× cap but does not expose readable RTP, stakes or New Zealand casino availability.

Three values must be kept apart

Rise of Ymir uses individual sticky Ymir multipliers, Giant Ymir reel values and a Megamultiplier that can operate globally. They are related, but they are not interchangeable. A final screenshot containing one large number cannot show how that number was built or where it applies.

Create separate ledgers for grid positions, merged reel values and the active global multiplier. Every event should state which ledger changes. This prevents a sticky value from being counted once in a Giant and again as though it remained independent.

The provider cap of 15,000× bet applies across modes. It is a ceiling, not evidence that a particular combination or bonus is likely to reach it.

Landing a Ymir

A Ymir is a substituting Wild multiplier. Record its reel, row and displayed value on the stopped grid. If it participates in a winning combination, include its value under the feature’s additive rule.

The landed Ymir becomes sticky and starts a free respin after wins are evaluated. Store the settlement before advancing to the respin state. Confirm that no new stake is deducted for this feature step.

Assign stable IDs such as Y1 and Y2. Sticky coordinates should be copied forward until the active sequence ends or a documented merge consumes them.

Adding Ymir values in one win

When several Ymirs participate in the same winning combination, add their displayed values. Participating 3× and 5× Ymirs create an 8× combined feature multiplier, not 15×. Both illustrative starting values belong to the supplier’s published set.

Only Ymirs on the evaluated route belong in the sum. A sticky Ymir elsewhere on the grid is excluded from that award even though it remains visible.

List the base win, participating IDs, additive total and credited result separately. This makes the settlement reproducible.

Respin continuation

New Ymirs continue the free-respin sequence. Record the sticky set before each respin and mark only symbols that genuinely land for the first time. Existing sticky Ymirs do not satisfy the “new Ymir” condition by themselves.

The ordinary Ymir’s Conquest continuation ends when no new Ymir appears. A separately activated Megamultiplier also awards a respin, so do not use that condition to cancel its documented award. Save the actual terminal grid and credit before clearing the base-feature map.

Do not describe the chain as unlimited. It is conditional on new arrivals and subject to the live game’s grid and cap.

Forming a Giant Ymir

Four sticky Ymirs on one reel merge into a Giant Ymir covering that reel. Preserve the four source IDs and values, then record their additive total as the Giant’s reel value.

After merging, the individual values have been consolidated. Do not add them again alongside the Giant for the same winning combination. The Giant’s displayed value represents their combined state.

Every qualifying win containing the Giant uses that reel value under the provider description. Trace participation through the deployed paylines.

Worked Giant example

Suppose four sticky Ymirs on reel three display 2×, 4×, 5× and 10×. Their merger creates a Giant with a 21× value. The source cells are consolidated in the individual ledger, and the reel ledger receives G3=21×. These illustrative inputs use published possible starting values.

A later win crossing reel three can use G3 under the paytable. A win that does not include the Giant reel cannot claim the 21× solely because it is visible.

These illustrative values explain addition and consumption; they are not promised outcomes.

Activating Megamultiplier

When a Megamultiplier lands while Ymirs are present, their values combine into one global multiplier for all wins while active. Record each incorporated value and the board after activation. Combining numbers into a global total does not itself prove that the underlying sticky symbols are erased.

The Megamultiplier awards a respin. New Ymirs landing on later respins add their values to the active global number. Keep an event history rather than overwriting the total.

In the base sequence, the global multiplier is removed at the beginning of the next round. Record that reset explicitly so it is not carried into unrelated play.

Global does not mean permanent

“Global” describes which wins the multiplier affects while it is active. It does not mean that the value survives every mode, session or paid round. The base reset boundary remains important.

For each active result, record base awards first and then apply the global value in the order specified by the live help. If an additional Ymir arrives, capture whether its value changes the current or next settlement.

Do not combine a Giant value and its already-consolidated source Ymirs again when building the global total. Count each represented grid value once at collection, without inferring that ordinary Megamultiplier activation removes every sticky symbol.

Dawn of Gods

Three scatters start Dawn of Gods with ten Free Spins. The provider states that Ymirs appear with increased chance and stronger values, but it does not quantify either change on the accessible page.

Save the trigger grid, initial counter and every Ymir value. Apply the ordinary sticky, merge and additive rules unless the deployed help states an exception.

Two extra scatters add two spins and three add four. Record the counter transition on the exact bonus spin.

Fury of Ymir

Four scatters start Fury of Ymir with ten spins. Its defining rule is that an activated Megamultiplier remains between spins until the bonus ends.

Open a persistent global ledger at activation. Copy its value into each later spin and add new qualifying Ymir values as documented. Clear the total at bonus completion.

The same two-scatter and three-scatter extensions apply. Keep duration changes separate from global-value growth.

Comparing Dawn and Fury

Both modes begin with ten spins and use the same published scatter extensions. Dawn emphasizes increased Ymir opportunity and values. Fury adds cross-spin persistence for the Megamultiplier.

Do not assume that Dawn’s Megamultiplier persists because Fury’s does. Mode identity controls the reset boundary.

Nor does Fury guarantee immediate Megamultiplier activation. The source describes what happens when it activates; the observed round must provide the event.

Fall of Ymir entry

Five scatters start Fall of Ymir with three refilling lives. Record the trigger grid, starting lives and every Volcanic Ymir position and value.

This mode uses a collection-style board rather than a ten-spin counter. Track lives before and after each event and identify the exact condition that refills them from the live help.

At termination, all remaining Volcanic Ymir values are added and multiplied by the bet, subject to the published cap.

Green Orb consumption

In Fall of Ymir, a Green Orb adds the collected global value to every Volcanic Ymir on the Orb’s reel. Record the global value, reel, recipients and resulting grid. The reel limits the recipients; it does not turn the global ledger into a separate reel-local balance.

Do not apply a Green Orb across the whole grid or split the global value among its recipients. Each eligible Volcanic Ymir on that reel receives the addition. If none exists there, the supplier says nothing happens; do not invent recipient positions or an unresolved empty-reel consumption sequence.

When the global value is consumed through the documented Orb addition, it resets to zero and is removed. The updated Volcanic values remain on the board. A later Megamultiplier can collect the current board again; a reset global ledger does not mean those symbols became zero.

Golden Orb consumption

A Golden Orb adds the collected global value to every Volcanic Ymir across the whole grid, then that consumed global value resets to zero and is removed. Capture each recipient’s before-and-after value. Its grid-wide recipient set distinguishes Golden from Green.

Use chronological events when several Orbs appear. The first consumption changes the state available to the next.

After distribution, reconcile the global ledger with the grid. A number should not be counted in both places without an explicit rule.

Fall of Ymir settlement

At feature end, list every remaining Volcanic Ymir value and calculate their additive total. Multiply that total by the documented complete bet unit and compare it with the feature award.

If the 15,000× cap truncates a higher calculated value, record the uncapped calculation and applied ceiling separately. Do not present the cap as the expected return.

Reconcile the credited amount with account history and preserve the round identifier.

Worked Megamultiplier example

Suppose sticky Ymirs Y1=2×, Y2=5× and Y3=10× are present when Megamultiplier lands. The global ledger begins at 17×. A new 4× Ymir on the awarded respin increases it to 21× under the described additive rule. These hypothetical starting values belong to the published set.

The audit marks the source values as combined and applies the active global number to qualifying wins according to the live help. It does not multiply 2×5×10 or infer that collection erased the sticky symbols.

Actual values and timing come from the tested round; this example only shows the ledger.

Paytable and bet definition

Obtain paylines, symbol values, Wild substitutions, operation order and complete-bet definition from the deployed help. These fields are required to verify individual, Giant and global multiplier settlements.

Record title, provider, version, operator, currency and date. If multiple configurations exist, do not mix them.

The accessible provider page supports the 15,000× cap but not readable RTP or stakes.

New Zealand availability

The global provider page does not confirm real-money availability in New Zealand. Verify country terms, registration eligibility, authenticated catalogue and successful launch at the operator.

NZD support, deposits, withdrawals and verification are operator facts. Source them separately and date the check.

A demo or portfolio entry is insufficient. Do not advise bypassing location controls.

Mobile and accessibility checks

On mobile, all four rows, sticky values, Giant reel, global total, Orb targets and lives or spin counter must remain visible. Test portrait and landscape modes.

Individual, Giant and global values need labels beyond colour. Reduced-motion mode should preserve merge and consumption order. Keyboard focus must reach help, paytable and history.

After interruption, compare mode, sticky IDs, Giant values, global ledger, lives or counter, balance and round identifier with server history.

Support-ready evidence

For a merge dispute, provide the four source Ymirs and resulting Giant. For a global dispute, provide every incorporated value and later addition. For Orb issues, include the recipient set, copied additions and consumed global value, distinguishing global reset from retained grid symbols.

Add operator, title, version, timestamp, stake, currency, balances and round identifier. State the exact transition that failed.

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

Session controls

Sticky multipliers and persistent global totals can make an active feature feel like stored account value. They exist only under the mode’s reset rules and do not make a future paid spin due to continue.

Set stake, spending and time limits before play. Do not raise stakes to chase a Giant, Orb or 15,000× cap.

Feature knowledge improves accounting, not prediction. Use responsible-play tools and stop at the chosen boundary.

Publication checklist

• Add values from participating Ymirs; do not multiply them.
• Keep new-Ymir Conquest continuation separate from the respin awarded by Megamultiplier activation.
• Merge four sticky Ymirs on one reel into one Giant value.
• Do not double-count Giant source values.
• Keep grid, reel and global ledgers separate.
• Reset the base Megamultiplier at the next-round boundary.
• Preserve it across Fury of Ymir once activated.
• Distinguish green one-reel and golden whole-grid Orb scope.
• Settle Fall of Ymir from remaining Volcanic values.
• Verify RTP, stakes and New Zealand access through live evidence.

Editorial assessment

Rise of Ymir is an accounting game as much as a visual one. Individual sticky values can merge by reel, then combine into a global modifier, and Orbs can move that modifier back onto the board in Fall of Ymir. Every transition must consume, preserve or reset a value exactly once.

The three bonuses change persistence and settlement boundaries rather than erasing the core rules. A rigorous review tracks those boundaries, reports the 15,000× cap as a ceiling and leaves RTP, stakes and local availability unclaimed until the deployed version supplies primary evidence.

Keep dates visible.

Version comparison protocol

When a later build is reviewed, retain the earlier ledger and create a separate configuration record. Compare the five-by-four grid, paylines, Ymir value range, respin continuation, Giant merger, Megamultiplier reset and each bonus trigger field by field. A different RTP or stake range does not prove that the feature sequence changed.

Save one complete base respin, one Giant merger, one persistent Fury global state and one Fall of Ymir Orb event with the corresponding help screen. These reference cases make later changes traceable and reveal when an apparent difference comes only from an animation redesign.

If two primary sources conflict, publish both with dates and request clarification. Do not choose the larger value, combine rules from two builds or silently rewrite the old evidence.

Practical reader decision points

Before a paid round, a reader needs the live RTP, full stake range, complete-bet definition, local eligibility and available responsible-play controls. None is supplied by the feature artwork. They must be checked in the deployed client and operator terms.

During a feature, the useful questions are narrower: which Ymir values remain independent, which have merged, whether the global value is active, and whether an Orb consumed it. A ledger that answers those questions is more informative than a claim that the board “looks strong.”

After settlement, verify each credited award once in its correct scope and against the cap. An active global multiplier can apply to several wins; it is not a one-use coupon. At the documented feature reset, clear its state and apply the session boundary without carrying a completed ledger into unrelated rounds.

Fall of Ymir: copying a total is not dividing it

For this hypothetical reconstruction, assume three Volcanic Ymirs remain on the board: A=3 and B=5 on reel 2, and C=2 on reel 4. All three initial values are permitted by the supplier’s published starting set. Use completed, separate feature spins for the following events, so no unverified same-spin priority is required.

First, an actual Megamultiplier event in the example collects 3 + 5 + 2 = 10 into the global ledger. The Volcanic grid retains 3, 5 and 2. Collection has not paid ten base bets into the account or removed those three symbols. They are current feature states awaiting later effects and final settlement.

Next, a Green Orb on reel 2 consumes that global 10. A becomes 3 + 10 = 13 and B becomes 5 + 10 = 15. C remains 2 because it is on another reel. The grid sum is now 30, and the consumed global ledger is zero. Two recipients each receive ten; dividing ten into five per recipient would give the wrong board total of 20.

Completed event	A, reel 2	B, reel 2	C, reel 4	Global after event
Initial state	3	5	2	0
Megamultiplier collects current grid	3	5	2	10
Green Orb adds 10 to reel-2 recipients	13	15	2	0
Later Megamultiplier collects current grid	13	15	2	30
Golden Orb adds 30 to all three recipients	43	45	32	0

The later collection uses the updated 13 + 15 + 2 = 30, not the original ten. The Golden Orb then adds thirty to each of the three Volcanic symbols. Their closing sum is 43 + 45 + 32 = 120. The total rises by 3 × 30 = 90 because the addition has three recipients. It is neither 30 + 30 = 60 nor an equal three-way division of thirty.

Values such as 13 and 43 here are results of Orb additions, not invented possible initial landing multipliers. A symbol’s starting-value set and its later modified value are different fields. The example also does not claim that these events are frequent or that a player can choose their order.

If the feature then ends with exactly those three remaining values and no other state changes, the conditional settlement is 120 base bets. At an illustrative complete bet of 0.40 account-currency units, that is 48.00 units before any applicable limit. The consumed global thirty must not be added again as another terminal prize, and the intermediate grid total of thirty is not a separate account credit. Only the accepted final history establishes the actual award.

The lives ledger follows arrivals, not monetary growth

Fall starts with three lives. Each spin consumes one, and a non-dead symbol arrival restores the count to three. In the example, completed Megamultiplier and Orb spins can therefore restore duration while modifying different value ledgers. Two useful non-dead arrivals in one spin restore three lives; they do not bank six.

After the last such arrival, three dead-only spins give the counter sequence 3 → 2 → 1 → 0 and end the feature. A retained Volcanic symbol is not a newly landed refill event just because it remains visible. Conversely, the count is not driven by how much a global value increased. Record the actual arriving symbol and the lives transition separately from its monetary effect.

Frequently asked questions

How does a Giant Ymir form? Four sticky Ymir symbols on the same reel merge.

What starts Dawn of Gods? Three FS scatters.

What starts Fury of Ymir? Four FS scatters.

What starts Fall of Ymir? Five FS scatters.

What is the published maximum cap? 15,000× bet across all modes.

Is RTP published in readable form? No.

Is New Zealand availability confirmed? No.

Official source

• Hacksaw Gaming: Rise of Ymir

Bottom line: track sticky reel values, the temporary global multiplier and Orb consumption as three separate ledgers.

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.