Love Show: three host routes and verified game settings

Love Show by Endorphina is a 5×3 slot with 30 fixed paylines. The official page publishes 96.05% RTP, medium-high volatility and a €0.30–€150 reference range. Listed features are Hold and Win, Pick Game, Pile, jackpots and Fortune Wheel; the status is Approved.

The design centres on three fictional hosts: Amber, Goldie and Carmen. Coloured message symbols lead to different bonus routes. A reliable review maps each colour and state without treating character preference as strategy.

Verified settings

Field	Provider-page value
Grid	5×3
Lines	30 fixed
RTP	96.05%
Volatility	Medium-high
Stake reference	€0.30–€150
Status	Approved

The euro range is not an NZD limit. Confirm the account currency, increments, game ID and RTP inside the loaded help.

Base-game line rules

Save the 30-line map, win direction and paytable unit. Record total debit and every winning path. A host portrait can occupy a large graphic area without changing the number of reel positions.

If paytable prizes use base bet, locate its definition. Do not apply line count or total stake twice. Reconcile multi-line totals with round history.

Amber Wheel

Green messages activate Amber’s wheel according to the provider description. Listed multiplier segments are ×5, ×10, ×15, ×20, ×25, ×50 and ×100. Live help must define what amount the multiplier applies to.

At entry, record the triggering collection, starting award, visible wheel and final segment. A pointer passing a larger value during animation does not award it. Apply the resulting multiplier once and compare with history.

Goldie Holdie

Blue messages lead to Goldie Holdie. Each diamond can hide a regular value from 1× through 15× total bet or a jackpot. The provider lists MIN 25×, MID 50×, MAX 250× and ULTRA 1000×, with ULTRA awarded when all 15 Bonus symbols are collected.

Capture the starting grid, locked diamonds, respin or attempt counter and every new value. Add each diamond once. If all 15 positions fill, distinguish the individual values from the separate ULTRA condition and follow the live settlement display.

Carmen Pick route

The third coloured-message route leads to a Pick Game associated with Carmen. Open help for the number of choices, prize set and stopping rule. Save each selection and reveal.

If unchosen envelopes are exposed later, they are explanatory unless the rules say otherwise. Past selections do not identify a better envelope in a future round.

Pile and collection progress

Pile is listed as a core feature. Record what fills it, each visible threshold, award and reset point. A host’s progress animation does not reveal the probability of completion.

If messages persist across rounds, note whether stake changes reset or scale them. Do not assume persistence from appearance alone. A nearly complete display should not extend a fixed session.

Jackpot evidence

Goldie’s published multiples are scoped to the checked page. If the live game displays currency values, store amount, operator, currency and timestamp. Do not describe them as progressive unless help says so.

The ULTRA collection condition is a feature rule, not a prediction. Missing one diamond does not make the final position due on the next attempt.

RTP and volatility

The provider publishes 96.05%. RTP is theoretical over a large sample and cannot predict the next message colour or bonus. Preserve the live build’s disclosure separately.

Medium-high volatility means outcomes may be uneven. Use a fixed cash cap, time limit and ordinary stake. Do not raise stakes to reach a host route or recover a loss.

Demo and mobile

Official demo access can explain controls where permitted but does not prove real-money NZ availability. Check the mode label and help.

On mobile, test all 15 cells, 30-line highlights, message counters, wheel segments, Hold values, Pick envelopes, stake and history at enlarged text. Colour-coded routes should also have icons or labels.

After connection loss, use server history. A replayed host animation is not evidence of a second credit.

New Zealand scope

The provider page establishes product documentation, not operator-level New Zealand availability. Verify casino entity, country terms and authenticated lobby independently.

Do not infer local access from an English interface, studio logo or marketing image. Mark availability unconfirmed until directly observed.

Audit worksheet

Record title, ID, operator, currency, RTP, stake, timestamp and round ID. Add message colour, collection count, route entered, wheel segment, diamond values or Pick choices and final credit.

Use one parent row for the paid round and child rows for nested states. This prevents the same award appearing once on the route screen and again in the final summary.

Common questions

What RTP is published?

96.05% on the checked official page.

How many paylines are used?

Thirty fixed paylines on a 5×3 grid.

What are the three main routes?

Amber Wheel, Goldie Holdie and Carmen’s Pick route.

What is Goldie’s listed ULTRA condition?

Collecting all 15 Bonus symbols, with 1000× total bet listed on the provider page.

Is NZ access confirmed?

No operator-level availability was verified.

Worked three-route record

If green and blue messages advance in one round, note both counters separately. When Amber opens first, settle the wheel multiplier before returning to the base state. If Goldie then activates, start a diamond-grid child record and reconcile it at feature end.

Do not let one host’s multiplier modify another route unless current help explicitly connects them. A shared final celebration can repeat the combined amount without creating an extra credit.

Responsible interpretation

The dating-show narrative encourages preference and anticipation, but neither changes random outcomes. Choosing a favourite host is entertainment, not a way to improve return. Use session tools, reality checks and account limits where offered.

For a disputed result, share round ID, time, currency and redacted history with support. Never disclose credentials, one-time codes or payment PINs.

Final assessment

Love Show is a 30-line game whose main complexity comes from three clearly themed feature routes. Its best review keeps Wheel, Hold and Pick evidence separate.

Treat the provider RTP and euro range as scoped references. The live account settings and enabled routes determine whether the game fits a fixed entertainment budget.

Message-counter verification

Before the first paid round, identify the icon and label attached to each message colour. Create three columns—Amber, Goldie and Carmen—and record the starting counters. After each round, note only the counters that changed. If a message flies across the screen but the counter does not advance, preserve the animation and final state rather than assuming a missing collection.

When a route triggers, save the counter immediately before transition and after returning to the base game. This establishes whether progress resets, carries over or changes with stake. Never test persistence by increasing the wager beyond the session plan.

Route-specific arithmetic

For Amber, write the pre-wheel amount and selected multiplier. Multiply once, then compare with history. For Goldie, list every diamond value and jackpot in its cell, followed by the all-15 completion condition when applicable. For Carmen, list selected envelopes and their revealed values in order.

If two routes occur inside one server round, create separate child totals and one parent settlement. A final “show total” may already include both. Adding each route and the summary without reconciliation would triple count part of the result.

Editorial treatment of characters

The three hosts are fictional interface elements, not reviewers, advisers or indicators of probability. Describe only the rule each host represents. Avoid suggesting that a personality, clothing colour or preferred host improves outcomes.

The presentation should also remain respectful and age-appropriate. The game is restricted to adults, but its review does not need sexualised language. Readers need feature logic, limits, accessibility and evidence—not commentary on appearance.

Mobile accessibility test

At 390 pixels wide, verify that the message counters, total stake and current win remain on screen. Open each route in demo where permitted and test the wheel pointer, diamond values and envelope choices with large text. Focus indicators and close controls should remain reachable by keyboard or assistive navigation.

Because the routes use green, blue and another colour, check for icons or written host names. A colour-only interface can fail readers with colour-vision differences. Screenshots should capture both the colour and its accompanying label.

Session review and support

At the end, compare planned limit with actual debits rather than feature count. A session containing all three hosts can still be a net loss, while a session with no feature is not evidence that one is due. Stop at the boundary regardless of counter position.

For support, state title, operator, round ID, time zone, currency, message counters and route involved. Send redacted history through the verified support channel. Never provide credentials, one-time codes or remote access, even when someone claims it is required to investigate a feature.

Official and related sources

• Love Show 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.