Written and tested by Diligesker Lab · Published July 25, 2026 · Reviewed July 30, 2026. Mechanical claims are checked against the current browser build, project data, or test records. Report a correction.
BLOCK SMASH TURN GUIDE
The first ten turns are best treated as an observation window, not a scripted route. Block layouts and reward offers vary. The player can still make repeatable decisions: read the starter package, test the launch geometry, watch board pressure, and choose rewards that solve the run that actually appeared.
Before turn 1: read four fields
- Starter ball: Normal, Lightning, Ice, or Poison changes the initial behavior.
- Starter relic: its trigger explains when the package creates value.
- Minimum launch angle: Iron 12°, Volt 20°, Frost 13°, Viper 15°, Fortuna 17°, and Blaze 14°.
- Penalty or limitation: the character screen states the cost beside the benefit.
These fields are more useful than a memorized “best angle.” Volt cannot take the same shallow opening as Iron, and Frost may prefer a path that revisits a frozen target rather than the path with the largest immediate hit count.
Turns 1–3: map the launch geometry
- Find a side gap or lane that can produce more than one contact.
- Watch where the balls return, because that return point affects the next launch.
- Note whether the starter effect actually triggered: missing-HP scaling, a lightning chain, freeze setup, poison state, or another character rule.
Do not judge a package from one collision. A shallow rebound can produce a long path but may be unavailable because of the character’s minimum angle. A steep path can be correct when it reaches a key block or prepares a safer return.
Turns 4–6: identify the run’s present bottleneck
| Observed problem | Question before choosing a reward |
|---|---|
| Blocks are surviving near the danger side | Does this offer improve immediate removal or control? |
| The board is crowded | Can chain, split, splash, freeze, or poison reach multiple useful targets under the current layout? |
| One durable target dominates the board | Does the build have enough direct or boss-focused damage rather than only spread? |
| The run is losing HP | Will more damage solve the next descent, or is guard/healing the safer answer? |
| The build is functioning but rewards are weak | Is a reroll or economy option worth delaying immediate power? |
The question is intentionally conditional. A chain reward can be strong on a crowded board and less useful against a lone target. A survival reward can preserve an Iron run without contributing to Bloodbound’s damage text directly.
Turns 7–10: test whether the pieces form one plan
By this point, describe the run in one sentence using only effects that are actually active. Examples: “Iron is surviving in a lower-HP range and converting rebounds into direct hits,” “Volt has enough targets for repeated chains,” or “Frost can freeze a target before the next direct hit.” If the sentence needs an effect you have not acquired, the build is still an intention rather than a working system.
A practical turn log
| Turn window | Record | Decision test |
|---|---|---|
| 1–3 | Launch angle, return point, starter trigger | Can I repeat the useful contact without exposing the board? |
| 4–6 | Surviving blocks, HP loss, first reward direction | Does the reward solve the current bottleneck? |
| 7–10 | Effects that triggered together | Is there a real synergy, or only several unrelated bonuses? |
When to break the planned theme
A run does not owe the player the rewards needed for a named build. If Volt sees few useful chain destinations, direct damage can be more practical. If Frost cannot prepare a second hit, control alone may not remove a dangerous block. If Iron is one mistake from defeat, survival can matter more than another low-HP bonus.
What success means after ten turns
- You understand the character’s starter trigger and cost.
- You know which launch angles are legal and which paths return safely.
- At least two active effects solve the same board problem.
- You can name the current weakness without pretending the run is complete.
Review after the run
Use the summary to separate execution from build structure. A good idea can still end after a poor launch, and a long run can survive through raw board control without the intended synergy. Record which effects triggered, which offers were skipped, and what reached the danger side. That creates a useful comparison for the next attempt without claiming that randomized runs should be identical.