Ancient Troy by Endorphina: original and Dice feature comparison

Ancient Troy and Ancient Troy Dice are five-reel, three-row games with 25 paylines. Both official pages publish 96.06% RTP, medium-high volatility and a €0.25–€200 supplier stake range. Three or more Palace Scatters start 10 Free Games with two Trojan Jokers per spin.

The Dice edition changes character and object artwork into carved cubes while preserving the published headline rules. This single page compares the editions without creating competing near-duplicate URLs.

Shared official profile

Field	Original	Dice
Grid	5×3	5×3
Paylines	25	25
RTP	96.06%	96.06%
Volatility	Medium-high	Medium-high
Bet reference	€0.25–€200	€0.25–€200
Trigger	3+ Palace Scatters	3+ Palace cubes
Starting Free Games	10	10
Feature	2 Trojan Jokers/spin	2 Trojan Jokers/spin

These figures were checked on 8 October 2026. They do not prove New Zealand availability or operator limits.

Base-game symbols and paylines

The Trojan Horse is Wild and substitutes for all regular symbols except Scatter. Five Wilds are published at 40× base bet. Achilles is the highest ordinary symbol at 32× for five, while Hector is listed at 24×.

The Dice version maps those roles onto cubes: Palace cube as Scatter, Trojan Horse cube as Wild and character cubes for the high symbols. Use each edition’s own legend; do not identify a cube from colour alone.

Twenty-five fixed routes cross the 5×3 grid. Record the line number, matching symbol count, Wild substitutions and paytable value for every highlighted win.

Palace Scatter and ten Free Games

Three or more Palace Scatters trigger 10 Free Games. Five Scatters carry a published 200× base-bet award. Keep direct Scatter credit, entry to the feature and any base-game line wins as separate components.

Capture all Palace positions and the awarded counter. During the feature, two Trojan Jokers appear per spin. Their multipliers can be ×1, ×2 or ×3 according to the provider description.

The public summary does not justify multiplying the entire feature total automatically. Record which Joker participates in which winning combination and how the result panel applies its value.

Auditing two Trojan Jokers

Create a row for each Free Game with Joker A position and multiplier, Joker B position and multiplier, qualifying paylines, ordinary subtotal and final credit. If both Jokers touch one winning line, rely on the current help for combination rules rather than adding or multiplying them by intuition.

A ×1 Joker can still substitute while leaving the value unchanged. A ×3 label is not itself a win; the Joker must participate under the feature rules. Keep unrelated paylines outside the Joker calculation unless the interface groups them.

If a Palace Scatter lands during Free Games, note whether it retriggers and how many rounds are added. Do not import a retrigger value from another title.

Original versus Dice edition

The official specifications match, but deployed versions can still differ. Save the exact title, build number and RTP from both help screens. Compare symbol legends and feature wording side by side.

Dice cubes need adequate pip or icon contrast at mobile size. The original needs clear distinction between Palace Scatter and architectural background. A feature audit should depend on labels and coordinates, not theme familiarity.

If an operator carries only one edition, describe that observation narrowly. It does not establish a country-wide restriction.

Bonus Pop and Risk Game

Both pages list Bonus Pop and a classic Risk Game. Bonus Pop can be jurisdiction-dependent; check price, conditions and any alternate RTP notice before choosing it. Purchased access is not equivalent to a natural Palace trigger.

Risk follows an eligible settled win. Record the original credit before documenting the amount risked and outcome. It should not be folded into the Trojan Joker multiplier audit.

RTP, volatility and stake limits

The 96.06% RTP is theoretical over a large number of rounds. Ten Free Games can finish below the triggering stake. Medium-high volatility does not predict when the Palace will appear.

Keep the provider’s €0.25–€200 range in euros. An operator can use another currency, minimum or maximum. Verify total stake immediately before play.

Set affordable money and time boundaries and do not chase a missing feature. If live help shows another RTP, report that deployed value separately rather than averaging it with 96.06%.

Mobile and demo testing

On a phone, confirm all fifteen positions, both Joker markers, their multipliers, counter, total stake and balance remain readable. Test portrait and landscape layouts and reopen the round from history after rotation.

The studio demo can help locate controls. It does not prove real-money availability, regional permission or account-level settings.

Worked Joker settlement

Suppose Joker A at C2 shows ×2 and Joker B at D1 shows ×3. Copy the settled grid and list only paylines using either position. Separate routes using A, routes using B and any route using both. Then follow the active help’s rule for each category.

Do not automatically calculate ×6 for a route containing both; multipliers might add, multiply or be resolved another way. The game history should expose the final amount even if it does not reveal every intermediate operation.

Compare the sum of all feature-round credits with the final summary and balance increase. Account for any direct trigger-spin Scatter award once, not twice.

Support evidence

Provide edition, version, active RTP, UTC time, round ID, total stake, Palace positions, feature counter, both Joker positions and values, highlighted lines and balances. Ask for the server-side multiplier sequence if the displayed arithmetic is unclear.

Keep the original and Dice evidence in separate folders. Matching public specifications do not make screenshots interchangeable.

Distinguishing Joker placement from Wild substitution

The base-game Trojan Horse is Wild, while Trojan Jokers belong to Free Games. Do not label every special feature marker as the base Wild. Capture the feature legend showing how a Joker is placed, which multiplier it carries and whether it substitutes before or after ordinary symbols are evaluated.

Two Jokers per spin means two placement events, not necessarily two winning events. A Joker can land outside a payable route. Mark both coordinates even when only one contributes to settlement; this makes the absence of a second multiplier understandable.

If both occupy the same reel, record the rows independently. If the interface prevents overlap or selects distinct reels, note that observed constraint without generalising it until help confirms the rule.

Counter and multiplier ledger

Use columns for feature round, remaining spins, Joker A coordinate/value, Joker B coordinate/value, affected lines, line subtotal and credited total. Put Palace Scatters in another column so retriggers cannot be confused with Joker awards.

For each round, reconcile the counter first and the money second. This catches an omitted Free Game even when the total payout looks plausible. At feature end, the sum of row credits should equal the summary, while the counter should have accounted for all initial and added spins.

If the animation displays ×1, retain it in the record. It confirms Joker participation even though it leaves value unchanged. Omitting ×1 events can make later comparisons appear to have fewer than two Jokers.

A version-comparison protocol

Load the original and Dice help files, not just their splash screens. Compare grid, lines, RTP, trigger, starting spins, number of Jokers, multiplier set, Scatter award, Wild rule and optional controls. Mark each field as matched, different or not shown.

Then compare one settled base-game round format and one feature-history format. The public pages match today, but an operator may carry different build revisions. Keeping version-specific evidence avoids claiming that a Dice visual update changed—or did not change—the math without proof.

If future official data diverges, retain one canonical page and update the comparison table. A separate thin Dice URL would make such corrections harder to keep consistent.

Understanding paytable multipliers

The five-Palace 200× example, five-Wild 40× example, Achilles 32× and Hector 24× are all expressed against base bet. Trojan Joker ×1–×3 values apply within the feature under their own rule. Never multiply every paytable example by a Joker unless settlement demonstrates that interaction.

Equal numerical results can arise through different paths. Label the symbol, line and feature state alongside every credit so the source remains clear.

Final assessment

Ancient Troy’s central feature combines two random Trojan Jokers per Free Game with ×1–×3 values. The Palace trigger and 25-line structure are straightforward; multiplier scope is the detail that must be read from the exact build.

The official sources support the matching original/Dice profile. Availability, live currency, active RTP, retriggers and optional access remain deployment-specific.

Retain dated help captures so later configuration changes remain traceable to the correct edition and round.

Official and related sources

• Ancient Troy official product page
• Ancient Troy 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.