Chapter 3 Walkthrough: The Harrowing Home

Chapter 3 is the point where Block Tales stops feeling like a straight castle adventure and starts asking for emotional boss planning. The Harrowing Home has more moving parts, more mini-boss pressure, and a final stretch where greedy damage feels good until it suddenly loses the run.

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.

Train Fight Opening Rhythm

The Bizville Train opening sets the chapter tone: quick enemies, paired threats, and fewer free recovery turns than Chapter 1. I remove one target quickly instead of spreading damage evenly. The goal is reducing enemy actions, not creating a beautiful damage chart.

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 3 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 3 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.

Manor Exploration Without Wasting Items

Telamon's Haunted Manor is easy to over-clear. I check rooms, pick up what is obvious, and avoid turning every hallway into a full farming loop. The chapter gives you enough practice naturally. Spending all recovery before the dream world is the real mistake, not missing one small pickup.

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.

Turkey and Slasher Are Different Tests

Turkey is a tempo and quest check; Slasher is a fight where nervous players overreact. Against Turkey, keep the route objective in mind. Against Slasher, preserve your stable plan. If you are swapping cards after every hit, the boss is controlling your build more than you are.

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.

Dream World Boss Order

Greed, Sorrow, Fear, and Hatred work because each boss attacks a different player habit. Greed punishes overreach, Sorrow punishes weak recovery planning, Fear punishes blind following, and Hatred punishes anyone who arrives exhausted. I treat the dream world like one extended dungeon with multiple named checks.

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.

Fear Forest Navigation Mindset

Fear is a good example of why guides should explain decisions, not just list directions. If the encounter points you one way, question it and keep track of where the safe path actually is. This mental rule matters again in later chapters when a room tries to make you rush.

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.

Hatred Survival Build

For Hatred, I want Prayer, SP Wire or Good Vibes if available, Bodyguard if the party is fragile, and one consistent damage option. The fight is not a speedrun on a first clear. It is an endurance check where one calm rescue turn can be worth more than three ambitious attacks.

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.

What Chapter 3 Teaches for Later

The best lesson from Chapter 3 is that Block Tales bosses are not all solved by the same card tier list. A card can be S-tier for a nightmare fight and merely fine in a simple damage race. Carry that flexibility into Chapter 4 and the site calculator will make more sense.

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

Why does Chapter 3 have so many bosses?

The chapter uses the manor and dream-world structure to run several smaller tests before Hatred.

Is Hatred a damage race?

Not on a first clear. Stability, SP, and recovery planning are more important than forcing burst every turn.