Grinsworth is the named monster hunting players in FATHOM. The official experience description says he climbs walls, crawls through vents, hears footsteps, chat, and microphone voice, and can talk back when players speak to him. The official Radar pass also names him directly and says the radar can show his position in Story and Chase.
Those facts define a mobile, sound-reactive threat. They do not provide a fixed hearing radius, patrol route, memory timer, or chase speed. Survive by controlling inputs and keeping an escape route rather than relying on an unsupported number.
Prevent detection before a chase
Stop moving while deciding what to do. Footsteps are a confirmed signal, so circling an objective or pacing in a locker area creates risk without progress. In a group, let the route watcher decide when everyone moves.
Keep chat and microphone calls short. Use a landmark, direction, or tool status instead of narrating the whole scene. If someone wants to test Grinsworth’s voice response, do it in a run where the group accepts the risk rather than during a badge attempt.
Inspect vertical approaches. A corridor may look safe while a wall or vent gives Grinsworth another line. Do not stand directly beneath an opening while reading a long objective, and turn around before interacting so the retreat is familiar.
Read pursuit and choose one answer
When Grinsworth appears, move toward the route you already identified. Avoid improvising through teammates or into an unseen corner. The goal is not to use every tool; it is to create enough distance or interruption to reach a reset point.
Use the grapple for movement when the destination is valid and visible. Use the camera flash when Grinsworth is facing the camera and the interruption creates a real exit. Use a locker after gaining separation and becoming quiet.
Do not assume a wall, vent, or locker has a permanent safety timer. The exact behavior needs current testing. Watch the threat’s movement and sound feedback in your server and be ready to leave only when the route is clear.
Manage a group around Grinsworth
One player should call the threat direction, and one should call the retreat. Everyone else should avoid adding competing voice instructions. After a silence signal, stop both speech and typed chat.
Spread out at doors and turns. If the chased player needs to grapple or enter cover, teammates should not fill the same space. Players who are not pursued can protect the objective area and regroup point instead of following Grinsworth into the same corridor.
Radar may help its owner track Grinsworth in Story and Chase, but the product description does not say the display is shared with the whole team. Communicate only the useful direction and do not make the radar owner responsible for every decision.
Use passes without confusing them with AI rules
Radar officially shows Grinsworth and needed items or objectives, but it is disabled in Nightmare. That limit means Nightmare players need environmental awareness rather than relying on the overlay.
Night Vision improves dark visibility but does not say it changes Grinsworth’s ability to see or hear. Stronger Grapple changes reach and pull speed, not the monster’s pathfinding. Infinite Lives changes the player’s life supply, not the Untouchable condition.
Shove can move teammates and still works in Nightmare. It may clear a blocked path, but an uncontrolled shove can also send another player into danger. It is a player-spacing tool, not a stun against Grinsworth unless the live game explicitly demonstrates otherwise.
Recover after Grinsworth catches the team
Identify the first error, not the final scare. Did footsteps reveal the group? Did voice continue after a silence signal? Was the retreat unknown? Was the flash used at the wrong angle? Did players block a doorway? Choose one correction for the next attempt.
Return to the location calmly if the mode allows it. Walk the retreat without pressure, identify one grapple destination, and choose where a flash would produce useful distance. If a locker is part of the plan, agree that the group goes silent before reaching it.
For Story, inspect the current objective after a life loss or reconnect. For Untouchable, treat any lost life as ending the attempt even if the run continues. Public badge data does not grant exceptions for passes or teammates.
What the public record does not prove
There is no first-party public value for Grinsworth’s hearing radius, volume threshold, chat keyword behavior, pursuit memory, patrol randomness, camera-blind duration, locker search chance, or mode-specific speed. Videos can show one build and one server but should not be converted into permanent statistics without repeatable tests.
Nightmare is confirmed to exist by pass descriptions, yet those descriptions only establish that Radar and Night Vision are off while Shove works. They do not establish Grinsworth’s exact Nightmare behavior.
A repeatable survival checklist
- Read the objective and stop moving while planning.
- Inspect the return route, walls, and vents.
- Agree on one silence signal.
- Keep a grapple route or camera flash available.
- Let the pursued player own the escape line.
- Regroup before returning to the objective.
This checklist remains useful when an update changes positions or values because it responds to the behaviors the developer actually confirms.