Candy Glyph — charge five power-ups through tumbles

Candy Glyph by Quickspin is a 7×7 cluster game with tumbles. After a winning cluster, one Candy Wild can be awarded in an empty position. Removing that Wild charges the current power-up.

Verified configuration

The official game sheet lists a 96% RTP, volatility three out of five and a 35.92% hit frequency. These are long-run model descriptors, not a prediction for a session. Confirm the active help in the deployed game before play.

Five-feature sequence

Five power-ups are selected for the sequence, with the final one always being Free Spins. A charged power-up executes on a non-winning screen, so the resolution may occur after the tumble chain ends rather than immediately when the Wild disappears.

Bouncy Bean adds four to ten random Wilds. Lollipop Rocket removes one low-paying symbol type, while Bonbon Bomb removes a row and column of normal symbols. The official rules state that each symbol removed by the Rocket or Bomb pays 1/20 of the bet.

Bonus Piñata

Bonus Piñata awards nine Free Spins, with three more spins on a retrigger. The Piñata persists and moves between spins, and its multiplier can reach x99 under the documented rules.

The provider page mentions a 13,000x maximum. Treat that as a cap or simulated potential, not an expected result.

Mobile and evidence checks

The mobile layout should keep the full 7×7 grid, active power-up, Wild charge and remaining Free Spins readable. Preserve the Game ID and before/after screens when checking a removed-symbol payment.

Shields of Lambda provides a useful comparison: both use clusters and tumbles, but its Unity meter persists by bet level, while Candy Glyph progresses through a selected five-feature sequence.

Cluster wins on a 7×7 field

Candy Glyph uses 49 grid positions and cluster evaluation rather than fixed paylines. Identify matching symbols connected under the active adjacency rule and store their coordinates before removal.

Winning cluster symbols disappear, replacements tumble into the empty cells and the grid is evaluated again. One paid round can contain several cluster states.

Label the original state C0 and later tumbles C1, C2 and onward. Save each cluster, award and removed coordinates. The final board cannot explain the earlier sequence.

Do not import Shields of Lambda’s saved collection meter. Candy Glyph advances through charged power-ups instead.

Candy Wild award after a win

After a winning cluster, the game can add one Candy Wild to an empty position. The official rule caps the addition at one per tumble.

Record the empty cell chosen and the current power-up. A Candy Wild is not automatically a cash award; it must be removed in a later winning cluster to charge the active feature.

If the new Wild participates immediately in another cluster after replacements settle, store its removal in that next tumble state. Do not count the placement itself as a charge.

Charging the active power-up

When a Candy Wild is removed as part of a winning cluster, it charges the currently selected power-up. Mark the power-up name, charge event and grid state.

The feature does not necessarily execute at the exact moment of removal. The rules state that a charged power-up resolves on a non-winning screen, after the tumble chain ends.

This delay is important. Preserve the charge during all continuing wins, then apply the effect only when the first no-win state arrives according to the history.

Five-feature sequence

The game selects a sequence of five power-ups. Store their displayed order at the start or as each becomes visible. The fifth position is always Free Spins.

The first four positions can contain the documented non-bonus powers. A feature advances after its charge and execution under the active rule. Do not assume the same ordering in every paid round.

Use a sequence table with slot number, power-up, Candy Wild placed, Wild removed, charge state and execution result. This turns a long animated chain into a verifiable record.

Bouncy Bean

Bouncy Bean adds between four and ten random Wilds. Record the number and coordinates actually delivered. The range does not mean every event adds ten.

Those Wilds can participate in cluster evaluation after the feature resolves. Store the resulting grid before any new tumble so their contribution can be traced.

Do not treat Bouncy Bean Wilds as five separate power-up charges unless Candy Wild rules and history explicitly identify them as chargeable symbols.

Lollipop Rocket

Lollipop Rocket removes one low-paying symbol type from the grid. Identify the selected symbol, number of cells removed and resulting payment.

The official rule states that each symbol removed by the Rocket pays 1/20 of the bet. Multiply the unique removed-cell count by that unit. Do not use the removed symbol’s ordinary cluster paytable value.

After removal, replacements can create clusters and further tumbles. Keep the Rocket payment separate from those later cluster awards.

Bonbon Bomb

Bonbon Bomb clears a row and a column of normal symbols. Mark the intersection and count unique removed normal-symbol cells; the crossing cell exists once, not twice.

Each eligible symbol removed by the Bomb pays 1/20 of the bet under the source. Special symbols excluded by the rule should not be added to the count.

Store the payment before replacement symbols tumble in. Any clusters formed afterward are separate awards.

Other selected power-ups

Where the active sequence displays another documented power-up not fully described in the extracted summary, use the live help for its exact targets and payment. Do not infer it from the candy artwork.

Record its name, charge, delayed execution and resulting grid using the same sequence table. This preserves completeness without inventing a rule.

The official source remains the authority for feature variants. If a later version changes the available pool, date the Game ID and update only that title.

Free Spins as the fifth power-up

The fifth charged position is always Free Spins. Once its Candy Wild is removed and the tumble chain reaches the execution state, Bonus Piñata begins.

This is a power-up progression trigger rather than a Scatter count. Preserve the five completed sequence positions and the transition counter.

The source awards nine initial spins. Store nine as the starting count before any retrigger.

Bonus Piñata movement

The Piñata persists through the bonus and moves between spins under the documented feature. Record its position at the start and after every move.

Its location matters to the game effects shown on the 7×7 field. Use coordinates rather than describing it only as left, centre or right.

The moving Piñata is feature state, not an extra wager. All bonus spins belong to the initiating round.

Piñata multiplier

The multiplier can increase under the Bonus Piñata rules and reach up to 99×. Record the value at the start of each spin, changes during the spin and closing value.

Do not apply the final 99× headline to earlier awards. Every cluster should use the multiplier shown for its own settlement stage.

The 99× value is a feature ceiling, not a guaranteed destination. A nine-spin bonus can end with a lower multiplier.

Free Spins retrigger

The documented retrigger adds three spins. Record the event, counter before addition and counter afterward.

A retrigger extends the current Bonus Piñata; it does not restart the five-power-up sequence. The Piñata and multiplier continue according to the live rules.

If multiple retriggers occur, store each separately under the same server round.

Removed-symbol payments

Rocket and Bomb both pay 1/20 of the bet for each eligible symbol they remove. Keep the fraction as an exact rule and calculate the subtotal from the unique cell count.

For example, removing eight eligible symbols produces eight units of 1/20, or 8/20 of the bet, before any later clusters. This illustrates arithmetic only and does not predict a feature result.

Do not round intermediate values prematurely when the account currency supports smaller units. Compare the final displayed credit with the game history.

RTP and model checks

The official sheet lists 96% RTP, volatility three out of five and hit frequency 35.92%. Record the deployed Game ID and help value rather than assuming every casino uses the same model.

Hit frequency does not mean a profitable result on that proportion of spins. It counts events under the provider’s definition and is separate from long-run return.

The source summary supplies one RTP model. Do not invent lower alternative rows based on patterns in other Quickspin titles.

13,000× product maximum

Quickspin’s product page mentions a 13,000× maximum. Treat it as the title’s stated cap or potential and verify the exact wording in the live paytable.

The cap does not forecast a result and is not connected to power-up progress. A charged fifth feature does not make the maximum due.

Operator-level payout limits remain separate account terms and should not be inserted into the game rule without a source.

Full Candy Glyph worksheet

Start with operator, title, Game ID, RTP, currency and stake. Record the 7×7 initial grid and every cluster tumble.

Add the five power-up order. For each Candy Wild, record placement, removal, charged feature and delayed execution. For Rocket or Bomb, count eligible removed cells and 1/20-bet units.

During Bonus Piñata, record remaining spins, Piñata coordinate, multiplier and retriggers. Reconcile the complete round with the server ledger.

Mobile review

On a phone, verify that all 49 cells, current power-up, charge status, Piñata position, multiplier and remaining spins remain readable.

Open a completed round in history to confirm that delayed power-up execution is represented. A screenshot taken when the Candy Wild disappears does not show the later feature result.

Colourful effects should not be the only way to identify Rocket, Bomb or Bean. Names and values should remain available in the help.

Product and market scope

Quickspin establishes the grid, power-ups, RTP and Bonus Piñata rules. It does not establish New Zealand casino availability, NZD stakes or operator withdrawals.

Confirm those commercial facts separately. Label the candy-temple image as editorial artwork and keep Candy Glyph distinct from Shields of Lambda by recording the exact Game ID and source date.

Power-up execution after a non-win

The delay between charging and execution deserves a separate event record. When a Candy Wild is removed, mark the feature “charged” but leave its result blank while the tumble chain continues.

At the first non-winning grid, record the power-up execution, affected cells and payment. Then determine whether the resulting transformation creates a new cluster and resumes tumbles. This sequence can alternate between ordinary wins and feature effects within one paid round.

Do not execute the feature immediately in a hand calculation simply because the Wild disappeared. Applying it too early can change the grid and create clusters the server never produced.

Tracking sequence advancement

Number the five power-up positions S1 through S5. A position advances only after its charge and resolution are complete under the game history. Record the next active power-up before another Candy Wild is awarded.

The sequence order can make identical Candy Wild events produce different outcomes. A Wild removed while Rocket is active is not equivalent to one removed while Bean is active.

Because S5 is always Free Spins, the worksheet should show four completed earlier positions before Bonus Piñata entry. If the live history shows another path, preserve the Game ID and check for a version change.

Cluster adjacency audit

Draw the 7×7 board and label rows 1–7 and columns A–G. Trace every winning cluster using the adjacency defined in the help. Mark unique cells removed and the location selected for any awarded Candy Wild.

A large cluster can touch another same-colour group diagonally without joining it if diagonal adjacency is excluded. Let the server highlight settle the boundary rather than merging groups by eye.

After replacements fall, start a new grid record. Do not carry an old connection into the next tumble merely because similar colours appear nearby.

Piñata state example

Suppose Bonus Piñata begins with nine spins and a displayed multiplier at its starting value. Record the Piñata coordinate and meter before spin one. If it moves and the multiplier increases, store both changes after settlement.

If a retrigger occurs, add three to the remaining count and continue the same state table. Do not reset the multiplier or return the Piñata to its original coordinate unless the live rule does so.

This example describes state management only. It does not predict movement, multiplier growth or retrigger frequency.

Checking the 1/20-bet arithmetic

Use the actual base bet defined by the paytable, not the total account balance. Divide that bet by twenty to obtain the unit for each eligible Rocket or Bomb removal.

Count unique normal-symbol cells. For a Bomb’s row-and-column cross, subtract the intersection from a naive row-plus-column total because the same position cannot be paid twice unless the history expressly does so.

Keep this fixed removal payment separate from cluster paytable awards created after replacement symbols arrive.

No unsupported feature buy

The source summary used for this page does not establish a direct feature-buy price. Do not insert one from another cluster game or from a third-party lobby.

If a deployed version displays a buy control, record its name, price, RTP and starting Piñata state from the live help before adding it to the article. Until then, progression through the fifth charged power-up is the verified route described here.

Source revision procedure

Save the retrieval date for both Quickspin’s product page and the linked sheet. If a later version changes the power-up pool, multiplier cap or maximum, preserve the old Game ID and document the revision.

Do not blend two versions into one feature list. The active help for the round determines which sequence and payments apply.

Internal comparisons with Shields of Lambda should remain conceptual—cluster grid versus meter—not a source for Candy Glyph values.

Final editorial and ledger checks

Read the completed page against one round worksheet. Every charge, delay, feature execution, cluster and bonus state should have a defined place. Remove any paragraph that merely repeats a general casino warning without helping this calculation.

At settlement, compare the accumulated cluster awards, fixed removal payments and Bonus Piñata results with the round-specific ledger credit. Do not rely on a main balance that can change through other activity.

Verify the hero asset, alt text, internal links, FAQ and official URLs. Run word-count and duplicate-paragraph audits before marking the page complete.

Frequently asked questions

What is the grid size? Seven reels by seven rows using cluster wins.

How many Candy Wilds can be added per tumble? The official rules say a maximum of one.

What is always the fifth power-up? Free Spins.

How many Bonus Piñata spins are awarded? Nine initially, with three on a retrigger.

Is Candy Glyph confirmed at New Zealand casinos? No. The provider source does not establish local operator availability.

Official sources

• Quickspin: Candy Glyph
• Official game sheet

Bottom line: track when the Candy Wild is removed, which power-up is charged, and when that feature actually resolves.

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 Quickspin, 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.