Our review process is boring on purpose, because horror games are not. A build or a walkthrough only earns its place here by surviving a routine that does not bend for deadlines.
Step one: install like a player
We download the build exactly as a visitor would, on ordinary Android phones, over an ordinary connection. If the install flow confuses us, it gets rewritten in the help pages before the build is announced.
Step two: finish the chapter
The reviewer plays the full chapter on a test phone: all four parts of Broken Things, every chase, every puzzle, every collectible note we know about. Walkthrough steps are written from that run and checked on a second run with a fresh save.
Step three: verify the story
Character and lore pages are checked against the game itself: tapes, research notes, dialogue and scenes. If a claim cannot be traced to something in the chapter, it is labelled as theory or left out entirely.
Step four: keep it current
When a new build changes a route, a puzzle or a control, the affected pages are replayed and updated. A page that describes a build nobody can download anymore is worse than no page at all.