The official Untouchable condition is: “Finish Chapter 1 without losing a life.” Treat that wording strictly. If you lose a life, restart the attempt even when Infinite Lives or another recovery allows Story Mode to continue.
Untouchable was the rarest of FATHOM’s five public badges in the October 30 snapshot, with 4,712 total awards and a displayed 0.7% win rate. The numbers will change, but the official condition is the stable target.
Learn Chapter 1 before attempting it
Complete Story Mode normally first. A successful ordinary run identifies objective transitions, pursuit points, ending prompts, and the places where the group tends to make noise. Trying to preserve a life on a blind route adds uncertainty that practice can remove.
Watch a current Chapter 1 walkthrough only if spoilers are acceptable. Use it for visual orientation, then follow the objective text in your server. Updates can change timing or placement, and no community video can guarantee the badge logic in a later build.
Choose the ending branch before the attempt begins so the final prompt does not create hesitation. Untouchable requires Chapter 1 completion; it does not publicly require one specific ending.
Choose solo or a disciplined group
Solo gives full control over footsteps, chat, microphone sound, tool use, and the final choice. It removes uncertainty about a teammate losing a life. The tradeoff is that you must watch the route and read objectives alone.
A group can share observation, but every player adds noise and collision risk. Assign one objective reader, one route watcher, and one tool caller. Agree that any lost life ends the badge attempt unless the live game has been conclusively tested to prove otherwise.
Public badge text does not explain whether a teammate’s death invalidates your badge or whether only the local player’s life matters. A no-death group is the lowest-risk interpretation.
Protect the run with sound control
Grinsworth hears footsteps, typed chat, and microphone voice. Stop moving while planning, use one short silence signal, and avoid long calls near objectives. Muting the microphone is not enough if the group keeps walking or typing.
Choose a regroup landmark before each interaction. If someone becomes separated, return to it rather than shouting directions. Do not test Grinsworth’s voice-response feature during a badge run.
Background noise can enter an active microphone. Confirm the device and permission state before starting. If you are uncertain, disable microphone input and use planned minimal communication.
Reserve tools for known danger
Map one grapple destination before touching an objective. Save the camera flash for a close, front-facing interruption that opens an exit. Enter a locker only after gaining separation and becoming quiet.
Do not spend the grapple and flash together unless one action clearly failed. The run needs an answer for later pursuits. Extra flashes from Starter Pack can improve the reserve, but they do not replace timing.
Stronger Grapple officially reaches 50% farther and pulls 50% faster. Radar can show Grinsworth and objectives in Story. Night Vision can improve visibility. Those conveniences may help, but none changes the written requirement to avoid losing a life.
Treat passes conservatively
Infinite Lives and Survivor Bundle include life-related value, yet the official Untouchable condition does not say that recovered lives are exempt. Do not use a pass as a reason to continue an attempt after a life loss.
Radar and Night Vision work in Story and Chase but are disabled in Nightmare. Untouchable is tied to Chapter 1 completion; use the normal current Story route unless the live badge interface states another requirement.
Shove can move teammates and may clear a crowded escape, but it can also create an accidental death. A badge group should agree when it may be used.
Reset cleanly after failure
Identify the first cause of the lost life: sound, route, tool timing, visibility, blocked movement, or an objective misunderstanding. Fix one cause before restarting. A new attempt with the same uncontrolled failure is not progress.
If a disconnect occurs, do not assume it preserved eligibility. Public data does not describe reconnect behavior. Inspect the current objective and decide whether a fresh run is safer than continuing an ambiguous state.
Do not let frustration increase noise or speed. Untouchable rewards consistency. A slower run with a clear retreat and unused tool is stronger than a fast run built on recovery.
Strict attempt checklist
- Finish Chapter 1 normally at least once.
- Confirm controls, microphone state, and the intended ending.
- Choose solo or a no-death group plan.
- Name a retreat before every objective.
- Keep one active escape tool in reserve.
- Treat any lost life as a restart.
- Let the full ending and badge-award sequence complete.
If the badge still does not award after a demonstrably no-life-loss finish, confirm that Badge ID 3343823445780188 remains enabled and record the current server version and party conditions for a repeatable test.
Primary source
- Official FATHOM badge API
- Chapter 1 Guide for route preparation.