Gilles and Iseult end runs for opposite reasons. Gilles catches the attack that started before his string was over. Iseult catches the player who spends burst on unsafe ground, during a relocation, or on the wrong body. Treating both fights as a race to maintain damage hides the decision each boss is testing.
This guide covers the Early Access game through gameplay version 0.11.57863 and the August 9, 2026 mouse-stutter hotfix, 0.11.57874.1. Patch 0.11 changed Iseult’s stun-bar behavior, while earlier official notes changed boss parries and fixed several Gilles/Iseult progression problems. Exact damage, healing prices, and stun contribution can move again, so the method below uses visible cues and current-client confirmation rather than fixed health percentages.
The Tears of Metal beginner guide covers the route, Threat budget, objective priority, and Village return. Here, the map problem is already solved: the player is at Gilles or Iseult and needs a repeatable way to read the fight.
Enter with one test hit and one real punish
A boss-ready build does not need every preferred Emblem. It needs two attacks with different costs:
- Test hit: a short Strike, quick projectile, or Ally Command that can confirm recovery or identify the real target without locking the hero in place.
- Real punish: one Heavy, Finisher, Special, or coordinated army sequence that fits inside a confirmed opening.
Bring enough health to survive one failed read, keep a useful Commander or Companion alive, and decide what the remaining Coins are for before selecting the node. Do not enter with a large damage engine but no way to test whether the engine is safe. Critical health, a depleted army, maximum Threat, and an unfinished single-target loop are separate warnings; stacking them makes the same boss animation much less forgiving.
Sweep the completed battlefield before leaving it. Collect the reward already earned, check for recovery, and look at the formation. A speculative extra node is poor preparation when it removes the health or Commander that would let the player observe a second boss cycle.
Against Gilles, wait for the recovery rather than the pause
Gilles fills the camera and encourages the player to react to the first quiet moment. That pause may be the middle of a longer string. Begin outside the first swing, defend the readable contact, and watch what his weapon and body do next. A short test hit belongs after he clearly stops, not after the first impact sound.
Use this loop:
- Keep enough camera distance to see the weapon and the ground around the hero.
- Block a short, direct swing only while Block Stamina can absorb the complete exchange.
- Leave an extended string before the guard is exhausted.
- After the final motion and recovery, use the test hit.
- If Gilles remains open, spend one real punish.
- Exit immediately and rebuild the same view.
The test hit prevents a common false read: a brief stop that still belongs to the current sequence. If the short Strike is interrupted, the Heavy would have failed more expensively. If the test lands and Gilles has settled, the larger action now has evidence.
The raised weapon is an evacuation cue
When Gilles lifts the weapon for the large overhead impact, stop building the combo. The raise is not free damage time. Move outside the marked or likely impact space, keep him visible, allow the hit and recovery to finish, then re-enter.
Do not spend Dodge merely because the animation looks large if normal movement already clears the area. Preserve Dodge for a late position, a second threat, or an escape from an action that has already committed the hero. Conversely, do not hold Block through a large ground impact just to protect a combo. Guard can be a valid emergency answer to direct damage, but losing the bar inside a continuing boss string leaves no defense for the next hit.
Official patch 0.8 made boss Block Breaking attacks parryable. That creates an option, not an obligation. A current-client parry can contribute to the stun opportunity, but the safer first clear still begins by identifying which direct attack is being parried and which area effect should simply be left.
Use Gilles’s visible change instead of a memorized percentage
Some supplied pages claim exact phase changes at fixed health percentages, but the evidence does not reliably establish those numbers. Gilles does show a visible transformation into a more dangerous state. Use that presentation as the boundary.
Stop attacking during the transition, create room, and watch the first empowered sequence. Save the Special or strongest Finisher until one recovery has been confirmed in the new state. An animation that was safe to Block earlier may cover more space or empty the guard faster now. Re-test before reusing the old answer.
This is also where hoarded damage finally has a defined purpose. Spend it after the first readable empowered recovery, not before the transformation and not during a blind attempt to force the phase.
Move Gilles away before starting a rescue
A downed or endangered Commander creates urgency, but crossing an active slam to reach it can turn one loss into two. Pull Gilles’s facing and next impact away from the rescue point. Wait for the long recovery, then make the rescue the entire action for that window.
During ordinary resets, use Spearmen or another protected-target command to pressure Gilles while the hero takes the short punish. Archers can keep contributing while the hero exits. The army is not permission to stay in the danger area; it is a way to preserve pressure while the player gives up the unsafe second combo.
Release or loosen lock-on when Gilles hides an Archer, a ground cue, a Commander, or the route to open space. Reacquire the boss after the battlefield is readable. A camera filled by one body is a missing-information problem, not proof that every threat has disappeared.
Diagnose the first Gilles decision that failed
- Heavy begins during the wind-up: the recovery was never confirmed. Restore the short test hit.
- Block breaks during a continuing string: leave earlier or parry only the attack whose timing is actually known.
- The overhead hit lands while attacking: treat the raised weapon as an immediate stop signal.
- The army disappears off-camera: widen the view during resets and clear the nearest interruption before returning.
- The rescue consumes the health bar: move Gilles away and dedicate a later recovery window to the rescue.
- The transformed state erases the saved build: observe its first string before spending burst.
Iseult runs a four-step confirmation cycle
Iseult’s fight is easier to read when damage and observation are separated. The cycle is:
- Ground: leave Erupting Earth or another unsafe lane before preserving any combo.
- Movement: keep the camera wide and let Iseult finish relocating.
- Identity: touch a candidate body with the shortest safe attack and watch the main boss health bar.
- Commitment: spend one direct combo when the health-bar test succeeds and the return lane remains open.
If one step is missing, the Special stays saved. This removes two expensive errors at once: hitting a clone and firing at a target that is still moving.
Leave Erupting Earth before choosing a target
When the ground becomes unsafe, abandon the current attack and move into a lane that still has an exit. Do not cross the hazard merely to keep Iseult in reach. The next useful action is determined by where the player can stand after the effect, not by where the boss was when it began.
Keep enough screen space to track both Iseult and the smaller enemies that could interrupt the next check. Wait until relocation ends. A direct Special sent during movement may consume the resource without proving whether the target was real or reachable.
Block Stamina is better saved for direct contact from the boss or nearby soldiers. The ground mechanic is solved through position. If a later patch changes the exact presentation, the current red/unsafe area and movement cue take priority over the name used here.
Test the clone with the main health bar
Approach one candidate from open ground and use the shortest available hit. Watch the main boss bar, not the damage-number cloud and not lock-on behavior. If the bar does not respond, leave and test the next reachable target. Heavy, Finisher, and Special remain unused until a hit produces the expected boss-health response.
This test is deliberately cheap. A wrong candidate costs one quick input rather than the whole burst window. It also exposes a different failure: if the real body is found but the route back crosses unsafe ground, identity is confirmed but commitment is still denied.
In two-player co-op, one player performs the checks and calls the real body. The second removes nearby pressure and preserves burst. Sending both players toward different candidates divides the army and makes neither result easy to read.
Patch 0.11 changed the Banshee stun calculation
Official version 0.11.57863 increased the effect of damage on Iseult’s stun bar, reduced the contribution from parries, and slowed the bar’s decay. That means an older plan built around repeated parries should be rechecked. Parry the direct attack when the timing is reliable, but use confirmed direct damage to advance the current stun opportunity.
Do not convert that change into blind aggression. The stun bar decaying more slowly gives the player permission to preserve a safe cycle. Leave the ground effect, find the real body, land the direct sequence, and carry that progress into the next clean opening. Damage that misses a clone or is interrupted by the terrain contributes nothing.
Clear only the soldiers that corrupt the next check
Nearby enemies can consume defensive effects, hide the health-bar response, or force the hero across Erupting Earth. Remove the group already controlling the lane while Iseult is unavailable or relocating. Do not chase every distant fodder and miss the next boss window.
Area builds are useful here because the crowd can be thinned without abandoning the boss task. Brienne can spread Burning and use a safe Combust payoff around the tested target. Wallace can use Vortex or an army command to hold interruptions while saving the slow Heavy for the confirmed body. Against the boss itself, keep direct damage available; a build that depends entirely on fodder deaths loses its fuel when the arena briefly clears.
Give each co-op player one confirmation responsibility
Against Gilles, one player keeps the boss’s facing readable and tests the recovery while the other handles ranged pressure and rescues. Both spend damage inside the same confirmed window, then both leave. Against Iseult, one tests candidate bodies while the other protects the lane and holds Special. The real target is called before the long attacks begin.
Do not stack every Ally Command and Special on the first visible pause. Preserve one answer for the transformed Gilles sequence or the next confirmed Iseult body. If a player is downed, the surviving player stops acting as a damage partner and becomes the person who must create a safe rescue interval.
Separate a bad read from a current-client problem
Official patches have already addressed Gilles ignoring an attacker, Iseult becoming invisible or floating, boss invulnerability/stuck states, and ally damage during boss battles. The August 9 hotfix targeted sudden mouse stutters caused by the Epic Online Services overlay. If the visual cue, target, or input behavior does not match a normal failed read:
- Confirm the displayed game version and update before changing the strategy.
- For crossplay, check the official branch notice and make sure the party uses compatible builds.
- Retry the boss from a clean client session if it becomes unreachable, invincible, or visually displaced.
- Report a repeatable bug with the requested logs through the official Steam forum or in-game feedback path.
A missed punish has a readable cause: early Heavy, empty guard, unsafe ground, unconfirmed target, or no exit. A boss that cannot return, cannot be damaged after its normal state, or no longer responds to input may be a version or bug problem instead.
Current boundary and official sources
The official Steam page identifies Tears of Metal as Paper Cult’s AppID 1913120 release, dated July 22, 2026, and documents its three-act solo or four-player Early Access campaign. The displayed JPG files come unchanged from that first-party record; the Paper Cult site supplies the matching studio and campaign provenance.
Gilles, Iseult the Banshee, boss-parry changes, Banshee stun-bar balance, boss and ally fixes, and the August 9 version boundary were checked against Paper Cult’s Steam patch record. Named cues and punish methods were narrowed from a tested launch-version boss reference and compared with independent advanced-combat notes. Unverified phase percentages, fixed all-boss routes, removed Steam walkthrough claims, and trainer assertions were not used.