Tribe by Endorphina: blue-sun Free Games counter explained

Tribe is a five-reel, three-row slot with nine fixed paylines. Endorphina publishes 96.06% RTP, medium-high volatility and a €0.09–€144 supplier stake range. Three or more Scatters start a Free Games feature governed by a blue-sun counter rather than a fixed number of rounds.

The provider specifications were checked on 8 October 2026. They do not confirm access through a New Zealand operator, an NZD stake range or a particular deployed RTP. Verify those items in the loaded game help.

Published configuration

Field	Official value
Grid	5×3
Paylines	9
RTP	96.06%
Volatility	Medium-High
Bet reference	€0.09–€144
Trigger	3+ face Scatters
Starting counter	3 blue suns
Green sun	Adds one blue sun and pays 2x total bet
Red sun	Removes one blue sun and pays 2x total bet
Free Games wins	x3 multiplier

The term “unlimited” describes the absence of a pre-set round count. It does not mean the feature cannot end or guarantees an infinite number of spins.

How the sun counter works

Free Games begin with three blue suns. The feature continues while at least one blue sun remains on the counter. Each completed spin must therefore be logged alongside the counter movement, not merely numbered against a fixed total.

Green and red sun events are awarded at random according to the provider description. A green sun adds one blue sun; a red sun destroys one. Both are published with a 2x total-bet payment. Record the counter before the event, its colour, direct credit and counter after the event.

Trigger and Scatter value

The face-with-tongue coin is Scatter. Three or more trigger the Free Games, while five Scatters are published at 500x base bet. The direct Scatter payment belongs to the trigger round and should be separated from feature credits.

A trigger with three Scatters does not specify how long the feature will last. Duration emerges from the subsequent green and red events. Any estimated number of rounds would therefore be speculation.

The x3 Free Games multiplier

Endorphina states that all wins during Free Games are multiplied by three. Apply that multiplier once to the qualifying settled win. Do not multiply direct sun payments again unless the loaded rules explicitly include them in the x3 treatment.

For an audit, list base paytable value, number of matching lines, Wild substitution and the displayed feature credit. If the result panel provides only the final value, ask support whether the x3 was already included before performing manual arithmetic.

Wild limits

The people-in-a-boat symbol is Wild. It substitutes for regular symbols but not for green sun, red sun or Scatter. Five Wilds are published at 1000x base bet.

Those exclusions matter in the feature. A Wild cannot be inserted into a sun event or used to create a Scatter trigger. Keep ordinary line combinations separate from counter-changing symbols even when they appear on the same grid.

Highest regular symbol

The older tattooed man is identified as the highest regular symbol, with five published at 83x base bet. This is distinct from the Wild’s own five-symbol value and the Scatter award.

Nine fixed lines make route verification manageable. Copy the line shape, then match consecutive symbols from the left. Do not connect visually adjacent artwork if it falls outside an enabled route.

Bonus Pop and Risk Game

The official page lists Bonus Pop and Risk Game. Bonus Pop availability can depend on jurisdiction and casino. If an optional paid control appears, save the quoted price, target feature and any alternate RTP disclosure before activation.

Risk Game follows a settled eligible win. Record the original line credit before the wager, then the risk amount and outcome. That chronology prevents a later decision from being confused with the reel calculation.

RTP and medium-high volatility

The 96.06% RTP is a theoretical long-run rate for the provider configuration. It does not guarantee that the x3 feature compensates for a short base-game session. Medium-high volatility is a distribution description, not a schedule for green or red suns.

The counter mechanic can encourage “one more spin” thinking because duration is unknown. Set an external time and money limit before play rather than using remaining blue suns as a reason to extend the session afterward.

Mobile display checks

On a phone, the blue-sun counter is essential evidence. Confirm it remains visible without covering the balance, stake or result. If the counter uses only colour, check whether the interface also provides a numeric or accessible indicator.

After a connection interruption, reopen round history and compare the server-settled counter sequence. An animation that was not displayed does not necessarily mean a round was skipped.

Worked counter ledger

Begin at three blue suns. Suppose spin one has no counter event: the published description implies the feature continues while a blue sun remains, so record the resulting visible count exactly. If the next event is green, add one; if a later event is red, subtract one.

Do not invent a universal “one sun consumed per spin” rule unless the loaded help explains it. The safest record copies the counter shown before and after every round. This distinction matters because promotional wording alone may not fully describe UI timing.

Separating sun payments from line wins

Create columns for ordinary line credit, green/red direct credit, feature multiplier and total. If the displayed total already contains all components, mark it as the authoritative settled figure and use the columns only for reconciliation.

Never apply the 2x total-bet sun payment as though it were a paytable multiplier on every line. It is described as a direct effect of the randomly awarded sun symbol.

Evidence pack for a dispute

Provide title, version, active RTP, currency, total stake, UTC time, round ID, trigger grid, three-sun opening state, every counter transition, x3 line breakdown, feature summary and balances. If a sun colour is hard to distinguish, include an uncropped screen and the accessible label if available.

Ask support to identify the rule version and server-side counter before and after the disputed round. A final feature total cannot explain whether a green or red event was applied correctly.

Responsible editorial handling

The game’s visual theme references a fictionalised culture. This guide focuses on mechanics and avoids treating a real community as decoration or making cultural claims unsupported by the source. Our original illustration uses an imagined landscape and objects rather than depicting people.

That editorial separation also helps readers distinguish provider marketing from verifiable rules. Theme does not alter RTP, counter arithmetic or regional access.

Counter termination edge cases

The feature ends when the displayed blue-sun state reaches its terminal condition under the loaded rules. If a red event and an ordinary line win occur on the same final spin, record both: the line can settle even though the counter then closes the sequence.

A green and red event should not be netted mentally before checking the order used by the interface. Capture the state transition exactly as displayed. If both can occur in one round, the server log should identify their application sequence and direct 2x payments.

The word “unlimited” must never be used as a financial claim. It describes a potentially extendable mechanic without a fixed opening count. Probability still governs the green and red events, and the feature has a defined ending state.

Nine-line reconstruction example

Draw the nine routes from the help panel on a blank 5×3 grid. For a disputed result, copy the visible symbols and trace each route from reel one. Stop a candidate combination at the first reel without the regular symbol or a valid Wild substitute.

Next, separate the line subtotal from sun-event payments. Apply the x3 feature multiplier where the rules and history show it belongs. Compare the sum with the settled currency credit rather than converting every number into a guessed “base bet”.

If the two values still differ, preserve the line highlight, counter and result panel in one uncropped image. That makes the support request testable without exposing unrelated account information.

Use neutral labels such as green event, red event and blue counter in the worksheet. Decorative names can be mistranslated between product versions, while colour, coordinate and round ID remain easier to reconcile. If colour alone is inaccessible, copy the symbol’s help-panel name as well.

Final assessment

Tribe’s central mechanic is an open-ended Free Games sequence controlled by blue-sun state. Green and red events change that state, while a x3 multiplier applies to Free Games wins. The correct audit is chronological.

The provider source supports the grid, nine lines, 96.06% RTP, medium-high volatility, trigger, sun rules and x3 feature. New Zealand availability and deployed settings remain live-account checks.

Official and related sources

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