Asgardians and Asgardians Dice: Free Games and Forge guide

Asgardians and Asgardians Dice are treated together because the planned search task covers the original family rather than creating duplicate URLs. Endorphina publishes the same headline configuration for both: five reels, three rows, 25 paylines, 96.07% RTP, low volatility and a €0.25–€200 stake reference.

Both official pages describe two distinct triggers. Three or more Rainbow Bridge Scatters award ten Free Games in which all wins are tripled. Three or more Mjölnir Bonus symbols open the Forge pick game. The Dice edition changes symbol presentation with cube motifs but retains the documented structure.

Version comparison

Field	Asgardians	Asgardians Dice
Grid	5×3	5×3
Paylines	25	25
RTP	96.07%	96.07%
Volatility	Low	Low
Bet reference	€0.25–€200	€0.25–€200
Free Games	10, wins 3×	10, wins 3×
Forge trigger	3+ Mjölnir symbols	3+ Mjölnir dice

The matching figures do not make the files interchangeable. Record the exact title and version from the loaded help. An account may offer one edition, both, or neither, and catalogue listing is not proof of access in New Zealand.

Base game and Loki Wild

Ordinary results follow 25 defined paylines. Loki is the Wild and substitutes for regular symbols but not Scatter or Bonus. The provider lists five Loki Wilds at 300× base bet in both versions. Odin is the leading ordinary character at 20× for five.

These values use base bet. Check the live formula before treating them as total-stake multipliers. Use the numbered line overlay to trace each combination and avoid counting nearby symbols that fall outside a path.

The Dice edition adds cube styling to Loki, Odin and the palace but does not, on the official page, publish a different paytable structure. A visual skin should not be described as a mathematical change without version evidence.

Rainbow Bridge Free Games

Three or more palace or Rainbow Bridge Scatters trigger ten Free Games. Endorphina states that all wins during those rounds are tripled. The symbol summary gives five Scatters a 100× base-bet award.

Record the trigger payment separately from feature results. For each Free Game, list highlighted line awards before the 3× factor if the interface shows them, then the multiplied credit. If only the final value appears, save the paytable wording and settled history entry.

Do not triple the feature total again when individual round values already include the factor. The displayed counter, per-round credits and end summary should reconcile. The public source does not need an invented retrigger rule; use the deployed help for any extension behaviour.

Mjölnir and the Forge pick bonus

Three or more aligned hammer Bonus symbols open the Forge. The player strikes or selects shields, with successful choices revealing prizes. This is a pick-style mode, not the Rainbow Bridge Free Games feature.

Create a bonus ledger with the trigger symbols, each shield choice, revealed value, running total and end credit. The phrase “correctly aligned” means the current help’s trigger diagram matters; do not assume hammer symbols count anywhere in the same way as Scatters.

An animation of Thor’s hammer is not itself a payout rule. Preserve the numerical values shown after each choice. If a losing or end condition exists, cite the live help rather than guessing from theme.

Original versus Dice evidence

For the original, the official page names the palace Scatter, Loki Wild, Odin high symbol and Mjölnir Bonus. The Dice page describes the same roles with cube-decorated versions. Both publish 96.07% RTP and low volatility.

When comparing screenshots, label them by edition and software version. Do not use an Asgardians Dice paytable to settle an original Asgardians round simply because headline values match. Operators can update or configure builds independently.

One canonical article is useful because it prevents search duplication while still preserving differences. The sources section links both official product pages so the reader can inspect each record.

Optional Risk and Bonus Pop

Both provider pages list Risk Game and Bonus Pop. Risk is a post-win decision and should be audited after the underlying line or feature award. Bonus Pop can depend on casino and jurisdiction; its presence in the studio profile does not prove account access.

For a baseline comparison, decline Risk and leave optional purchase controls unused. Once the two primary triggers are understood, document any optional price, stated RTP and debit separately.

RTP, low volatility and currency

The shared 96.07% RTP is theoretical over a large sample. It does not predict when a bridge or hammer will land. Confirm the active value in each edition because equal public numbers do not guarantee equal deployed configuration.

Low volatility is the supplier’s classification, not a promise of frequent profit. Ten tripled rounds can still return less than their triggering stake. Use fixed money and time limits and never increase stake to wait for a particular god or feature.

The €0.25–€200 range must remain labelled in euros. Actual NZD controls, if available, come from the authenticated game interface.

Mobile and evidence workflow

On mobile, confirm that cube overlays in the Dice edition do not obscure symbol roles. The title, total stake, feature counter, factor and Forge result should remain visible after orientation changes and text enlargement.

For a dispute, save title, edition, version, active RTP, round ID, trigger symbols, payline breakdown, 3× calculation or shield choices, and balances before and after. The server-side history is more useful than a cropped animation.

Final assessment

Comparing the two trigger routes in one round

The palace and hammer symbols must be logged independently because they lead to different modes. Start with a reel-coordinate table and label every special symbol as Scatter or Bonus. If the same settled grid appears to contain qualifying sets of both, the current help should explain feature priority or sequencing. Do not decide priority from which animation plays first.

For the bridge route, record Scatter payment, ten-round counter and the 3× factor on every win. For the Forge route, record the hammer alignment and each shield selection. If both modes are awarded in succession, keep two subtotals and compare their combined credit with the transaction history.

The word “aligned” in the Forge description deserves attention. Scatters count anywhere, but Bonus symbols may require specified reels or positions. Save the trigger illustration from the exact edition. A set of three visible hammers is not enough evidence when it does not match the published alignment.

A practical original-versus-Dice checklist

The title bar should say either Asgardians or Asgardians Dice. Next record the version string, palace artwork, Loki symbol, Mjölnir design and paytable. Confirm 25 lines, 96.07% RTP and the €0.25–€200 supplier reference only as comparison fields, not as proof that the builds are identical.

In the Dice edition, cube motifs can make the palace and hammer icons look like dice-based mechanics. The official source still describes a line slot with the same feature triggers; it does not describe a separate dice-roll payout system. Do not add one based on the visual skin.

When an operator lists both editions, link each game tile to the appropriate help before writing a support request. A round ID from Dice should not be paired with an original Asgardians screenshot. Keeping the identity evidence together prevents a correct result from being challenged under the wrong paytable.

Factor ordering and final credit

During Free Games, the official wording says all wins are tripled. If a Loki Wild also participates, first use the paytable to determine the line win, then apply only the factor sequence displayed by the active rules. The public page does not support an extra universal Loki multiplier; Loki is a substitute and has its own five-symbol pay.

At feature end, sum the settled per-round credits and compare them with the displayed total. Any Risk action belongs after this total. This ordering keeps the 3× feature factor, paytable multipliers and optional gamble from being conflated.

One last comparison point is the source date. The two official pages were checked together, so their matching headline settings are directly comparable. A later review should repeat that paired check instead of updating one edition from memory. If only one page changes, show the divergence in the table and keep the common canonical article; readers then see precisely which edition carries the new value.

Asgardians and Asgardians Dice share a documented 25-line, 96.07% framework with two clear feature routes: tripled-win Free Games from Rainbow Bridge Scatters and a separate Forge pick bonus from Mjölnir symbols. Dice styling changes the visual identity while the official headline maths remains aligned.

The loaded help must still confirm the exact edition, trigger alignment, factor application and optional controls. Keeping the two modes and two editions labelled avoids most interpretation errors.

Official and related sources

• Asgardians official product page
• Asgardians Dice official product page
• Endorphina catalogue guide
• 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 Endorphina, 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.