Quick Answer
If Seth stops near two talking girls and the mission cannot advance, treat it as a possible current game bug—not as a puzzle with a confirmed hidden solution. One Steam player reported this exact block, but the reviewed sources contain no official acknowledgement, stable restart method, confirmed trigger, or patch note. Preserve your save, document the scene, try only normal low-risk retries, and send the evidence through the developer’s official Steam bug-report channel.
Quick Answer: Do not delete a save or force a trainer. We could not independently verify a checkpoint reload, main-menu reload, waiting, approach-direction, frame-limit, or older-save workaround. Use the normal in-game retry options you can see, then report the exact block if Seth remains stuck.
Community report
The exact report appears in a Steam Community thread titled “seth has wall hacks.” Its author describes unusual visual detection, and another player says Seth became stuck near two girls who were talking, which stopped mission completion. This is useful because it identifies a visible location pattern, but it is still a single precise player report. It does not establish the task’s official name, a repeatable trigger, whether the issue is AI pathfinding or a script condition, or whether every Seth mission is affected.
Observed preview context
There is some broader context, but it must stay separate. An IGN pre-release preview observed strange stealth detection that appeared to operate through walls or floors. The preview does not name Seth and does not confirm the same mission problem. It supports only the limited statement that unusual detection behavior had been observed before release.
Safe steps to try before escalating
The evidence is too thin to promise a repair sequence. The following order is deliberately low risk and does not claim a result:
- Pause and confirm the active objective. Take a screenshot that includes the objective text, Seth, the nearby NPCs, and the surroundings. This prevents a vague report later.
- Use only the normal retry, checkpoint, or quit-to-menu options visibly provided by your installed game. We could not independently verify which of these options resets Seth, so do not describe any one of them as a fix. If you choose to retry, first make sure the game has saved normally.
- Return once without making unrelated configuration changes. Do not add unsupported launch options, overwrite a save, or alter files. A clean relaunch is low risk, but no source proves it resolves this block.
- Keep your earliest available intact save. Reading an older save may be a last-resort player choice, but we found no evidence that it bypasses the Seth issue. Never replace your only save with an untested workaround.
- Stop after a small number of controlled attempts. If the same behavior repeats, collect evidence rather than repeating a potentially broken sequence indefinitely.
What not to assume
We found no reliable source for a formal mission title, an exact map location, a mandatory approach direction, a required wait time, a frame-rate cap, or a controller/keyboard input change that fixes Seth. We also found no official patch note confirming that the character’s behavior is fixed.
That means common advice such as “walk around the girls from the other side,” “wait until morning,” “cap to 30 FPS,” or “reload checkpoint X” should not be presented as established guidance. If a player shares one of those outcomes, it belongs in a clearly labelled community thread until independently confirmed.
If it still doesn’t work
Use the developer’s official Steam bug-report route: the pinned Bug Report post directs players to the Janitor’s Office community area and asks for a clear description, device details, screenshots, and reproduction steps. State that Seth stopped near two talking girls only if that is what you observed; include the mission objective rather than guessing at the mission’s name.
Your report is stronger with: the current date and game-update state, Windows version, CPU, GPU, RAM, input method, a screenshot/video, what happened just before Seth stopped, and whether a normal relaunch changed the behavior. Avoid claiming that it is definitely an AI, wallhack, pathfinding, or story-script bug unless the developer confirms that diagnosis.
If your issue instead involves a guitar performance during a mission, use the separate guitar mission guide. If the game crashes before the mission can load, follow the not launching and early-crash guide.
Known bug or intended mechanic?
This behavior may be caused by a current game bug. The available evidence does not show that it is intended, but it also does not show an official confirmation or stable solution. We could not independently verify a reload or checkpoint workaround. Exact results may change after a game update.
The responsible editorial position is therefore a status page: it records the report, avoids invented task steps, and gives players a safe escalation path. It does not promise that normal retries will fix the mission.
Sources
- Steam Community: “seth has wall hacks” — player report of Seth blocking near two talking girls.
- Agefield High Bug Report thread and Janitor’s Office — developer’s reporting route and requested information.
- IGN preview — separate, pre-release observation of unusual stealth detection.
For a wider overview of verified school systems, visit the Agefield High classes guide and the Missions hub. For performance reports that might affect a retry, see best graphics settings for higher FPS.