Lord of the Seas: nine-step cannonball respin explained

Lord of the Seas is a five-reel, three-row Endorphina slot with 20 fixed paylines. The official page checked on 8 October 2026 publishes 96.01% RTP, low volatility and a €0.20–€200 reference stake range. Its defining mechanic stores cannonballs while a nine-step wick advances towards a free respin.

The supplier page establishes the public design, not access in every New Zealand account. It also does not convert the euro reference into an NZD limit. Confirm the loaded title, version, currency, RTP and help before treating any setting as active.

Published configuration

Field	Provider value
Grid	5×3
Paylines	20 fixed
Provider RTP	96.01%
Volatility	Low
Bet reference	€0.20–€200
Wick cycle	Every ninth spin
Cannonball capacity	Up to 9
Bonus Pop	Not listed

These are reference values. If live help shows a different configuration, preserve both sources with dates and use the loaded rules for the actual account session.

Base game and line evaluation

Ordinary wins use 20 fixed lines. The pirate ship is the highest listed ordinary symbol, paying 12.5× base bet for five, followed by the pirate at 7.5×. Save the complete paytable because these examples do not establish the value of every symbol or shorter combination.

Trace wins from the leftmost reel along the line pattern shown in help. Record total bet, any displayed line stake, symbol count and the settlement credit. A cannonball appearing on reel five is a state event; it should not be added as a cash award unless the paytable explicitly attaches one.

The public design allows a maximum of one cannonball to appear in a single spin, and it appears only on reel five. That gives a useful check: a replay that seems to show two new cannonballs needs to be compared with the pre-spin stored count and the final meter.

The two stored states

Lord of the Seas keeps two related records: accumulated cannonballs and wick progress. Up to nine cannonballs can be stored. The wick moves towards the ninth-spin trigger. These are not the same counter, and one should not be substituted for the other.

Endorphina states that both progress values are stored separately for different total-bet levels. Changing the wager can therefore switch the displayed state rather than erase or multiply it. Before altering the bet, note the current amount, cannonball count and wick position; after the change, record the state shown for the new level.

This wager-specific memory is central to an accurate review. A player returning to an earlier bet may see its earlier progress again, but that does not prove a cash balance was stored. It is feature state governed by the loaded rules.

The ninth-spin free respin

The wick burns out on every ninth spin at the selected total-bet level and triggers one free respin. At that point, stored cannonballs strike random positions on reels two, three and four. Each hit position becomes Wild for the respin.

Record the state immediately before spin nine, the stored cannonball count, every selected coordinate and the respin outcome. The targeting animation can bounce between cells, but only the final Wild positions belong in the settlement ledger.

The public page says the respin cannot retrigger itself. A cannonball or wick animation during that round should not be assumed to start another free respin. If a live build behaves differently, save the version and full round history before describing an exception.

Random Wild conversion

The middle three reels provide nine possible positions, matching the maximum stored cannonball count. Each accumulated cannonball is used to create a Wild at a randomly selected position in that area. Capture whether the interface guarantees unique positions; do not assume uniqueness unless the loaded help says so.

The important accounting question is the final Wild map, not the path of the cannon shots. Label the grid A1–E3, highlight converted cells on reels B–D, then trace every resulting line using the same 20-line table as the base game.

The free respin itself carries the line awards. Cannonballs and Wild conversions are mechanisms that form those lines, not automatically separate prizes. Add only the amounts shown in the win breakdown and transaction history.

A nine-spin audit ledger

Use one row for each paid spin at a fixed total bet. Columns should include spin number within the wick cycle, cannonballs before, new cannonball landed, cannonballs after, wick position and ordinary win. On the ninth row, add the target coordinates and respin settlement.

If the stake changes mid-cycle, close that segment and start a separate ledger for the new total-bet level. When returning to a previous level, compare the restored state with its last recorded row. This prevents apparent jumps from being mistaken for lost or newly awarded progress.

After the respin, capture the reset state. A screenshot taken only after the feature cannot prove how many cannonballs were used, so retain the pre-trigger meter and round identifier as well.

RTP, volatility and Classic Risk

The published 96.01% RTP is a long-run theoretical figure. It does not promise that collecting more cannonballs will produce a particular win, and the ninth-spin schedule does not make the respin profitable by itself. Low volatility is a broad distribution descriptor, not a guarantee of frequent positive sessions.

The supplier lists Classic Risk, potentially allowing up to 10 doubling decisions on eligible settled wins. This optional step is independent of wick progress and may be unavailable in some deployments. Declining it does not create another base spin; accepting it changes the risk attached to the settled amount.

Set time and spend limits before testing several wick cycles. A visible countdown can encourage continuing to a milestone, but the next respin is not a promise of a return greater than its cost.

Mobile and reconnect checks

On mobile, ensure the wick and cannonball count remain visible and distinguishable. Rotate the screen and open help to confirm that the 20-line map and wager-specific storage explanation remain accessible without hover. Note any meter hidden behind menus.

Test reconnect behaviour without placing an extra wager: close and reopen the game, then compare the total-bet level, stored cannonballs and wick position. If state changes, preserve timestamps and contact support with the round IDs rather than relying on memory.

Provider catalogue presence is not proof of New Zealand access. Report the operator domain, account region and observation date whenever describing availability.

Worked nine-spin example

Start at a fixed total bet with zero cannonballs and an empty wick. On each paid spin, advance the wick by the state shown in the interface and record at most one newly landed reel-five cannonball. If spins two, five and eight add cannonballs, the pre-trigger row should show three stored projectiles when the ninth spin activates the respin.

During the respin, suppose the game marks one cell on each of reels two, three and four. Record those final coordinates, not every target highlighted during the cannon animation. Draw the transformed 5×3 grid and trace the resulting combinations across the 20 fixed paylines. The settlement is the sum supported by the line breakdown and history; the three cannonballs are not three additional cash awards.

Now change the total bet after a fresh cycle begins. Photograph the old wager’s wick and cannonball state first. The new wager may show a different stored state because Endorphina describes progress as wager-specific. Returning to the old wager should be compared with the photograph, not with the meter seen at the temporary level.

This procedure also resolves reconnect questions. If the browser closes before the ninth spin, reopen the same title and bet level, then compare both counters. A discrepancy report should include the last completed round ID, previous meter, restored meter and device time. Those details give support a reproducible event instead of a general claim that progress vanished.

Common interpretation errors

• Treating the wick and cannonball meter as one counter.
• Assuming a wager change must erase progress.
• Calling a reel-five cannonball an immediate cash win.
• Counting targeting animation frames as several Wild conversions.
• Expecting the free respin to retrigger itself.
• Adding cannonballs as prizes on top of respin line wins.
• Converting the euro reference range directly into NZD limits.
• Describing catalogue presence as local availability.

Final assessment

Lord of the Seas is easier to verify than its animation suggests. Track two wager-specific states, wait for the ninth-spin free respin, record the final random Wild coordinates and reconcile the resulting 20-line wins once.

The official page supports the main configuration, nine-cannonball capacity and non-retriggering respin. The active help must still confirm the exact storage presentation, loaded RTP, currency and account availability.

Official and related sources

• Lord of the Seas 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.