Book of Vlad family: the original and Dice version compared

Book of Vlad family by Endorphina is documented as a 5×3 game using 10 lines, with 96.04% provider RTP and high volatility. The checked reference stake is €0.10–€45; its official page is marked Approved and lists Wild, Risk, Bonus Pop, Free Games and Scatter.

That source record does not prove an operator listing in New Zealand, a local-currency range or an identical live configuration. This review keeps published rules separate from deployment facts that must be read inside the exact build.

Provider settings

Field	Checked value
Grid	5×3
Evaluation	10 lines
RTP	96.04%
Volatility	High
Bet reference	€0.10–€45
Status	Approved

The status belongs to the supplier page, not to an operator or player account. Save the title, product ID, help version, account currency and total debit before using this table. If live help differs, it governs claims about that deployment.

Main feature rules

Both official pages publish the same grid, RTP, volatility and euro range. The Book is Wild and Scatter. Three or more Books trigger seven Free Games with expanding bloody symbols. Any non-Scatter symbol can gain expansion capacity when its accumulator fills. Each blood drop refills one cell of the matching accumulator; every activated accumulator adds two Free Games at the original bet and lines, then switches off.

Treat every bonus as a child of one paid parent round. Record the trigger once, then number each state change. A running feature display and a final summary may represent the same money; transaction history is the settlement anchor.

Symbols and paytable

The original uses character and horror symbols; Dice uses ruby-set dice. Matching non-Scatter symbols must be on enabled lines and adjacent reels from the left. Scatter and line wins are added.

Keep base-bet, line-bet and total-bet units attached to every value. A large symbol animation does not prove a pay; the grid, evaluation rule and official paytable must all support it.

Feature-specific evidence plan

First record whether the title is Book of Vlad or Book of Vlad Dice and save its product ID. During Free Games, keep one counter per eligible symbol, note every blood drop, the accumulator it fills, activation, two-spin addition and reset.

What distinguishes this game

The original Book of Vlad and Book of Vlad Dice belong on one comparison page because the official records publish the same core grid, line count, RTP, volatility, stake reference and accumulator framework. They must not, however, be treated as one executable file. The opening record needs the exact title and product identifier so a screenshot from the character edition is never used to explain the dice edition.

Once the build is identified, the accumulator is the central evidence. Create one row for every eligible non-Scatter symbol and mark its empty cells before the feature begins. Each blood drop should be assigned to the matching row, then checked against the on-screen fill. When an accumulator completes, record the chosen expanding symbol, the two added Free Games and the switch-off or reset state. That sequence explains the feature far better than a single image of an expanded reel.

The Book’s dual Wild and Scatter role also deserves a separate note. Scatter awards and ordinary line wins can be added, while non-Scatter line matches still need enabled lines and adjacent reels from the left. Reviewers should not count an expansion as a valid line without checking those rules. For players choosing between the two editions, the meaningful difference is presentation and symbol recognition, not a claim that one published framework pays better. Compare readability on the intended screen, confirm the loaded help, and keep the seven-spin starting count distinct from later two-spin accumulator additions.

Capture the state before it clears. A chronological record is more useful than a collection of final screenshots because it shows which rule changed the counter, grid or multiplier.

RTP and volatility

The 96.04% figure is a theoretical long-run provider setting, not a forecast for one session. A short sample cannot validate it, and another certified integration may load a different option. Save the live percentage beside the source date.

High volatility describes outcome distribution, not timing. No feature becomes due after a quiet run. Visible collection progress must not change a money or time limit chosen before the session.

Mobile and demo checks

A provider demo can help locate rules where age, location and site policy allow access. It does not establish real-money availability in New Zealand and may not share the operator build or wallet settings.

On mobile, verify the whole 5×3 grid, total debit, remaining counter and feature values in portrait and landscape. After backgrounding the browser, compare the round ID so a resumed animation is not recorded twice.

New Zealand boundary

The provider page alone does not show that Book of Vlad family is offered to an identified NZ account. The euro range is not an NZD minimum or maximum. Operator eligibility, game access, currency and current terms require separate evidence.

Supplier approval and operator permission answer different questions. If access cannot be documented, label it unconfirmed. Never recommend a location workaround for a blocked or missing title.

Before the round

Create a Book of Vlad family configuration note with title, ID, 5×3 layout, 10 lines, 96.04%, currency and total stake. Use a help-screen capture, not a lobby thumbnail, because artwork can remain after a software revision.

Read the settlement order before play. Identify which symbols trigger, which values use base or total bet, whether extra rounds can be won and whether a maximum-win rule terminates the feature. Missing information should stay marked unavailable.

During the round

Record only events that change the rules: qualifying symbols, accepted tokens, locked cells, cascades, counter changes, accumulator fills or multiplier activations. Decorative effects are useful orientation but not settlement evidence.

Keep sequence numbers. Start with the paid grid, then feature state one, state two and so on. When two mechanisms occur together, state which resolved first according to help instead of choosing an order that gives a preferred result.

After settlement

Save the transaction entry before placing another round. Opening balance minus one debit plus the credited result should reconcile with closing balance if no other activity occurred. Do not add a feature total again if history already includes it.

If a discrepancy remains, preserve local time, time zone, game ID, configuration screen and the relevant grids. Remove personal and payment data before contacting support and never send a password or authentication code.

Worked audit method

Suppose Book of Vlad family enters its main feature. Write the debit once and mark the triggering positions. Apply the game-specific plan above, keeping printed values in their original unit. At completion, compare the final feature summary with the wallet transaction rather than estimating from animation.

If the app disconnects, stop. Reconnect once and inspect whether the same round is complete, interrupted or resumed. Repeated reloads and further paid rounds can erase the clean boundary needed for support.

Comparison criteria

A useful Book of Vlad family comparison asks whether the live minimum debit fits a preset entertainment budget, whether rules are readable on the intended device, whether history exposes stable IDs and whether optional controls disclose their price. Headline maximums do not answer those questions.

Compare like units only. A regular symbol stated in base bet is not directly comparable with a feature award in total bet. Fixed-currency values should remain in the displayed currency unless a documented conversion is explicitly needed.

Optional controls

In Book of Vlad family, Risk or Bonus Pop, where listed, is optional and can vary by jurisdiction. Record the original win before entering Risk. For a purchase control, record price, starting state and RTP treatment from the same live help. If the control is absent, report it as unavailable for that checked build rather than calling the game faulty.

An optional control does not improve the underlying certainty of a result. Its cost belongs inside the same session limit. Do not treat a purchased entry as separate from the planned expenditure.

Common questions

Is 96.04% guaranteed everywhere?

No. It is the checked provider value. The loaded help is required for a deployment-specific statement.

Does €0.10–€45 apply in NZD?

No. It is a euro reference. The eligible account must confirm local currency and limits.

Does a demo prove operator availability?

No. It can show controls but not operator access, account eligibility or an identical configuration.

Should visible progress change a stopping point?

No. Progress artwork does not make a random outcome due. Stop at the chosen budget and duration.

Final assessment

Book of Vlad family should be treated as an identified software build, not a thumbnail. The provider page establishes a dated baseline, live help supplies deployment rules and transaction history supplies settlement evidence.

Label units, preserve one parent round and record each state once. Presentation never overrides the stopping plan.

Official and related sources

• Book of Vlad family official source
• Book of Vlad Dice 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.