What you need to know
Official sources establish release facts and patch history. Firsthand testing establishes repeatable behavior. Community guides and reports identify useful leads, but they remain clearly labeled until reproduced. Conflicting or unsupported claims do not become facts through repetition.
INDEPENDENT FAN RESOURCE This site is not affiliated with Gator Dragon Games and does not republish game files or competitor copy.
What the status labels mean
| Label | Meaning | When it appears |
|---|---|---|
| Official | Published by the developer, an official store listing or official patch notes. | May be stated as fact, with a checked date for details that can change. |
| Developer reply | A direct developer response in an official community channel. | Useful for current intent or feature status, but not a release guarantee. |
| Site verified | Reproduced by this site's testing on a named build and platform. | Must include the tested version and exact steps. |
| Community report | A player describes an outcome or problem without official confirmation. | Presented as a lead or workaround, never as a universal rule. |
| Community guide | A third-party guide provides a repeatable process. | Rewritten in our own structure and queued for current-build retesting. |
| Unconfirmed | A claim lacks enough evidence or conflicts with stronger sources. | Kept out of factual tables until verified. |
Where changing details are checked
| Place checked | Type | Used for |
|---|---|---|
| Official itch.io page ↗ | Official | Price, direct downloads, platforms, content description, three endings and playtime estimate |
| Official Steam store ↗ | Official | Store availability, feature badges, system requirements and controller support |
| Official Steam news ↗ | Official | Hotfixes, Steam Deck status and development announcements |
| Localization project ↗ | Third-party author | Language packs, ModFramework, installers and platform-specific setup |
| Guidexon walkthrough ↗ | Community guide | First-wash action order and screenshot-supported opening flow |
| GG Guides escape article ↗ | Community guide | Escape and out-of-bounds experiments requiring version retesting |
| itch.io player comments ↗ | Community reports | Missed wash spots, resolution issues, save behavior and feature requests |
How conflicting information is handled
- Prefer a current official source over an undated fan claim.
- Keep a direct player observation as a community report rather than erasing it.
- Record the applicable build when a behavior may have changed.
- Use neutral labels such as Ending A/B/C until the game supplies confirmed names.
- Correct every page drawing from shared data when stronger evidence appears.
How other guides are used
Other guide sites can reveal a question players keep asking or an experiment worth repeating. Their prose, screenshots and unsupported mechanics are not copied. Practical steps are rewritten only after they can be compared with an official statement or a repeatable playthrough.
This keeps broad wiki-style coverage useful without turning a repeated fan claim into a game rule.
Review cycle
- Store and platform facts: recheck after an official update or storefront change.
- Mods and localization: recheck every release and after a base-game patch.
- Known issues: move to Fixed only with official notes or controlled reproduction.
- Scenes and routes: add exact conditions only after repeatable testing.
Visible reviewed dates refer to the page content, not the age of every linked community comment.