When a boss walls you: what to change

When a boss keeps ending your runs, work out first which of two problems you have. Either it is killing you before you learn it, or you are surviving it comfortably and it will not die. Those want opposite fixes, and mixing them up is how people spend an evening practising dodges for a fight that was a damage check all along.

The tell is simple: if you reach the second half of its health bar most attempts, the fight is not the problem — the build is. Experienced players say this about the late chapters almost unanimously, and the sentence they repeat to everyone who asks is the same one: commit to one or two artifact combos rather than spreading thin across five. A combo’s higher thresholds are where the large effects live, and a run holding two artifacts each from five different categories has reached none of those. If your runs die late, that is the first thing to change, before any dodging practice. The build workbench will show you what your current pile actually adds up to.

The answers that keep working

These are ordered by how consistently players report them, not by how clever they are.

Stand further away. This is the single most corroborated boss answer in the game. Several players, independently and about different fights, report that a wall which felt impossible on a melee weapon stopped being a fight at all once they had a ranged option — either a weapon with reach or a grimoire they could cast from across the arena. The pattern is consistent enough that it is worth treating as a rule: if a boss’s attacks are dense enough that you cannot find a window to close in, the answer is often not a better window, it is not closing in. Browsing weapons by whether they are ranged and active skills for something you can cast on cooldown is a faster fix than another twenty attempts.

Let something else hold its attention. Two separate groups of players arrived at this one on their own: companions are worth running not for their damage but because a boss busy with a companion is a boss you get to learn from a safe distance. It is named specifically as the answer for fragile builds that cannot afford a single mistake. The Companion category pays out along the way — companion damage at the low thresholds, then companion defence, then a large cut to revive time at the top — so this is a build direction rather than a single pickup.

Move faster. In one discussion where three players each gave a different answer to the same wall, the third was simply movement speed: enough of it turns a reaction you started too late into one that still lands. This is the least corroborated of the three and it is worth naming as such — one convincing account rather than several. It costs little to test, since move speed appears on costumes and artifacts you were probably going to look at anyway.

Bring damage aimed at bosses specifically. Wrath’s tenth level adds damage against bosses and minibosses, which is a rare thing in the game — most damage stats are spent everywhere. If bosses in particular are where your runs stop, that is a targeted purchase. Every talent lists what its levels give.

Dashes and ground markers

Almost every boss in the game tells you where it is about to hit by painting the ground first. The habit that separates players who clear from players who do not is that the second group dashes the moment a marker appears, and is therefore out of dashes when the attack actually lands. Wait, let the marker resolve, then move. Dash is a limited count that refills on a timer, not a movement key — why runs end on an empty dash bar is a whole habit on its own, and it is the cheapest improvement available to a new player.

Your weapon already has an answer, and it is not the dash

Each weapon carries its own defensive move: a block, a parry, a riposte, a sheathe, or in the crossbow’s case simply range. One weapon has none of them and asks you to solve everything with positioning. Which one you are holding changes what a boss even is — each weapon’s defensive answer is worth reading before you decide a fight is unfair, because a pattern that a shield walks through can be genuinely unblockable for the next weapon along, and players report exactly that mismatch: a defensive habit that carried them through one boss failing completely on the next.

The boss you are stuck on is not always the boss you get

The roster is not fixed. Players report — and this holds for the current version — that the earlier chapters can send you one of several possible bosses at the same point, while the late chapters have fixed ones. That is worth knowing for two reasons. If a particular fight is your wall, you will not face it every run, so a failed attempt is not proof you are stuck. And it means memorising one boss’s script buys you less than a build that answers a whole class of attacks.

Two fights people name most often

The chapter 2 boss generates more requests for help than any other early fight. The advice that askers report worked, and that a second player independently backed, is the ranged one above: a build with bolts or reach makes it a non-event. The more detailed suggestion offered alongside it — hold maximum distance, bank your dashes, and take your damage only in the window right after it commits to a big attack — comes from a single convincing account rather than several, so treat it as a starting plan rather than a script.

The library boss is the other. Three players answered the same request for help with three different routes, and the asker reported getting through: let companions do the work while you watch, switch to a ranged or magic build so you are never standing next to it, or stack movement speed. That three independent answers all worked is itself the useful fact — this fight has more than one legitimate solution, and none of them is “get better at dodging”.

In hard mode, part of the wall is something you bought

If you are running Root’s Retreat, read your own shard list before blaming the fight. Several shards target bosses directly: one makes every boss attack more aggressively, one stops you using potions during boss fights at all, and one makes enemies heal themselves when they hit you — a smaller share for bosses and minibosses, but enough to turn a slow build into a stalemate. Hard mode also carries a set of boss modifiers, and they are worth reading rather than guessing at: one resists a single damage type by 33%, one resists your critical chance by 30%, one ignores half your defence and another half your evasion, and one trades 20% of a boss’s health for 50% more damage. A build committed to one element meets the matching resistance eventually, which is an argument for a second damage source rather than a purer one.

What this page will not do

There is no frame-by-frame script here for any fight. The roster rotates, the developer has been actively adjusting boss patterns, warning indicators and hitboxes since release, and a step-by-step written against one version is wrong the moment it changes — several widely shared accounts of the final fight already describe behaviour that has since been patched. What survives all of that is the shape above: range, aggro, speed, targeted damage, and a build that clears the damage check. If the screen itself is the problem rather than the boss, reading a loud screen covers that separately.