Fears to Fathom: Scratch Creek Co-Op Guide

What Co-Op Changes

Scratch Creek turns the usual Fears to Fathom tension into a two-person problem. One player can see, hear, or trigger information the other does not have, so the horror often comes from incomplete communication.

Player roles

Marcus Reed and Tessa Langley.

Mode

Online co-op only; no confirmed offline solo route on the public Steam listing.

Communication

Proximity voice chat, player voice activity, NPC texts, and survivor-to-survivor texts are listed features.

Matchmaking

Duo Matchmaking is listed, so players without a friend can look for a survivor in-game.

Session Setup Checklist

Do this before starting a run, especially if one player is there for story and the other wants achievements.

1. 1Confirm both players have the Steam version installed and updated.
2. 2Test microphone input and decide whether to use in-game proximity voice, external voice, or both.
3. 3Agree on spoiler tolerance: blind run, guided run, or achievement route.
4. 4Decide who drives and who monitors phone messages during road sections.
5. 5If matchmaking, communicate intentions early so the other player does not leave mid-route.

What You Need Before Playing

Because Scratch Creek is online co-op only, the session setup matters more than in previous Fears to Fathom episodes.

• Both players need access to the Steam version of Scratch Creek.
• Both players need a stable broadband connection.
• A microphone is strongly recommended because proximity voice and separated scenes are core to the experience.
• One player should be ready to host or coordinate matchmaking before starting.
• If you are achievement hunting, decide whether the host or client performs each test action.

Best Practices During Play

Small habits prevent most co-op confusion.

• Call out every text message, locked door, new NPC name, and objective change.
• When separated, describe your room or landmark before asking the other player to move.
• During chases, use short direction words instead of long explanations.
• If one player dies, quickly identify whether it was pathing, hiding, or desync before retrying.

Known Launch Friction

Launch-window footage and community reports mention co-op sync, checkpoint frustration, and trigger confusion. These do not always mean the route is wrong.

• One player may see loading or survivor-state messages longer than the other.
• The car/trailer sections can feel awkward if players fight the physics instead of assigning roles.
• Sparse checkpoints can make the final chase feel punishing.
• Gas station or repair-shop progress may require both players to inspect the right area and regroup.