Gambleman: five-line rules and clover feature map

Gambleman by Endorphina uses a 3×3 grid with five fixed paylines. The official page publishes 96.07% RTP, high volatility and a €0.05–€15 reference range. It lists Pick Game, Pile, jackpots, Fortune Wheel and Re-Spin; the description also identifies Bonus Pop.

Its compact base does not mean simple feature accounting. Clover Tokens reveal covered cells, Fortune Draw uses card suits, and the wheel can apply a multiplier. Each state needs its own ledger.

Provider settings

Field	Checked value
Grid	3×3
Lines	5 fixed
RTP	96.07%
Volatility	High
Stake reference	€0.05–€15
Status	Pending

The provider range is denominated in euros and does not establish NZD limits. Confirm the loaded game ID, currency, RTP and increments in help.

Base paytable

Save the five line paths and winning direction. The official symbol note lists three diamonds at 50× base bet and three leprechaun hats at 5×. Confirm the base-bet definition; it may differ from total debit.

Record every winning path and final credit. Do not assume a large symbol graphic covers more than one cell. Where several lines pay, add them once and compare with history.

Clover Token reveals

Four-leaf-clover gold coins appear in the main game and cover other symbols. When they fly away, the uncovered symbol may complete a combination. Capture the grid before reveal, Token position, revealed symbol and settled line evaluation.

A Token is not a certain award. If several appear, note their order and whether evaluation occurs after each reveal or after all cells settle. Animation speed is not a rule.

Fortune Draw Pick Game

The provider connects the Fortune Feature Draw with Clubs, Hearts, Spades and Diamonds and describes a jackpot up to 1,000× total bet. Preserve the live paytable because a later FAQ line uses inconsistent wording.

Record the offered suits, selection, reveal, stopping condition and credited multiple. Do not infer that a suit is more likely because it recently lost. If all cards are revealed after settlement, only the selected outcome belongs in the credit ledger.

Clover Wheel

At wheel entry, capture starting award, visible segments, pointer position and final multiplier. Determine whether the wheel multiplies a current win, a feature total or a fixed base. Apply it only once.

A wheel animation can visually pass a larger segment without awarding it. The server result and history are the evidence, not the apparent stopping speed.

Lucky Re-Spin and Pile

For Re-Spin, save which reels or cells hold, the number of attempts and what resets the counter. Distinguish a single respin from a persistent Hold-and-Win sequence. List every newly credited symbol.

Pile is separately tagged. Record the item collected, thresholds, effect and reset. A growing coin heap does not prove that completion is near or that stake changes preserve progress.

Bonus Pop

The description says Bonus Pop can be triggered during gameplay, but operator and jurisdiction settings may disable it. If present, capture price, underlying stake, feature destination and mode-specific RTP disclosure.

Paid access buys an uncertain feature state, not profit. Compare the displayed cost with the full session cap before confirmation. A missing button should be recorded as unavailable, not as a broken game.

RTP and high volatility

Endorphina publishes 96.07% for the checked provider configuration. RTP is theoretical over many rounds and does not predict a Token, wheel or card draw. A casino may expose another approved setup, so retain the live value with date and game ID.

High volatility signals uneven results. Use a standard stake, cash cap and time limit. Do not raise the wager because a Pile looks advanced or because the wheel has not appeared.

Demo, mobile and history

Official demo access helps locate rules where permitted, but it does not prove real-money availability in New Zealand. Check the mode label.

On mobile, test all nine cells, five lines, covered Tokens, wheel pointer, Pick cards, respin counter, stake and history at 200% text size. After a disconnect, reopen the completed round before continuing.

New Zealand scope

The provider page confirms the game in Endorphina’s catalogue. It does not confirm a named NZ-facing operator, local legality or feature availability. Verify operator terms and authenticated lobby independently.

Do not use a studio licence as a substitute for consumer-facing operator checks. Keep supplier evidence and account evidence in separate fields.

Support-ready worksheet

Store operator, URL, date, title, ID, currency, RTP, stake and round ID. Add Token reveals, Pick choices, wheel result, respins, Pile changes and final credit. Redact personal data before sharing.

If two source statements conflict, preserve both and prefer the current embedded help for the played build. Do not silently choose the larger multiplier.

Common questions

What RTP is listed?

96.07% on the checked official page.

How many lines does Gambleman use?

Five fixed lines on a 3×3 grid.

What do Clover Tokens do?

They uncover covered symbols that may contribute to combinations.

Is Bonus Pop always enabled?

No. It can depend on operator and jurisdiction.

Is NZ availability confirmed?

No operator-level availability was verified.

Worked feature sequence

If a Token uncovers a symbol that starts Lucky Time, create a parent row for the paid round. Add the reveal as the first child event, then record crumbling coins, Fortune Draw choices and any wheel multiplier in order. Reconcile the feature only at final settlement.

This prevents the same coin value from being counted once during collection and again in the summary. It also makes a support report understandable without relying on animation descriptions.

Final assessment

Gambleman fits several feature types into a small five-line grid. Its best guide explains the evidence path from covered Token to Pick, Wheel and Re-Spin rather than treating “luck” as a strategy.

Use the 96.07% and euro range as studio references. The actual build, minimum account stake and enabled optional modes determine suitability for a fixed budget.

Resolving the provider-page wording

The official page contains promotional copy, structured feature tags and symbol notes. Those layers can use different shorthand. Build the rule record from the embedded help first, then use the public page as dated supporting evidence. Where the description says “up to 1,000× total bet” and another summary uses a different jackpot phrase, do not select the more attractive number. Record the conflict and quote only the value attached to the loaded build.

The same discipline applies to Bonus Pop. A public feature description confirms that the concept exists, but price, entry state and RTP can be deployment-specific. Capture the confirmation panel before accepting. If it omits cost or mode details, close it and keep the field unresolved.

Mobile feature-state test

Run a usability check without relying on rapid animation. In portrait mode, confirm that covered Clover Tokens remain aligned with the nine cells and that their revealed symbols are visible before the next state. Rotate to landscape and verify that the wheel pointer, multiplier labels and card suits do not move outside the viewport.

Increase text size to 200%. The total stake, current win, respin counter and close controls should remain reachable. Colour cannot be the only cue for card suits or wheel segments. If an element is obscured, preserve a screenshot with device and browser details.

Cost comparison without a false ranking

Compare Gambleman with another 3×3 game using exact minimum total debit, current RTP, volatility, optional-mode price and maximum wording. Do not rank it higher because it has more named features. A longer feature list can create more decisions and more opportunities to misunderstand settlement.

The five-line base may be easy to read, but high volatility and optional access can still consume a small budget quickly. Estimate how many ordinary rounds fit the session cap at the selected stake. Exclude Bonus Pop purchases from that estimate unless their full price is included.

Dispute package

For a Token-to-Draw dispute, provide the covered grid, reveal, Lucky Time trigger, card choice, wheel result if any, final credit and server round ID. State local time with time zone and account currency. Redact name, email, balance history unrelated to the case and payment data.

Support should never ask for a password or one-time authentication code. Use the verified operator contact route rather than links received in unsolicited messages. A well-structured package protects both accuracy and account security.

Reading one complete round

A complete Gambleman record begins with the paid base spin and ends only after every attached reveal, draw, wheel or re-spin has settled. Note the balance once at the start and once at the end; intermediate celebration screens are not separate payouts unless history lists a distinct credit. This avoids treating the same award as both a feature value and a final win.

If a clover reveal changes the grid, record the before-and-after state rather than photographing only the result. For the Fortune Draw, distinguish the selected card from the eventual credited amount. For the wheel, capture the pointer’s final segment and the history entry. These details turn a visual sequence into a checkable account of what happened.

Do not infer the next outcome from previous clovers or wheel stops. The log is useful for reconciliation and support, not prediction.

Official and related sources

• Gambleman 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.