Choose the result you need. Every guide below owns a complete player task, its current evidence state, and a clear success signal.
Unified live status: 0/3 verified - Needs Recheck. Historical evidence remains dated even when its current workflow is Verified.
Start here
Confirm the official destination and published premise before testing a mechanic.
Start by confirming the official experience and learning the three published risk conditions. Use the first-session path to choose one bounded next step without assuming unsupported controls or rewards.
Task path
Choose the specialist guide for one attempt or the walkthrough for broader progression.
Choose one of the three Roblox-published conditions and watch for a bounded success signal. The demonstrated route is dated evidence, so timing, distance, and current-build behavior still depend on freshness.
Use an evidence-bounded route from joining the official game through an abstraction attempt and recovery. The optional Caine and Cellar portion remains explicitly historical and must follow its current freshness label.
Risk management
Use the three published risks cautiously; unpublished Sanity math remains unknown.
Use the published risk conditions as a conservative checklist for reducing exposure. Exact Sanity rates, thresholds, and recovery speed remain unknown even when the dated workflow is still current.
Dated route
This route is preserved as Historical evidence rather than a permanent current mechanic. Check its workflow freshness before organizing two player roles.
Review the dated two-role sequence, visible checkpoints, and recovery path before attempting it. Treat the route as Historical evidence and use its current workflow freshness instead of assuming it still works.
Recover first
Diagnose a failed result before retrying. Check Updates when live and dated evidence diverge.
Start with the visible symptom and follow the shortest bounded recovery order. Record the server, live build, and failed checkpoint before repeating a workflow that may need recheck.
Compare the live game timestamp with dated evidence and affected workflows. A Needs Recheck label means the current build is not being summarized as verified until the task is reproduced again.
Evidence choice
Prefer official premises first, then dated verified observations, and treat reported claims as questions. Freshness tells you whether a demonstrated route still matches the live build.
Compare exactly three risk conditions published in the official listing. Unverified fourth-method claims stay separate, and the live core status determines whether dated route evidence needs another check.
Catalog reported secrets, glitches, and leak-video claims with evidence grades. YouTube ALL SECRETS montages and competitor tier lists stay Reported—not official mechanics.
Score 4th–6th-way videos, tier lists, and glitch myths as Official, Reported, or Unverified. Entertainment TRUE/FALSE edits are not site evidence.
