Chapter 4, Challenge 6: the full checkpoint route

Chapter 4 Challenge 6 is the one most players ask about: a progressive challenge built around the film's babysitter night, with checkpoint kills in a fixed order — Annie, then Bob, then Lynda, then Laurie's confrontation. Fail a checkpoint's conditions and the challenge quietly stops progressing even though the chapter itself continues, which is why so many "it didn't count" reports trace back here. Reported

This is part of the story mode chapter flow — if you haven't cleared Chapter 4 in general yet, do a clean run first so you know the layout.

The checkpoint route

1. 01

   Annie — the car. Wait for her sequence to reach the car before committing. Entering too early is the classic failure; the timing details have their own guide in Annie's car sequence.

2. 02

   Bob — the kitchen. Let him separate from Lynda and come to you. The kill needs to happen away from Lynda's line of sight or the alert state can break the next checkpoint.

3. 03

   Lynda — upstairs. The phone moment. Approach only after she's engaged with the phone; an early approach can trigger an alert that voids the stealth condition.

4. 04

   Laurie — the confrontation. This checkpoint is a scripted confrontation rather than a stealth kill. Follow the prompts; the challenge credit lands when the sequence completes.

What fails the run

• Killing a target out of order — the challenge tracks sequence, not just completion.
• Triggering a full alert before a stealth checkpoint (Bob, Lynda). Reports agree alerts matter; they disagree on exactly how much alert is tolerated. Unverified
• Entering Annie's car sequence early — see the dedicated timing guide.

Retry checklist

Before you re-run, check each of these — they cover nearly every failed attempt we've seen reported:

• Restart from the chapter start, not mid-checkpoint, so the tracker state is clean.
• Confirm the challenge is actually active in the challenge screen before playing.
• Take the checkpoints slowly — this challenge rewards patience over speed, and there's no timer condition in any credible report.
• If the run was clean and credit still didn't land, it may be the tracking bug rather than your play — see challenges not counting.