Death Order: Simon Says officially supports editable controls through Settings → Mobile HUD Editor, PC Keybinds, Controller Binds. The developer description says you can rebind or rebuild every one. Use that flexibility to keep the prompt visible and make one clean action; do not copy an exact button map that may differ by device, Roblox client, or later update.
Direct setup: open Settings in a safe area, choose your input section, move or bind one action, save it, test press and release, then continue. Never rebuild the entire layout during an active Simon command.
Actions your layout must support
Prioritize movement, camera, jump, crouch, sprint, interact, and any current combat or Event action. Each input should be reachable without covering the command text or forcing you to release movement at the wrong time.
Test both press and release. A jump that works is not enough if a movement control remains held after your finger leaves it. A crouch toggle and a hold-to-crouch behavior require different habits. Use the live action label in Settings rather than assuming a guide’s terminology matches your current menu.
Leave one reliable interaction input for beds, chairs, NPC conversations, tables, doors, or trade panels. Do not bind it so close to jump or combat that one press can trigger the wrong action.
Mobile HUD setup
Place the movement control where your thumb naturally rests and keep the command area unobstructed. Separate jump, crouch, sprint, and interact enough that you can identify them without staring down. The important measure is not symmetry; it is whether you can read the full prompt while your fingers find the intended action.
Resize buttons only as much as needed for reliable contact. A huge transparent button can overlap another control or capture touches near the prompt. A tiny button can fail under pressure. Test the layout by walking, stopping completely, jumping once, crouching once, interacting once, and rotating the camera without accidental movement.
If the HUD feels wrong after editing, rebuild from a simple layout: movement on one side, camera space on the other, frequent actions around the camera thumb, and rare actions away from the central view. Save before queuing.
PC keybind setup
Use keys you can reach without leaving movement for long. Check for duplicate assignments and operating-system shortcuts. If two actions share a key, decide whether the game treats them as contextual or conflicting before relying on the bind.
Keep interaction distinct from jump and crouch. Location tasks often end at a usable object, so a mistaken jump can waste the final second. Put any Event-specific or combat action where it can be reached without moving the mouse away from camera control.
Mouse sensitivity should let you scan a stairway or arena without losing the prompt. Test a controlled half-turn and return to the original view. Extremely high sensitivity can turn a route correction into disorientation; extremely low sensitivity can hide a hazard behind you.
Controller bind setup
Confirm movement and camera sticks, then check jump, crouch, sprint, interact, and current combat actions. Watch for stick drift by releasing both sticks in a safe area. If the character moves or the camera continues turning, use available dead-zone settings, reconnect the device, or test another controller before attempting a no-movement command.
Avoid assigning a critical action to a button that is uncomfortable to hold while moving. If sprint uses a stick click and causes camera or movement instability, move it to a reachable shoulder or face button when the current bind menu allows it.
Prompt icons may change when the active input device changes. Disconnect duplicate controllers or stop touching the mouse if the Roblox client rapidly switches displayed prompts. The action name is more reliable than memorizing a platform icon from an older video.
Safe control test
Run this test after a Roblox client update, device swap, or full HUD rebuild. Do not assume a saved layout loaded correctly until the character demonstrates it.
Controls for common commands and Events
For “Don’t Move,” release character movement completely; camera movement may be separate, but avoid experimenting during a valuable run. For location orders, combine camera and movement without hiding the destination. For Obby, prioritize predictable jump timing and centered landings. For Split Second, use one deliberate input rather than mashing. For Duel, confirm the current weapon controls only after selection.
The guide does not publish a fixed default key table because the official feature is rebinding and the exact defaults can differ across clients. Use the current Settings labels as the source of truth.
Troubleshooting
If a bind does not save, close the menu normally, reopen it, and check the displayed action. If input prompts flicker, disconnect unused devices. If mobile touches miss, reduce overlapping transparent controls. If movement continues after release, test in a safe area and resolve drift or held input before returning to a round.
Reset only when you cannot isolate the problem. Take a screenshot of a working layout before a full rebuild so you can recover button positions without guessing.
Frequently asked questions
Can every control be changed?
The official description says mobile HUD, PC keybinds, and controller binds can be rebound or rebuilt. The exact options still depend on the current client and game version.
What is the best control layout?
The best layout keeps the prompt visible, separates frequent actions, and stops movement cleanly. Device size and hand position make one universal layout impossible.
Why does my character move during Don’t Move?
Check held touch input, duplicate keys, stick drift, and whether a movement key released. Test outside the active command before blaming the rule.
What should I read next?
Use the Beginner Guide to apply the layout, Obby for jump control, and How to Win for clean late-round inputs.
Source checked
- Official Roblox experience — current Settings path and rebind/rebuild statement, checked October 7, 2026.