The official Endacopia Steam page states that keyboard and mouse are required and describes inspection, conversations, inventory use, mini-games and monster responses. This article explains the interaction habits that matter before a verified control table is available. It does not guess key names or map a community setup from another build.
Learn the input language
Move the pointer slowly across a room and watch for a change in cursor, highlight, tooltip or character response. Use one interaction, then observe the result before clicking again. A puzzle guide should describe the visual signal that makes an object actionable, not only the final click.
For keyboard input, check the current in-game menu or prompt. Record the displayed key, action and context. A keybinding can differ by platform settings or update, so keep the version note beside the result. If no prompt is visible, do not invent a default mapping.
Inspect before combining
Read an object description before trying to use it. Match an inventory object to a clue by shape, color, function or wording. After a failed test, return to the clue rather than cycling through every item. This makes the reason for a successful interaction clear and avoids accidental route changes.
Conversations are inputs too. Let a character finish establishing the topic before selecting an item. If the line changes after a room event, record the event and return point. A detailed dialogue route belongs under Characters or Endings, while this page should remain a spoiler-light control reference.
Mini-games and danger
Read the mini-game objective, input response, success signal and failure effect on a controlled first attempt. If failure resets safely, try one variable at a time. If the activity changes a route, use the supported save system first when possible.
The store description says Mellow can block, dodge and punch monsters. During danger, find the attack cue and escape lane before testing a nearby puzzle. Exact timing and damage values require current-build evidence and do not belong in a generic control page.
The official product page supplies the keyboard-and-mouse boundary. Public label 1.08, Steam base game AppID 2684630 and Windows-native scope apply. Use Updates when a control claim predates a current announcement.
A reliable troubleshooting pass
When an interaction seems unavailable, stop clicking and check four things in order: whether the cursor is over the intended hotspot, whether the character has finished speaking, whether the room state changed after the last action, and whether the inventory item is actually selected. Record which check solved the problem. That note is more useful than a blanket instruction to “try again.”
If the prompt looks different from a guide screenshot, compare the game version, display scale and control settings before assuming the puzzle changed. A screenshot can reveal the object while hiding the input state. Keep an exact keybinding in a guide only when it is visible in the current menu or confirmed by repeated testing.
For a mini-game, use the first attempt to learn feedback, not to chase a perfect score. Watch for a sound, animation, meter or reset that confirms success. If a monster interrupts, survive first and return to the control question after the room is safe. This separation keeps a control article durable across puzzle and combat routes.
Match the help level to the problem
If the issue is “what can I click,” give an input hint. If it is “why did the click fail,” explain the prerequisite. If it is “which key is shown,” quote the current prompt and its scope. These are different questions and should not be answered with one generic control paragraph.
Keep accessibility and display differences visible in testing notes. A small cursor change can disappear in a compressed screenshot, while a prompt can be hidden by a different window size. The durable guide tells the reader what feedback to seek, then links to the exact route only when the interaction is confirmed.