Cloud Princess — three multiplier types evolve at different speeds

Cloud Princess by Hacksaw Gaming collects all wins from one spin in a Total Win Bar. Multiplier symbols activate at the end only if that spin produced at least one win. Their values are added together, then the sum multiplies the collected win.

Three multiplier types

A Normal Multiplier lands showing 2×, 3× or 4× and gains 1× with every new cascade. A Super Multiplier begins hidden, reveals an initial 5×, 10×, 15× or 20× when activated, and gains 2× per cascade. An Epic Multiplier starts at 5×, 10×, 50× or 100× and doubles after every new cascade. The provider states that a multiplier symbol can reach a maximum value of 10,000×.

Cloud Surge

Three FS scatters start ten Free Spins. Wins from each spin accumulate as a pending amount across cascades; multiplier values then add together and apply at the end of that spin. Two additional scatters add two spins and three add four.

Divine Boost

Four FS scatters also start ten spins, but this mode adds a progressive Divine Multiplier portal. Multiplier values that participate in a win enter the portal, and its total grows on later winning spins that contain more multiplier symbols. New values first increase the portal, then the updated total is added to the Total Win calculation.

A win without a multiplier does not activate the portal. Multiplier symbols without a win are not collected. The same +2 and +4 retrigger rules apply.

Evidence limits

The source supports multiplier rules but does not expose readable RTP, stake range, complete paytable or New Zealand casino availability. The 10,000× figure is a symbol-value cap, not a published game RTP or an expected result.

Settlement follows a strict order

Every paid or bonus spin first builds a Total Win through one or more cascades. Multiplier symbols grow during those cascades, but they activate only at the end of a spin that produced at least one win. Eligible values are then added together and the resulting sum multiplies the collected Total Win.

An audit should therefore maintain three columns: cumulative win before multipliers, each multiplier symbol’s final value, and the combined multiplier applied at settlement. Applying a multiplier after every cascade would misstate the provider rule.

If a spin has no win, the multiplier symbols do not activate. Their mere presence is not a cash award.

Building the cascade ledger

Save the original grid and assign each cascade a number. For every step, record the winning combination, symbols removed, replacements, Total Win increment and all multiplier values before and after growth.

The final no-win grid closes the cascade chain. Only then should the multiplier settlement be calculated. Preserve the round identifier so the chain remains one spin rather than several unrelated events.

Do not infer missing paytable values from animation. Use the deployed help and round history.

Normal Multiplier

A Normal Multiplier lands showing 2×, 3× or 4×. It gains 1× for every new cascade. Record its starting value and stable symbol ID, then add one after each verified cascade transition.

For example, a Normal symbol starting at 3× reaches 4× after one new cascade and 5× after two. This explains growth; it does not promise a particular chain length.

At settlement, include it only when the spin produced at least one win and the live rules treat it as eligible.

Super Multiplier

A Super Multiplier begins hidden. When activated, it reveals an initial 5×, 10×, 15× or 20× and gains 2× per cascade. Record both the concealed pre-state and the revealed starting value.

A revealed 10× Super becomes 12× after one new cascade and 14× after two. Do not apply Normal’s +1 growth to this symbol.

If a no-win spin leaves the symbol unactivated, do not invent its concealed value. The accessible rule does not permit reading an unrevealed number.

Epic Multiplier

An Epic Multiplier starts at 5×, 10×, 50× or 100× and doubles after every new cascade. Keep an exponential value history: 10×, 20×, 40× and so on.

Doubling is different from adding the starting value. A 50× Epic becomes 100× and then 200×, not 150×. Preserve every cascade count to verify the final number.

The provider states that a multiplier symbol can reach a maximum value of 10,000×. Treat this as a per-symbol value cap, not a game-wide maximum-win promise.

Several multiplier symbols

At spin end, add the final values of all eligible multiplier symbols. A 5× Normal, 14× Super and 200× Epic yield a combined 219× multiplier under the additive rule, not their product.

Keep symbol IDs and types beside the arithmetic. A multiplier that was visible but did not activate because the spin had no win contributes nothing.

After addition, apply the combined value once to the collected Total Win in the order shown by the live help.

Worked ordinary-spin example

Suppose a winning spin begins with a Normal 2× and an Epic 5×. Two new cascades occur. Normal progresses to 4× and Epic to 20×. Their final values add to 24×.

The ledger sums the base awards from all cascade stages into Total Win, then applies 24× once at spin end. It does not multiply each cascade separately and does not calculate 4×20.

Actual symbol values, awards and stake come from the tested round; the example demonstrates order only.

Cloud Surge entry

Three FS scatters trigger Cloud Surge with ten Free Spins. Save the trigger grid, initial counter and version. Each Free Spin has its own cascade chain and its own end-of-spin multiplier calculation.

Do not carry a multiplier symbol’s value into the next primary Free Spin unless the deployed rules explicitly show persistence. The public description focuses on values growing through cascades within a spin.

Record the feature total as the sum of completed Free Spin settlements.

Cloud Surge retriggers

Two additional scatters add two spins and three add four. Save scatter coordinates and the counter before and after settlement.

Keep retrigger counter changes separate from cascade counts. A cascade is a board refill within one spin, while an added Free Spin changes feature duration.

The public source does not state an award for one extra scatter or more than three. Do not extrapolate.

Divine Boost entry

Four FS scatters trigger Divine Boost with ten spins. This mode adds a progressive Divine Multiplier portal while retaining the spin-level Total Win and multiplier logic.

Open a separate portal ledger at feature start. Record its value before each Free Spin, every contributing multiplier value and the portal state after settlement.

The same two-scatter and three-scatter extensions apply. Keep them outside the portal calculation.

What enters the Divine portal

Multiplier values that participate in a win enter the portal. A multiplier symbol on a no-win spin is not collected. A winning spin without a multiplier does not activate the portal.

List every contributing symbol ID and value. Add new values to the existing portal according to the provider rule, then use the updated portal total in the current Total Win calculation.

This order matters: update the portal first, then apply the resulting total. Do not settle the win using the old portal value and add the new symbol afterwards.

Persistent portal versus spin-local symbols

The Divine portal persists and grows across qualifying bonus spins. Individual multiplier symbols still have values developed through their current spin’s cascades. Keep these two layers separate.

At the next Free Spin, begin a new local multiplier ledger while carrying forward only the portal total. This prevents the same symbol from being retained visually when only its value was collected.

Clear the portal when Divine Boost ends. The public rule does not support carry-over into paid play or another bonus.

Worked Divine Boost example

Suppose the portal begins a spin at 12×. A winning cascade chain ends with eligible Normal and Super multipliers worth 4× and 10×. Their 14× sum enters the portal, increasing it to 26×.

The updated 26× then participates in the Total Win calculation under the provider description. The ledger stores 12× opening, +14× contribution and 26× closing.

A later winning spin without a multiplier does not activate the portal, while a no-win spin with a multiplier contributes nothing.

Total Win reconciliation

For every spin, sum all cascade awards before feature multiplication. Compare that subtotal with the displayed Total Win Bar. Then add eligible multiplier values and apply the combined number.

In Divine Boost, show the portal update as an intermediate stage. The account history should reconcile with the final credited amount and feature total.

If the interface presents only a combined settlement, preserve that display rather than inventing component cash awards. The ledger can still document state transitions.

Interpreting the 10,000× symbol cap

The provider says a multiplier symbol can reach a maximum value of 10,000×. This limits one symbol’s displayed growth. It does not by itself establish the game’s total payout cap, RTP or probability of reaching that value.

Several eligible symbols can be added at settlement, and Divine Boost has a portal ledger. The live paytable must explain any overall cap affecting the final credit.

Do not market 10,000× as an expected or guaranteed result.

RTP, stakes and maximum exposure

The public page does not expose readable RTP, minimum or maximum stake, default denomination, volatility or complete maximum exposure. Collect these from the deployed information panel with title, provider, version, operator, currency and date.

If multiple RTP versions exist, report only the tested one. Do not combine numerical fields from different deployments.

The symbol cap and feature triggers cannot be used to calculate theoretical return.

New Zealand availability

The global Hacksaw page does not prove real-money availability in New Zealand. Verify operator country terms, registration eligibility, authenticated catalogue and successful launch.

NZD support, payments, verification and withdrawals belong to the operator. Source them separately and date the check.

A demo or portfolio card is insufficient. Do not recommend bypassing location controls.

Mobile and responsive checks

On mobile, the grid, cascade counter, Total Win Bar, multiplier values, portal total and remaining Free Spins must remain visible. Test portrait and landscape modes.

After rotation or interruption, compare the cascade stage, symbol IDs, portal value, counter, balance and round identifier with server history. Do not resume if state differs.

Controls must not obscure hidden-versus-revealed Super symbols or the final no-win grid.

Accessibility checks

Normal, Super and Epic types need labels beyond colour. Growth operations should be communicated as +1, +2 or doubling, and the hidden Super value must be announced only when revealed.

Reduced-motion mode should preserve the cascade order and final values. Keyboard focus must reach help, paytable, history and responsible-play controls.

The Divine portal should expose opening, contribution and closing values to assistive technology.

Support-ready evidence

For a multiplier dispute, provide the starting type and value, complete cascade count, expected growth and final displayed value. For a portal issue, include opening total, contributing symbol IDs and closing total.

Add operator, title, version, timestamp, stake, currency, balances and round identifier. State the exact arithmetic or state transition in question.

Never share passwords, one-time codes, private keys or seed phrases. Ask authenticated support to inspect server events.

Session controls

Epic doubling and a growing portal can make an unfinished cascade chain feel like stored future value. Those states exist only inside the active round or bonus and do not make another paid trigger due.

Set stake, spending and time limits before play. Do not increase stakes after seeing a high multiplier fail to activate.

Mechanical knowledge supports settlement review, not prediction. Use responsible-play controls and stop at the chosen boundary.

Publication checklist

• Build Total Win from all cascades before multiplier settlement.
• Activate multiplier symbols only on a spin with a win.
• Grow Normal by +1× per cascade.
• Reveal Super at 5×, 10×, 15× or 20× and grow by +2×.
• Double Epic after every new cascade.
• Add final eligible multiplier values; do not multiply them together.
• Treat 10,000× as a per-symbol value cap.
• In Divine Boost, update the portal before applying it.
• Keep spin-local symbols separate from persistent portal value.
• Verify RTP, stakes and New Zealand access from live evidence.

Editorial assessment

Cloud Princess is governed by calculation order. Cascades first build Total Win and evolve three multiplier types at different rates. Eligible final values then add together and act once. Divine Boost introduces a second, persistent portal ledger that updates before settlement.

A rigorous review records those stages without turning the 10,000× symbol cap into a payout promise. RTP, stake range, overall exposure and New Zealand access remain unconfirmed until the deployed game and operator supply primary evidence.

Version comparison protocol

Keep every verification attached to its operator, build, currency and date. When a new version appears, compare starting multiplier sets, growth operations, activation timing, scatter awards and Divine portal order individually. A changed RTP does not prove that the cascade arithmetic changed.

Archive one complete paid-spin cascade and one Divine Boost portal update with the matching help screen. These reference rounds allow later editors to distinguish a genuine rules revision from a shortened animation or a third-party summary that applied multipliers after each cascade.

If two primary sources conflict, display both dated configurations and request clarification. Do not average RTP values, merge separate stake ranges or choose the larger multiplier claim.

Practical reader decision points

Before play, confirm the live RTP, complete stake, local eligibility, payout cap and responsible-play controls. During a round, ask four mechanical questions: how many cascades occurred, what Total Win they produced, what each eligible symbol became and which combined multiplier settled the spin.

In Divine Boost, add two more questions: what portal value entered the spin and which symbol values were collected before settlement. If those six fields reconcile with history, the result can be reviewed without promotional assumptions.

After feature end, clear local and portal ledgers and apply the pre-set session boundary. A large previous Epic value or portal total is not stored value and does not alter the next paid outcome.

Arithmetic review template

For each disputed spin, write the calculation on one line: cascade awards summed to Total Win; Normal, Super and Epic final values added; portal opening plus new contributions where applicable; final eligible multiplier applied once. Compare that expression with the server credit.

This template exposes the common errors immediately: multiplying symbol values together, using a concealed Super amount, carrying an old local symbol into the next spin or activating the portal without a win. It also keeps feature mechanics separate from RTP, which describes long-run theoretical return rather than one settlement.

A symbol’s growth count is not automatically the round’s cascade count

A multiplier that first appears on a replacement grid needs its own landing boundary. The original paid grid and every later refill belong to one spin, but a symbol cannot be assumed to have received growth before it existed. Use the growth events actually assigned to that symbol by the history. The public summary does not fully resolve every simultaneous landing-and-increment boundary; this worksheet starts with explicit confirmed event counts instead of guessing one.

Suppose an invented ordinary or Cloud Surge spin has three multiplier objects. Its records say Normal N began at ×3 and received two growth events; Epic E began at ×5 and received one; Super S revealed an initial ×10 and received none. These are hypothetical observations illustrating the published operations, not a gameplay sample.

Object	Initial value, when verified	Recorded eligible growth events	Operation	Final value
Normal N	3	2	3 + 2	5
Epic E	5	1	5 × 2	10
Super S	10, only once revealed	0	10 + 0	10

If at least one win occurred and those three objects are eligible, their final values add to ×25. Giving every object the first symbol’s two-event history would wrongly change Epic to ×20 and Super to ×14, producing ×39. A shared cascade label is useful for chronology, but does not replace per-object landing and growth records.

Assume the same spin’s unmultiplied cascade awards are 0.4, 0.6 and 1 bet unit. They total two units. Under the published additive end-of-spin rule, ×25 gives fifty bet units before any separately applicable overall payout limit. It is not 5 × 10 × 10, and it is not three repeated applications of ×25. These amounts are invented arithmetic; the actual paytable supplies each cascade award and the deployed rules supply any final cap.

Check portal eligibility with two independent conditions

For Divine Boost, a winning spin and a contributing multiplier must both be present before the stored portal updates. Consider a hypothetical opening portal of ×12. A no-win spin showing multipliers contributes nothing. A winning spin with no multiplier leaves the portal inactive. If a later winning spin has verified contributing values of three and four, the stored total becomes 12 + 3 + 4 = 19 before the documented settlement stage.

The two inactive cases must not be collapsed into the same missing-data description. In the first, the visible symbol values failed the win condition; in the second, a win existed but had no multiplier contribution. A screenshot of just the portal cannot explain which condition failed. Preserve the Total Win status and eligible-object list beside it.

The portal’s ×19 is a multiplier state, not nineteen currency units already credited. Likewise, the newly collected seven must not remain as a second carried copy of the same symbol values after they have entered the stored total. On the next primary spin, begin fresh local object records and retain the portal separately. This division lets a reviewer trace a late-landing growth discrepancy and a portal-eligibility discrepancy without asserting a guaranteed feature return or transferring the symbol’s 10,000× limit into a game-wide payout claim.

Frequently asked questions

When do multiplier symbols activate? At the end of a spin that produced at least one win.

How do Normal multipliers grow? By 1× per new cascade.

How do Super multipliers grow? By 2× per new cascade.

How do Epic multipliers grow? They double per new cascade.

What starts Divine Boost? Four FS scatters.

Is RTP published in readable form? No.

Is New Zealand availability confirmed? No.

Official source

• Hacksaw Gaming: Cloud Princess

Bottom line: keep the spin’s Total Win, individual symbol values and Divine portal value as separate stages of the calculation.

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 Hacksaw Gaming, 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.