NZ-NI-0450 · supplier source record
Silk Road: Walking Wild journey and chest rules
Silk Road begins its feature only when the camel and bazaar land together on opposite edge reels. This guide follows the Walking Wild, adjacent chests, sandstorm stop and retrigger rules in order.
Supplier sources below. Operator eligibility needs a separate check.

Silk Road is a five-reel, three-row Endorphina slot with nine paylines. The official page checked on 8 October 2026 publishes 96.04% RTP, medium volatility and a €0.09–€180 reference stake range. Its 10-Free-Game journey starts only when a camel on reel one and a bazaar on reel five land simultaneously.
The supplier profile documents the general game design. It does not confirm availability in a New Zealand account, an NZD stake ladder or the exact RTP delivered by an operator. Open the active help and preserve the game version before a paid decision.
Published configuration
| Field | Provider value |
|---|---|
| Grid | 5×3 |
| Paylines | 9 |
| Provider RTP | 96.04% |
| Volatility | Medium |
| Bet reference | €0.09–€180 |
| Journey trigger | Camel reel 1 + bazaar reel 5 |
| Initial Free Games | 10 |
The catalogue lists Classic Risk and Bonus Pop. Both are optional controls whose availability may vary. Their presence and current terms should come from the loaded build, not assumption.
Base game and enabled lines
Wins form on enabled paylines from the leftmost reel across adjacent reels. Because the public page describes enabled lines, record how many are active and the total bet before each round. A nine-line diagram alone does not prove that every line was selected in a configurable interface.
The merchant is the Wild and substitutes for ordinary paying symbols but not the Scatter. The provider page describes five Wilds as paying approximately 555× and five necklace symbols as approximately 111×. “Approximately” is not an exact paytable entry, so current help must supply the precise multiplier and wager basis.
Do not convert those promotional approximations into guaranteed cash amounts. Save the visible paytable, line stake and settlement whenever a relevant combination occurs.
Exact edge-reel trigger
The journey begins when the camel appears on reel one and the bazaar appears on reel five in the same paid spin. The two edge symbols work as a paired condition. One without the other is not the published trigger.
The qualifying spin awards 10 Free Games with a Walking Wild. Capture both edge positions, the feature message and the starting counter. If an operator offers another entry route through Bonus Pop, document that route separately rather than rewriting the natural trigger.
This exact condition prevents a common error: describing any two thematic symbols as enough. The reel placement and simultaneous landing are both material facts.
Walking Wild journey
During Free Games, the merchant Wild begins on the left side and moves towards reel five and the bazaar. Record its position after each round. Movement is part of the feature state; it is not automatically a separate award.
The Walking Wild can substitute on paylines as it moves. Trace each resulting win through the enabled line map. If more than one Wild image is shown during a transition, wait for the settled reel state before recording coordinates.
The journey can continue for up to 10 Free Games and may be retriggered. The public summary does not justify assuming an unlimited loop. Record every added game and compare the post-retrigger counter with the remaining balance.
Adjacent treasure chests
Treasure chests on the reel adjacent to the Walking Wild can award up to 50× total bet. “Adjacent” is a positional requirement. Mark the Wild reel, chest reel, row and printed prize for each event.
A chest elsewhere on the grid should not be treated as a qualifying journey prize without support from the loaded help. Likewise, the 50× figure is an upper bound, not the default value of every chest.
Keep the chest award separate from line wins for the same Free Game, then compare their combined amount with the feature meter. If the meter is inclusive, do not add the chest again at the end.
Sandstorm stop
The sandstorm ends the journey. Wins accumulated before that point are added according to the provider description. Save the last settled round before the storm, the stop message and the final summary.
Do not infer an extra consolation award from the storm animation unless current help lists one. Its confirmed role is to terminate the feature sequence. A journey that ends before the merchant reaches the bazaar should be reconciled using the prizes already settled.
If the interface shows a cinematic transition after the stop, wait for transaction history. The final animation may repeat earlier chest values for presentation without creating new credits.
Scatter route in the base game
Gold coins are the Scatter symbols and appear in the main game. Five Scatters pay 100× base bet according to Endorphina’s page. The public description separates this Scatter award from the camel-and-bazaar journey trigger.
Record the coin count, printed base-bet multiplier and final credit. Do not use the Scatter as a substitute for either edge symbol and do not assume a coin combination automatically starts Free Games.
If active help lists additional coin counts, preserve that table rather than extrapolating from the five-symbol example.
Feature ledger and settlement
Use one row per Free Game with counter before, merchant position, adjacent chest coordinate, chest value, line-win subtotal, retrigger addition, sandstorm flag and counter after. Include rounds without wins because they establish how the journey advanced.
At feature end, total the chest prizes and line results once. Compare that subtotal with the feature summary and account history. If the final screen already includes every component, it is the reconciliation total rather than another award.
This method also catches a missed retrigger. The expected next counter can be calculated from the previous counter, one consumed game and any explicitly added games.
RTP, volatility and optional features
RTP of 96.04% is the provider’s published long-run setting. It cannot predict when the paired trigger will land, how far the merchant will travel or whether a 50× chest will appear. Medium volatility is not a promise that outcomes will be evenly spaced.
Classic Risk can offer up to 10 doubling decisions on eligible settled wins where enabled. It is separate from the journey. Bonus Pop may provide alternative feature access where permitted; record its displayed cost and terms before use.
Choose spend and time boundaries in advance. A Walking Wild moving closer to the bazaar can create a sense of progress, but it is not stored cash and does not guarantee that the next round will avoid the sandstorm.
Mobile and local-access checks
On mobile, confirm that both edge-reel trigger symbols, the Walking Wild position and the chest value remain visible. Rotate the device and open history before play so a later reconnect does not obscure the evidence path.
Record provider, game ID, version, RTP, currency and enabled lines. If the title is absent from a New Zealand account, report that observation rather than treating the global supplier catalogue as proof of local availability.
Where the loaded paytable replaces the provider’s approximate 555× or 111× wording with exact values, use the live table and note the check date. Do not average or round two configurations together.
Worked journey example
Begin with the paid trigger round showing a camel on reel one and bazaar on reel five. Record both coordinates and the 10-game opening counter. For every Free Game, draw the merchant’s settled position after movement and mark only chests on the adjacent reel. A chest two reels away may fit the theme, but it does not meet the published adjacency condition.
If an adjacent chest reveals 12× total bet, enter that value separately from the round’s line-win subtotal. If the next game triggers a sandstorm, close the journey after recording all earlier settled amounts. Do not add a speculative storm award or assume the merchant would have reached the bazaar on the following round.
When a retrigger appears, calculate the counter transition explicitly and continue the same journey ledger. At feature end, compare the accumulated line and chest components with the summary and history. The summary should reconcile the components; it should not be counted as an extra prize.
Common interpretation errors
- Treating a camel or bazaar alone as the natural trigger.
- Ignoring the required reel-one and reel-five positions.
- Counting Walking Wild movement as a cash award.
- Applying a chest value when it is not adjacent to the Wild.
- Reading “up to 50×” as every chest’s prize.
- Treating the sandstorm animation as an extra loss or award.
- Publishing approximate promotional paytable figures as exact.
- Claiming New Zealand access from the supplier page.
Final assessment
Silk Road is best recorded as a journey state: paired edge symbols open 10 games, the merchant moves towards reel five, adjacent chests may add prizes, retriggers extend the counter and the sandstorm closes the sequence.
The official page supports the grid, lines, RTP and central mechanics. Current game help remains necessary for exact paytable values, the loaded RTP, optional controls, settlement order and local access.
Official and related sources
- Silk Road 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.
Primary source and correction path
This guide separates documented product information from market availability. Check the official source and the game help inside the exact version offered before making a decision.
