Chapter 1 Walkthrough: Storming the Castle

Chapter 1 teaches the real rhythm of Block Tales: walk into a new room, read the enemy pattern, block instead of panic-healing, and save burst for the boss turn that matters. I treat Storming the Castle as the first build checkpoint because the game stops letting a random card pile carry every mistake.

Fast Clear Notes

Bring one reliable damage card, one recovery card, and one card that protects a bad turn.
Do not treat the boss as a pure damage race until you know the danger turn.
Use the calculator after picking the target boss, then adjust for mechanics the score cannot see.

Start at the Cave Exit, Not the Castle Door

The route becomes easier if you treat the cave exit as your first inventory checkpoint. Buy or save enough recovery for two bad fights, equip one damage card, and leave one slot for defense. Running straight into Blackrock Castle with only attack habits creates the same failure loop: you win small fights quickly, then reach the throne room with no plan for long turns.

My practical test for this section is simple: if the plan still works after one missed block, it is a real route and not a highlight clip. For Chapter 1 Walkthrough, I favor repeatable choices over perfect-turn assumptions because most players are clearing the chapter while learning enemy timing.

The route note I care about most is whether a normal player can repeat the advice without a perfect inventory. For Chapter 1 Walkthrough, I assume one missed block, one imperfect card slot, and one player who needs a turn to recover. If the plan only works when every attack lands and every guard is clean, it belongs in a speedrun note, not in the main guide.

A good route also protects player attention. If the advice asks you to memorize too many exceptions before the next door, it is probably overbuilt. I keep each section tied to one decision: what to equip, what to save, what to block, or when to stop attacking.

Snowy Thicket Teaches Guard Timing

Snowy Thicket is where I slow down and practice blocks against predictable enemies. The goal is not farming; the goal is leaving the area with confidence that a one-damage hit can stay one damage instead of becoming a panic heal. If your guard timing feels inconsistent, take one extra normal battle before moving on.

When a player asks whether to swap cards here, I look at the lost turn first. If the loss came from running out of SP, add turn economy. If it came from a low-health ally, add recovery. If it came from a boss staying alive too long, then add damage.

I also compare the fight to the previous chapter so the build change has a reason. A card that was enough against the last boss may become weak when the new boss adds status, multiple bodies, or a protected ally. This is why the guide does not tell you to carry one favorite loadout through all five chapters without checking the mechanic.

This matters for Block Tales because the game teaches through mistakes. The fastest improvement usually comes from naming the mistake, not from grinding until the same mistake is hidden by higher stats. The walkthrough keeps those mistake labels visible.

Banished Knight and Killbot Pressure

The Banished Knight and Spiky Killbot fights punish players who spend every SP point as soon as it appears. I use Power Stab for confirmed windows and keep one defensive answer ready. If a fight has adds, remove the low-health target first so the enemy side gets fewer actions next turn.

This is also where party size changes the answer. A two-player route needs compact cards because every support turn removes half the party's offense. A four-player route can dedicate one player to safety and still keep damage moving.

For party play, I call out role separation because it prevents argument during the fight. One player owns recovery, one owns defense, and damage players wait for their window instead of draining SP early. That small agreement often improves clears more than another card swap because it fixes the decision timing, not just the inventory screen.

I also avoid treating wiki knowledge as a substitute for a route. A name, location, and HP number can identify a boss, but they do not tell a player how to spend the next turn after a bad block. These sections focus on that next-turn decision.

Blackrock Castle Room Order

Inside Blackrock Castle, the important habit is checking the next room before spending your last good item. The castle route has enough encounters to drain sloppy players, but not enough to justify grinding for an hour. Move carefully, break crates, and treat every staircase as a chance to reset your card plan.

I avoid calling any route mandatory unless the mechanic demands it. Block Tales gives enough card flexibility that a calm defensive build can clear fights that a louder damage build keeps losing. The best card is the one that fixes the next failure point.

For solo or two-player clears, the same advice has to compress. You cannot dedicate a whole player to support, so defensive cards become valuable only when they protect more than one future action. That is the difference between a cautious build and a slow build: the cautious build buys a real turn, while the slow build merely delays the wipe.

If you are playing with friends, read the relevant boss section out loud before the pull. A ten-second role check prevents the common problem where two players heal the same target while no one blocks the next threat.

Sentient Statue Checkpoint

Sentient Statue is less about raw damage and more about proving that you can survive a boss-sized enemy without burning the whole bag. If your party is two players, have one person commit to defense and one to damage. If you are soloing with a follower, keep the same idea: one action creates safety, the next creates progress.

For repeat attempts, write down the turn that actually caused the wipe. Most failed clears do not fail at the final HP bar; they fail three turns earlier when a player spends the only safety action on unnecessary damage.

When I rerun a route, I write down the first turn that felt unstable. The visible loss may happen later, but the real failure usually starts when SP drops too low, a heal lands one turn late, or a player attacks into a danger pattern. Fixing that earlier turn is the reason these walkthroughs focus on pacing instead of only final-boss HP.

If you are playing alone, use the same logic in a smaller loop. Decide your safety card before the fight, decide your burst card before the fight, and do not change both after one unlucky turn. One stable change is easier to judge.

Cruel King Build Before Entry

Before Cruel King, I want Power Stab, Charge or another tempo card, and a way to absorb mistakes. The king fight can feel unfair if you chase damage every turn. It becomes manageable when you accept that some turns are guard turns, some turns are setup turns, and only a few turns are burst turns.

If a detail is still uncertain, I mark it as a route note instead of pretending it is a datamined number. That keeps the guide useful during the Chapter 5 freshness window without turning estimates into fake certainty.

The calculator is intentionally a planning tool, not a replacement for watching the boss. If the score says a damage card is efficient but the fight keeps killing Cassie, the score is not wrong; it is answering the wrong question. In that case the guide overrides the math and moves protection higher.

The Chapter 5 freshness window makes this discipline more important, not less. New pages often rush to be first and forget to be useful. I would rather publish fewer claims and update them than fill the guide with confident guesses.

Post-Fight Cleanup and Chapter 2 Prep

After the chapter clear, do not immediately rewrite the whole build. Keep the reliable damage card, then add status planning for Chapter 2. The next chapter asks different questions, but the lesson from Cruel King stays useful: clean blocks and resource pacing beat a pretty card list.

After the fight, keep the lesson and drop the overfitted card. A boss-specific answer can be perfect for ten minutes and wrong for the next area. That is why this guide links back to the calculator and the card meta page instead of freezing one universal loadout.

This page will stay useful after balance changes if the reasoning is visible. A patch can change a number, but it rarely removes the core problem of a fight: status pressure, action economy, burst timing, or ally protection. I keep those labels in the text so future updates can replace details without rewriting the route from zero.

After each route, I keep notes for the calculator. If a card repeatedly saves a bad turn, its turn-economy value deserves to be high. If a card only looks good in a perfect clip, it stays out of the default recommendation.

FAQ

What level should I be for Cruel King?

Level 4 is a comfortable target for a normal clear, but guard timing matters more than one extra level.

Should I farm before Chapter 1?

A short cleanup loop is fine. Long farming is usually worse than practicing blocks and fixing cards.