Nazar Wishes: 20-line rules and three wish routes

Nazar Wishes by Endorphina is a 5×3 slot with 20 fixed paylines. The checked studio page publishes 96.07% RTP, high volatility and a €0.20–€180 reference range. It lists Hold and Win, Pick Game, Pile and jackpots, while the page status reads Pending.

The public description also names Jackpot Collecting and a Character Feature. These labels are navigation clues, not complete rules. A player must identify the loaded build and read its help before assigning an effect to a genie, lamp or eye symbol.

Verified configuration

Field	Provider-page value
Grid	5×3
Lines	20 fixed
RTP	96.07%
Volatility	High
Stake reference	€0.20–€180
Status	Pending

The euro range does not establish NZD limits. Save operator, game ID, currency, live RTP and total-bet increments together. Pending status is another reason not to claim universal release or availability.

Base-game payline audit

Open the line map and confirm direction, adjacency and the paytable unit. For every result, record total debit, symbol count, winning line and final credit. A large character can cover several visual cells without representing several symbols; use the grid boundaries.

If the table expresses prizes as base-bet multiples, find the game’s definition of base bet. Do not multiply the same award by line count and total stake. Where several lines pay, list each component and reconcile their sum with history.

Character and amulet triggers

The provider copy connects friendly genies, the Nazar amulet and a Character Feature. Live help should state which symbol activates each route, whether collection persists and what resets progress. Record the trigger symbol and screen reached rather than interpreting colour or animation.

A glowing eye does not make a feature more likely on the next round. If a meter appears close to completion, it still cannot justify extending a planned session. Random outcomes and persistence rules are separate questions.

Hold and Win

At entry, capture locked positions, starting respins and displayed values. After every respin, note new symbols, value changes and counter resets. If a collector gathers coins, record the grid before and after collection so each value is counted once.

MIN, MID, MAX and ULTRA labels can represent fixed multiples, configured cash values or progressive amounts. Quote a number only when current help defines its basis. A screenshot from another operator cannot establish the value in this account.

Pick Game

Save the number of selectable objects, every choice, every reveal and the stopping condition. If the interface reveals unchosen objects after settlement, label them as explanatory reveals rather than missed awards.

Choice history does not identify a better lamp, branch or jewel. The useful evidence is the chosen position, credited value and round ID. Where a jackpot is revealed, preserve its label, amount, currency and timestamp.

Pile and jackpot collecting

Pile is listed as a distinct feature. Document what fills it, the visible thresholds, corresponding effect and reset point. Costume changes or a growing treasure display are state indicators only when help says so.

For Jackpot Collecting, distinguish coin value, collector action and named award. A collection animation may move an amount already included in the feature total. Compare the component ledger with the final server credit before adding anything twice.

RTP and high volatility

The 96.07% figure is a studio reference for the checked configuration. RTP is theoretical over many rounds; it is not a session refund or a forecast of the next wish. A deployed build may disclose another value, so preserve both sources with their scope.

High volatility means outcomes may be uneven. It does not promise larger profit or reveal feature timing. Choose a standard stake that leaves enough rounds within a fixed cash cap and stop when either cash or time limit is reached.

Demo and mobile

The official page offers demo access where permitted. Demo can help locate rules, but it does not prove funded access in New Zealand or identical operator settings.

On mobile, test all 15 cells, 20-line highlights, Hold values, respin counter, Pick objects, Pile meter, total stake and history at enlarged text. A glowing effect must not hide numbers. After a disconnection, consult history before placing another round.

New Zealand scope

The product page proves that Endorphina documents Nazar Wishes. It does not prove that a particular NZ-facing casino offers it. Verify operator identity, country terms, account eligibility and authenticated lobby separately.

Do not infer access from an English page, studio logo or search snippet. Mark availability unconfirmed until the exact build appears in the account on a dated check.

Evidence worksheet

Record title, ID, operator, currency, RTP, stake, timestamp and round ID. Add line wins, trigger symbols, Hold grids, Pick choices, Pile levels and jackpot credits. This chronology gives support a reproducible case.

Redact account and payment identifiers. Never share a password, one-time code or remote access. Product rules and operator trust are distinct evidence layers.

Common questions

What RTP does the provider publish?

96.07% on the checked official page.

How many lines are used?

Twenty fixed paylines on a 5×3 grid.

Does the public page list Bonus Pop?

No. Its FAQ explicitly says Nazar Wishes does not include Bonus Pop.

Is it high volatility?

Yes, according to the checked studio page.

Is NZ availability confirmed?

No operator-level NZ availability was established.

Practical settlement example

If a character opens Hold and Win and a later symbol starts Pick, create one parent record for the paid round and child rows for both features. Store the Hold values before the Pick, list every selection, then return to the locked grid. Reconcile only the final round credit.

This prevents the Pick amount being counted once on its reveal screen and again in the Hold summary. Apply the same logic to a jackpot collection animation that repeats an already credited value.

Final assessment

Nazar Wishes has a straightforward 20-line base but several state-heavy bonus routes. Its useful review is an evidence map, not a retelling of the desert theme.

Treat 96.07% and the euro range as dated provider references. The live build, minimum account-currency debit and exact feature rules determine whether it fits a fixed entertainment budget.

Detailed pre-session verification

Begin with identity rather than artwork. The help title, provider name and game ID should agree with the lobby tile. Photograph the settings page containing RTP and currency, then return to the main screen and check that the displayed total bet matches the intended amount. A provider euro reference cannot be converted into an operator promise because increments and denominations can differ.

Next, read every feature definition once without placing a round. Write down the Character trigger, Hold starting counter, Pick stopping rule, Pile reset and jackpot basis. If help does not explain one of those items, mark it unavailable. A blank field is safer than borrowing a rule from another genie-themed game.

During play, use a simple event code: B for base line win, C for Character, H for Hold, P for Pick and J for jackpot collection. Attach those codes to the same server round ID. If a route enters another route, indent the child event instead of starting a second paid round. This preserves the difference between one debit with several animations and several independent wagers.

At session end, compare opening balance, all debits, all credits and closing balance. The arithmetic should reconcile without counting feature summaries twice. If it does not, stop and save history immediately; continuing creates more records and makes the disputed round harder to isolate.

Accessibility also belongs in the audit. The blue-eye theme uses intense light and colour, so check that text, counters and selected Pick objects remain identifiable in greyscale or with reduced brightness. A feature that relies only on blue, gold or red without a label can be difficult to follow. Report that as a usability issue even when settlement is numerically correct.

Finally, review the result against the budget, not the story. The amulet, genie and wish language cannot alter independent random outcomes. Do not extend time because a character appeared recently, and do not raise stake after a feature without profit. The safest interpretation is operational: understand the current rule, record the result and stop at the preset boundary.

A clean evidence capture

One compact record is enough when it is complete. Save the help-screen title, RTP line, selected stake, round identifier, opening balance and final credited amount in that order. Add a short note stating whether the Character, Hold, Pick or Pile route appeared. This sequence lets a reader reconstruct the event without relying on animation screenshots alone.

For a mobile session, capture the browser address or app lobby path as well. Two products can share similar artwork, while their identifiers and settings differ. If the history entry uses a different title from the help screen, pause and ask support to identify the build before making any numerical claim. Evidence quality matters more than collecting many disconnected images.

Keep the record only as long as needed for budgeting or a support enquiry, and remove account numbers before sharing it. The purpose is to verify one session, not to publish personal account data.

Official and related sources

• Nazar Wishes 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.