Sublustrum Beginner Guide: October Playtest Preparation

What should I check before starting?

Confirm that you installed the remake playtest, rather than finding a walkthrough for the 2008 original. Steam access instructions explain the October testing window. Compare your PC with the official requirements. The advertised performance targets are not a benchmark of your machine.

The developer says the test covers Chapter One. A trailer can show areas outside that playable slice. Do not plan your session around an assumed full campaign or a route copied from Outcry.

How can I keep useful exploration notes?

Use a short observation log. Record what you see and hear before deciding what a mechanism means. These are suggested session habits, not a verified room-by-room route.

Record	Useful detail
Your location	A room name visible in the game, or a clear description
Object or document	The visible label and the clue you actually read
Action	What you changed, and its starting state
Feedback	A sound, prompt, light or movement after the action
Open question	What you still need to establish

Changing one thing at a time makes it easier to separate a clue from an unrelated sound. Revisit a document using the inventory UI when a mechanism appears to refer to it. The developer’s October 2 notes describe revised inventory scrolling and document navigation; exact bindings should be checked in your installed build.

What if an interaction seems to do nothing?

Look for both visual and audio feedback, and compare the result with your notes. The developer acknowledges that some earlier interactions did not communicate a successful action clearly enough. That history makes it worth documenting an apparent blocker, but it does not establish that every unsolved puzzle is a bug.

For device-specific context, open Echophone hints. Avoid repeatedly applying an old numeric answer: the original-versus-remake comparison explains why that can mislead you.

How do I report a useful blocker?

Include your build if visible, hardware, location, actions already tried and what you expected to happen. Distinguish “the prompt never appears” from “I do not know the solution.” Add a screenshot or a short recording if the official feedback channel accepts it. Mark puzzle details as spoilers.

The developer links a feedback form inside the playtest and directs puzzle conversations to the playtest discussion hub. This fan guide does not operate that hub.

Sources and verification limits

• October 2: closed playtest results — controls, interactions, feedback and inventory changes.
• October 5: open playtest announcement — test scope and official feedback route.
• Steam store: app 4151300 — current product identity.

This page is source-based preparation. We have not independently tested every control or verified a complete Chapter One route.