3 Witch Pots: green, red and purple feature routes

3 Witch Pots by Endorphina is documented as a 5×4, 40-line game with 96.07% provider RTP and medium-high volatility. The studio gives a €0.40–€200 reference range, marks the page Approved and lists Wild, Hold, Pick, Pile and Free Games. Bonus Pop is not listed.

Its core is a three-colour system: green Elixir tokens lead toward the Potion of Fortune Free Games, red tokens toward Pumpkin Hold, and purple tokens toward a Pick feature. These routes have different units and records, so a single “bonus value” table would be misleading.

Verified provider settings

Field	Published value
Grid	5×4
Paylines	40 fixed
RTP	96.07%
Volatility	Medium-high
Bet reference	€0.40–€200
Status	Approved
Bonus Pop	Not listed

The values are an official-source snapshot, not confirmation that the title is accessible through a New Zealand account. The live help must establish the loaded RTP, currency, minimum debit and exact trigger wording.

Base grid, Wild and Elixir tokens

The black cat is Wild on reels two through five in the base game and Free Games. It substitutes for symbols other than Tokens. A cat on reel one shown in artwork would not override this rule; verify the actual grid and payline.

Green, red and purple Elixir tokens can appear in the base game and Free Games. The tokens cover positions and are then removed, revealing symbols that may complete wins. Record both the covered grid and revealed grid. Otherwise a later symbol can look as though it landed independently.

Use separate colour counters. Do not combine a green token and red token into one generic progress total. The public page describes distinct cauldrons, and the live interface should show which colour accepted each token.

Green Potion of Fortune

The green cauldron route awards 24 Free Games according to the provider. Capture the accepted green token state, trigger transition and starting counter. During the feature, continue recording Elixir reveals and black-cat Wild positions.

The page does not resolve every retrigger or settlement edge case. Check whether additional green tokens add spins, advance another pot or behave only as reveal covers. Number rounds one through 24 and place any extension in the same parent feature record.

A 24-spin headline does not indicate value. The actual outcome depends on the paytable, line map and results. Do not compare it with a jackpot multiple by count alone.

Red Pumpkin Hold

The red route is a Pumpkin Hold feature. The provider says Pumpkin Scatter symbols trigger Hold, with five bonus symbols transferring to a 5×4 field and respins. Map the five starting symbols, remaining empty positions and attempts counter.

The published Ultra award is 500×. Confirm whether it requires a full field, a particular pumpkin or another condition in live help. Keep ordinary pumpkin values and named prizes in separate columns.

Each new locked symbol may reset attempts. Record the counter before and after the reset rather than inferring it from animation speed. At the end, use the transaction history as the settlement anchor.

Purple Pick route

The purple cauldron opens a Pick feature with 20 objects. Reveals can include Emerald, Sapphire, Amethyst or Ruby awards. A gemstone name alone does not establish a currency value or multiplier; the live instructions and result screen must supply it.

Number choices in the order selected. Record the unrevealed layout, chosen object, revealed label and final summary. The choice interface does not demonstrate player control over the underlying award unless the rules explicitly say so.

Do not add every reveal to the summary twice. Some Pick features display component prizes and then a total that already contains them. Balance history resolves that ambiguity.

Pile and cross-feature progress

Pile is listed, yet the public description does not completely define what persists. Check whether each pot’s progress is round-bound, session-bound or account-bound. A decorative liquid level may not be a saved counter.

Capture the pot immediately after an accepted token, then again after logout and return if the terms permit. Do not place extra rounds merely to test persistence. If the display resets, ask support whether it was cosmetic or linked to the session.

The three pots can create simultaneous visual progress. That does not prove the game will choose the nearest pot or that one colour increases the probability of another. Keep colour histories independent.

Maximum-multiplier context

The provider mentions a maximum multiplier of x1,300. A maximum is a design limit, not an expected result. It does not mean the 500× Ultra plus other labels can simply be added until x1,300 is reached.

Locate the maximum-win rule, cap and unit in the live help. If the build terminates a feature when a cap is reached, record that wording. Never market the ceiling as a likely return.

RTP and medium-high volatility

The 96.07% source value is theoretical over a long run. It cannot be validated from a short sample or promised for a particular operator build. Put the source percentage beside the loaded help value and date.

Medium-high volatility describes distribution, not timing. Pot progress does not make a trigger due. A budget and time boundary should be set before play and remain unchanged if a cauldron appears nearly full.

Mobile and demo verification

Where a provider demo is available, it can be used to locate the line map and token help, subject to age, region and site policy. It does not establish New Zealand real-money access.

On mobile, confirm that colour is not the only way to distinguish tokens. Pot labels, counters, total debit and Pick objects should remain legible in portrait. Test landscape without hiding outer reels. After backgrounding, compare round identifiers before recording a resumed scene.

New Zealand scope

The checked Endorphina page does not verify an operator-level New Zealand listing. The euro range is not an NZD promise. Check domain, account eligibility, currency, product ID and current terms.

An Approved supplier status is useful evidence about the provider page but does not authorise a particular operator relationship. If availability cannot be documented, call it unconfirmed and do not suggest bypasses.

Worked green-route record

Record one paid debit and the green token that completes the trigger. Save the counter at 24, then number each free round. For an Elixir reveal, preserve the covered position and the underlying symbol. Trace completed wins through the active 40 lines.

At the final summary, compare the feature total with history. If the feature added rounds, note the event that changed the counter. Keep all of it under the original trigger transaction.

Worked red-route record

Sketch the 5×4 field and enter the five transferred pumpkins. Number every respin or hold state, mark newly locked cells and update the attempts counter. Separate numeric values from named awards and retain the help rule for Ultra.

If the grid fills or the displayed value approaches a published ceiling, do not calculate a credit from artwork. Wait for settlement, then reconcile the opening and closing balances.

Worked purple-route record

Before choosing, save the instruction screen and 20-object layout. Number each selected object and revealed gemstone. The feature summary should be recorded once. If history shows a different value, preserve both records and stop before contacting support.

Troubleshooting

If a pot fails to update, capture the last accepted token, current counters, game ID and local time. Reconnect once and check history. Repeated play can obscure the state being disputed.

For green, include the Free Games counter; for red, include the full Hold grid; for purple, include pick order. Remove personal data and never provide passwords or authentication codes.

Common questions

Do all tokens trigger the same bonus?

No. Green, red and purple tokens belong to different routes.

Does the green route always start with 24 spins?

That is the provider-page statement. Verify additions and deployment details in live help.

Is Ultra always 500×?

The official page publishes 500× for the red route, but the loaded help must confirm its condition and unit.

Is Bonus Pop offered?

It is not listed on the checked product page.

Final assessment

Accessibility matters because the feature logic relies heavily on colour. A valid mobile check should confirm that labels, shapes or positions distinguish the pots for a person who cannot rely on green, red and purple alone. If the live build supplies only colour, document that limitation rather than inventing text labels.

3 Witch Pots is best audited as three independent state machines attached to one 40-line game. Green requires a free-round log, red a cell ledger and purple a pick-order record. Blending them loses the evidence needed to understand settlement.

The official source establishes the broad routes and notable values. Live help supplies deployment-specific rules. Keep the colours separate and stop at the preset limit regardless of visible pot progress.

Official and related sources

• 3 Witch Pots official page
• Endorphina catalogue guide
• Review methodology
• Responsible gambling
• 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.