Start by reading the current instruction, identifying the action it asks for, and using the corresponding control. If you miss something, try to work out what you missed before changing several things at once. That is a useful approach to a first run without needing a walkthrough open beside you.
This Suzy Says beginner guide keeps later events, puzzle solutions and ending routes out of the article. It focuses on getting comfortable with the game and knowing when to ask for a small hint.
Before your first Suzy Says session
Suzy Says is MOONBIT’s Windows horror game, built around an interactive DVD and an activity mat inspired by Simon Says. The developer documents three movement controls: WASD to move, Space to jump and C to crouch. The official listing also warns of flashing lights, jump scares and unsettling themes.
If you still need the game, use our Suzy Says download and version overview. The rest of this article assumes you have chosen a copy and are ready to learn by playing.
Our suggestion is to give yourself a first attempt without a full walkthrough. You can always look up a particular problem later. It is harder to forget an ending or a reveal once a video thumbnail has shown it to you.
Put the controls within easy reach
The controls below come from the developer’s listing. The practice ideas are suggestions for becoming familiar with those keys, not extra rules imposed by the game.
| Input | Documented action | What to practise when you have room |
|---|---|---|
| W, A, S, D | Move | Make a short, deliberate movement rather than holding a direction while reading. |
| Space | Jump | Find the key by touch so you do not need to look away to locate it. |
| C | Crouch | Notice where C sits relative to your movement keys. |
For other interactions, use the instructions displayed in your copy of the game. Do not borrow an interaction key from a different horror title just because its controls feel familiar.
There is no need to turn this into a long rehearsal. The aim is simply to avoid confusing “I could not find the key” with “I did not understand the request”.
Read the whole instruction before guessing
The developer frames Suzy Says around listening and following rules. For a first attempt, a useful habit is to separate understanding an instruction from carrying it out.
Ask yourself:
- What action is being requested? A movement instruction and an object interaction need different responses.
- What does the current prompt actually say? Use the wording on screen rather than your memory of the previous request.
- What feedback did I receive? Look for the game’s response before deciding what went wrong.
This is a way to organise your attention, not a promise of a safe response window. It does not establish an exact delay, a universal command sequence or an exploit. Follow any timing cues the game itself provides.
Knowing the party game Simon Says gives you context, but it is not a substitute for reading this game’s instructions. Let the current prompt guide your next action.
After a mistake, change one thing
A confusing moment can make it tempting to press several keys, move somewhere else and try another action immediately. That makes it difficult to tell which part of your response mattered.
On your next opportunity to try, focus on the part you were least sure about. Did you misread the instruction? Use a different key from the one you intended? Lose track of where you were looking? Narrowing the question gives you something concrete to observe.
If you take a note, keep it short and factual: “I used Space while the instruction was still on screen” is more useful than “jumping is broken”. The first describes an event. The second assumes a cause you may not yet have established.
A failed attempt by itself does not prove that you encountered a bug. Equally, a technical problem is not automatically a puzzle. Use what you can actually observe.
Get a hint without reading ahead
If you decide you want help, ask about the smallest problem that is stopping you.
A useful request might be: “Spoiler-free help, please. I do not understand what this prompt is asking me to do.” Include the prompt only if you are comfortable discussing it, and say that you do not want later events explained.
For a video, check the chapter labels before opening a section. Titles such as “all endings” or “full story explained” are a warning that the answer may reveal more than the immediate problem. Even comments beneath an otherwise useful clip can give away later scenes.
You do not need to choose between struggling alone and reading the entire solution. One small hint can be enough to return to your own run.
If the problem looks technical
Keep a distinction between uncertainty about an instruction and trouble running the program.
| What you notice | A useful next step |
|---|---|
| The game runs, but the request is unclear | Re-read the prompt or ask for a narrowly scoped hint. |
| A control seems unresponsive | Check the documented key and note exactly what you tried. |
| The application freezes or closes | Record any error message and when it happened before looking for support. |
| Your download or purchase is missing | Return to itch.io and your purchase information. This fan site cannot access orders. |
Before deleting files or reinstalling, consider whether you need to preserve anything and check for instructions from the developer. This guide does not verify save-file locations or recovery procedures.
A final check before you begin
You are ready for a first attempt when you know where the movement keys are, can recognise the current instruction and have decided how much outside help you want.
There is no route or ending to memorise here. Keep your attention on the next request, observe the response, and use a specific hint only when you need one.
Return to the Suzy Says homepage for the official download link and edition details.
Sources and scope
Game premise, documented controls and content warning: MOONBIT’s official Suzy Says listing, checked 15 November 2026.
The practice, note-taking and help-seeking suggestions above are editorial advice. This article is not a report of a hands-on playtest and does not verify command timing, puzzle solutions or ending requirements. Suggest a correction.