Red Cap by Endorphina: expanding Wild Free Games guide

Red Cap is a five-reel, three-row slot with 20 paylines. Endorphina publishes 96.03% RTP, high volatility and a €0.20–€160 supplier stake range. Three or more basket Scatters start ten Free Games, and the feature can retrigger. During those rounds, the Red Cap Wild expands across every position on its reel.

These figures identify the studio profile checked on 8 October 2026. They do not prove that a particular New Zealand account carries the game or uses identical settings. If a version loads, its own help, currency and transaction history are the relevant evidence.

Published configuration

Field	Official value
Grid	5×3
Paylines	20
RTP	96.03%
Volatility	High
Bet reference	€0.20–€160
Trigger	3+ basket Scatters
Starting Free Games	10
Retrigger	Available
Feature Wild	Expands over its reel

Keep the euro range labelled as euros. It cannot be rewritten as an NZD limit. Before any paid round, open the live help and record the title, version, active RTP, total stake, currency and optional controls.

Base-game paylines and symbols

Ordinary combinations use 20 numbered line paths. A visible row of matching symbols is payable only when it follows one of those routes under the help’s direction rule. Use the line overlay and settled result rather than judging the artwork alone.

Red Cap substitutes for regular symbols but not the basket Scatter. In the base game it behaves as a standard Wild; its expansion belongs specifically to Free Games. The provider lists granny as the highest ordinary symbol at 40× base bet for five, followed by the huntsman at 30×.

Those examples are expressed against base bet, not necessarily total stake. Check how the loaded version defines line stake, coin value and total bet before translating a multiplier into currency.

Basket Scatter and ten Free Games

The pie basket counts as Scatter. Three or more trigger ten Free Games, and the mode can retrigger. The official symbol summary also gives five Scatters a 200× base-bet award. That five-symbol example should be applied only when the settled grid and result panel confirm the count.

Start an evidence sheet with the trigger round ID, basket positions, stake and balances before and after settlement. Add one row for each Free Game, noting the counter, any new baskets, rounds added, Wild reel and credit. If a retrigger occurs, insert additional rows instead of overwriting the original ten.

The counter should reconcile arithmetically: previous remaining rounds minus the round played plus any extension. This makes a fast retrigger animation easier to verify.

Expanding Wild during the feature

When Red Cap lands in Free Games, it expands over all positions on that reel. Expansion changes substitution coverage; it does not automatically create a separate cash award. List every highlighted line that uses the expanded reel and apply the paytable once per valid route.

Do not assume the expanded reel remains sticky into the next Free Game. The public description supports full-reel expansion, not persistence. If the deployed help states a continuing rule, record that version explicitly rather than importing it into the general profile.

A clean screenshot shows the complete grid, line numbers, Free Games counter and numerical credit. A crop of the character animation alone cannot substantiate settlement.

Risk Game and Bonus Pop

Endorphina lists a classic Risk Game as an optional post-win decision. Reconcile the slot result first. If Risk is used, document the offered amount, choice, comparison and final balance on a separate line; it does not change whether the basket trigger or expanding Wild worked correctly.

Bonus Pop is also listed, but the supplier says it may be unavailable at some casinos or in some jurisdictions. If the button appears, read its price, conditions and any alternate RTP notice before choosing it. Its absence does not change the ordinary Free Games rules.

RTP, high volatility and limits

The 96.03% RTP is a long-run theoretical rate for the cited provider configuration. It is not a prediction for one feature, session or deposit. Approved deployments may use different settings, so the value inside live help takes priority for an actual account.

High volatility describes uneven outcome distribution; it does not say when a feature will arrive. Ten Free Games can end without covering their trigger stake. Set an affordable loss boundary and time limit before play, and do not raise the stake because baskets have not appeared recently.

The €0.20–€160 range remains a supplier reference. An operator decides actual currency, increments and caps. Record total stake, not just a coin denomination, before comparing any result.

Mobile and demo checks

On a phone, ensure all five reels, the feature counter, total stake, balance and line highlight remain visible. Test portrait and landscape orientation, open the paytable, and confirm that the close control stays reachable after system zoom.

The studio demo can help locate the basket, Wild and history controls. It does not establish real-money availability in New Zealand or prove the configuration of another operator’s build.

For support, preserve the game version, active RTP, timestamp, round ID, trigger screen, each expanded reel, retrigger count and final feature total. Redact personal account data before sharing evidence outside authenticated support.

Worked feature audit

Create a three-column grid for every Free Game and mark the original Red Cap position before expansion. Shade the other two cells on the same reel to show substituted coverage. Beside the grid, write the numbered lines completed through that reel and their separate awards.

If baskets land during the same round, record their count independently. This prevents a retrigger from being mistaken for an extra Wild prize. At the end, total all feature-round credits and compare them with the summary screen and balance movement.

Common errors include calling the expanding Wild sticky, treating 20 lines as 20 ways, adding the 200× Scatter example without five baskets, or merging Risk outcomes into Free Games return. A chronological worksheet resolves each error without relying on memory.

Final assessment

Separating trigger, transformation and settlement

The feature has three stages that should not be compressed into one claim. First, baskets are evaluated as Scatters and the game awards entry. Second, the Free Games counter starts and Red Cap changes from a standard substitute into a full-reel expanding Wild. Third, each resulting line is settled under the paytable. A screenshot from only the third stage cannot prove how entry occurred.

Use a timestamped sequence. The trigger capture should show basket count and the awarded counter. Each feature capture should show the original Red Cap coordinate before expansion where possible, the completed reel and the highlighted lines. The final capture should show the summary and post-feature balance.

When an expanded reel intersects several line paths, list those lines individually. If the game shows one combined award, reconstruct it from the highlighted routes only when the current paytable provides enough information. Otherwise preserve the combined value as reported rather than inventing a breakdown.

If a basket lands during Free Games, first determine whether it remains Scatter and whether the build awards more rounds. Do not treat the basket as a Wild simply because the main character changes behaviour in the feature; the transformation applies to Red Cap, not automatically to every special symbol.

Questions for an operator support case

Ask for the server record of the specific round ID, the active game version and RTP, and the feature counter before and after a disputed retrigger. If the concern involves expansion, identify the reel and line numbers. A message with those details is more actionable than saying the Wild “looked wrong”.

Keep the operator response with the captured help screen. If the reply describes a configuration different from the public Endorphina page, label it as an operator-specific version and date it. Do not overwrite the supplier record; both pieces of evidence can be accurate for different deployments.

The same discipline applies to Bonus Pop. A button’s presence establishes only that an option is offered. Its price, outcome rules and RTP must come from the active interface before it is discussed as part of Red Cap.

Finally, verify the feature-end transition. The Free Games counter should reach zero, the expanding behaviour should stop, and the next paid round should use the base-game Wild rule. Record the first post-feature grid if the interface appears to retain an expanded reel; it may be a visual delay, but the settled history will show whether a new stake was debited under normal rules.

Red Cap is a conventional 20-line game whose feature changes one symbol materially: the normal Wild becomes a full-reel expanding Wild during ten retriggerable Free Games. The official page supports the grid, RTP, volatility, euro range, basket trigger, expansion and optional features.

The live help remains decisive for the deployed RTP, retrigger additions, base-bet definition and Bonus Pop availability. A settled round history is stronger evidence than the fairy-tale animation.

Official and related sources

• Red Cap 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.