Chapter 4 Walkthrough: Excavation Exploration
Chapter 4 is a resource chapter. The enemies hit harder, the route is longer, and the Firebrand path asks whether your party can handle multiple demanding fights without rebuilding from scratch every room.
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.
Ancient Tomb Entry Checklist
I enter the Ancient Tomb with enough healing for a bad block streak and enough damage to avoid endless chip fights. The first mistake is assuming Chapter 4 is just Chapter 3 with sand. It is more demanding because it compresses travel, puzzles, and boss prep into a route that slowly drains weak builds.
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 4 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 4 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.
The Great Flocci as an Endurance Signal
The Great Flocci fight tells you whether your party can keep a plan alive when the boss refuses to end quickly. If every recovery item disappears here, stop and tune the build before pushing to the temple. The fight is a signal, not a wall to brute force.
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.
Temple Guardian and Hand Management
Temple Guardian is a target-priority lesson. The hands matter because they change the enemy action economy. I do not tunnel the center body if the side pressure is about to steal multiple turns from the party. Remove or control the part that creates the next problem.
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.
Captain Trotter Before the Summit
Captain Trotter is one of those fights where overconfidence from a clean temple run can create a sudden wipe. I keep Charge DEF or another defensive tool available and avoid spending every SP point before the last half of the fight. Strong parties still need a reserve.
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.
The Ancients Build Plan
The Ancients is the chapter final and the Firebrand check. I like a four-player setup with one defensive player, one support player, and two damage players. Aggressor can work, but only when the support plan is real. If defense is thin, Aggressor turns a strong team into a brittle one.
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.
Optional Finn McCool Timing
Finn McCool is worth doing when your Chapter 4 plan already works. I do not recommend using the optional superboss to prove a bad build is secretly fine. Defeating Finn for Aggressor is valuable, but the reward is best on players who already know when not to attack.
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.
Chapter 5 Prep After Firebrand
After Chapter 4, start building around protection and turn economy. Chapter 5 introduces Cassie, Trinity Castle, and Frostmaw pressure where one protected ally can decide the fight. Do not carry a pure damage deck forward just because it won the last chapter once.
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
Is Aggressor required before Chapter 5?
No. It is strong, but it creates risk if the party lacks recovery and defense.
What party size is best for The Ancients?
Four players is the most comfortable because roles can stay separate.