Sugar Glider by Endorphina: original and Dice expanding-Wild guide

Sugar Glider and Sugar Glider Dice use five reels, three rows and 10 paylines. Endorphina publishes 96.03% RTP, medium-high volatility and a €0.10–€200 supplier bet range for both. Their central mechanic is a praying-mantis Wild that spreads over adjacent positions.

The original uses colourful nature symbols, while Dice reframes the set around dice. One canonical page prevents those cosmetic variants from becoming near-duplicate reviews.

Verified comparison

Field	Sugar Glider	Sugar Glider Dice
Grid	5×3	5×3
Paylines	10	10
RTP	96.03%	96.03%
Volatility	Medium-high	Medium-high
Bet reference	€0.10–€200	€0.10–€200
Wild	Praying mantis	Praying mantis
Risk Game	Listed	Listed

These are supplier specifications checked on 8 October 2026, not proof of New Zealand availability or operator limits.

Ten paylines, not ways

The 5×3 display is evaluated on ten fixed routes. A matching cluster beside the mantis is not automatically payable; the resulting symbols still need to follow a valid line. Open the overlay and number the routes before auditing the spread.

In the original edition, Endorphina identifies the cute cat as the top ordinary symbol, paying 100× base bet for five. The live paytable is required to interpret “base bet” and to confirm the Dice symbol hierarchy.

How the praying-mantis Wild should be audited

The provider says the mantis Wild substitutes for regular symbols and spreads over adjacent positions. “Adjacent” needs a coordinate-based reading. It may mean orthogonal neighbours, diagonal neighbours or a predefined pattern; only the active help and result animation can establish the precise footprint.

Capture the grid before the spread if possible. Mark the original mantis cell, then shade every transformed cell. List the ten paylines that intersect those positions and reconcile their credits with history.

Do not call the mechanic expanding across a whole reel unless that is what the loaded rules say. Do not assume transformed cells stay for another round. Spreading, expanding and sticky are different behaviours.

Original versus Dice presentation

The original surrounds the glider and mantis with fruit and forest imagery. Dice replaces much of that symbolic vocabulary with dice while retaining the published grid, lines, RTP and volatility. The comparison therefore focuses on readability rather than inventing mathematical differences.

On a small screen, check whether each die face remains distinct and whether the transformed positions have more than a colour-only cue. In the original, ensure decorative foliage does not obscure the line highlight.

Save each edition’s exact title and version. A matching marketing page does not prove that two operator builds share the same internal revision.

Risk Game and the absence of a public free-spin claim

Both provider pages list a classic Risk Game. Treat it as an optional post-win branch and record it after the base round has settled. The amount risked, choice, outcome and final balance belong in a separate ledger row.

The cited core-feature sections list Wild and Risk Game; they do not advertise a Scatter-triggered Free Games mode. Do not import free spins from another forest-themed slot. If a live build adds a promotion or side feature, name its source and version.

RTP and medium-high volatility

The 96.03% RTP is a theoretical long-run rate. It does not predict the next mantis or guarantee that a spread creates a win. Medium-high volatility suggests uneven outcomes but cannot define a personal budget.

Set monetary and time limits before starting. The €0.10–€200 range must not be converted into a claimed NZD range without operator evidence. Read the total stake, not only coin value.

If help shows another RTP, keep the provider figure as a reference and report the live value separately. Never average configurations.

Mobile and demo checks

Use portrait and landscape modes to test visibility of all fifteen cells, stake, balance and line highlights. Trigger the help panel and verify that its close control remains accessible after system zoom. Round history should retain the pre-spread or settled grid in a form support can identify.

A provider demo helps users locate the mantis and learn the line map. It does not establish legal or commercial availability in New Zealand, nor does a demo balance equal money.

A coordinate worksheet for the spread

Label reels A–E and rows 1–3. If the mantis begins at C2, write C2 in the “origin” column and every changed coordinate in the “spread” column. Then add the line numbers that use each replacement. This makes the feature review reproducible.

Avoid counting one transformed symbol twice when two paylines cross it; paylines are separate awards, but the cell remains one event. Conversely, do not merge two different line awards simply because they share the same mantis origin.

For Dice, add the original and resulting pip values. For the original, add the fruit or character name. Both records should end with the numerical credit from history.

Operator-support checklist

Include edition, game version, active RTP, UTC timestamp, round ID, total stake, original Wild coordinate, transformed coordinates, line highlights and balance movement. Ask support to confirm the server-side Wild footprint.

If the animation appeared incomplete because of a connection drop, do not replay from memory. The server record and completed history are the evidence.

Testing the meaning of “adjacent” without guessing

Use a blank 5×3 coordinate grid and place the initiating mantis in the centre at C2. There are four orthogonal neighbours—C1, C3, B2 and D2—and four diagonal neighbours—B1, B3, D1 and D3. The live animation and help should show which group can transform. Do not assume all eight merely because they touch the centre visually.

Repeat the observation when the mantis lands at an edge or corner. A symbol at A1 has fewer possible neighbours, so the footprint may be clipped. Record whether the game compensates, relocates the origin or simply transforms fewer cells. One centre example cannot answer that boundary condition.

After the spread, freeze the settled grid and count valid combinations only along the ten published lines. A transformed cell outside every winning route can still demonstrate the feature, but it does not create a separate payment. Conversely, one transformed cell may contribute to several line awards.

For a fair original-versus-Dice check, use the same coordinate notation even though the artwork changes. In the Dice build, add the face visible before and after transformation. In the original, name the replaced fruit or character. This lets the two event logs be compared without relying on screenshots alone.

If two mantises land in one paid spin, establish whether their footprints are evaluated simultaneously or sequentially. Overlapping transformed cells should not be counted twice unless history reports distinct feature credits. Preserve each origin and the final union of changed positions.

The public provider wording establishes that spreading occurs; it does not answer every edge case. Mark unobserved cases as unknown instead of filling them from a review of another build. This distinction is especially important when an operator deploys a later version.

Reading the absence of Scatters correctly

The official summary for these editions foregrounds Wild and Risk Game rather than a free-spin package. That makes the mantis transformation the primary gameplay question. It also means a reader should not search indefinitely for an undocumented bonus symbol.

Open the current paytable and verify the complete symbol list. If no Scatter appears, write “not listed in this version” rather than claiming the game can never be revised. If an operator adds a promotional free-spin award outside the game, identify it as an operator promotion, not a Sugar Glider reel mechanic.

This separation keeps RTP discussion coherent: an external promotion may change the player’s cost basis, but it does not rewrite the published slot configuration.

Version-control notes for future checks

Save the page title, date, version and RTP together rather than keeping an undated screenshot of the forest. If Endorphina later changes the adjacency description, the earlier record will show which wording applied at the time of a reviewed round.

For editorial updates, revise the original and Dice columns independently. Matching specifications today do not guarantee permanent parity. Add a change note only when a primary source or loaded help supplies the new fact.

Readers should also distinguish device behaviour from game rules. A slow phone may display transformation frames late, but the completed grid and server history determine settlement. Capture those numerical records before reporting a mechanics fault.

Final assessment

Sugar Glider’s useful analytical question is precise: how does one mantis Wild change neighbouring positions, and which of the ten paylines benefit? The Dice edition changes the visual language but not the headline specification published by Endorphina.

The official pages support 96.03% RTP, medium-high volatility and the shared grid and stake reference. Availability, exact adjacency, currency and active configuration still require live confirmation.

Official and related sources

• Sugar Glider official product page
• Sugar Glider Dice 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.