Why there is no fake key list here
The official public description does not list a complete control map. Publishing guessed keys would create unreliable help.
How to document a control
Record the exact prompt, device type, action and version context. If the game does not expose a prompt, mark the control as awaiting verification instead of filling the gap with a familiar Roblox shortcut.
Best current method
Use the live Roblox control prompts and any in-game hints. This page will be expanded when controls can be verified against the current experience version. Until then, a missing prompt should be recorded as an evidence gap rather than filled with a guessed shortcut.
Control verification
A reliable control entry needs the exact action, prompt wording, device, and version context. This keeps desktop, mobile, and future interface changes separate and prevents a personal keybind from becoming a universal claim.
What this page can document
The controls reference can safely record an input only when the current experience exposes a clear prompt or the action can be verified for a named device context. A useful entry identifies the action, exact displayed instruction, platform, and observation date. It should not fill a missing mapping with a familiar Roblox key or gesture. No complete exact keybind list is confirmed in the existing public information. The page therefore explains how to read and verify controls while leaving undocumented shortcuts awaiting verification.
Device and version context
A control observed on PC should not automatically be assigned to mobile, and a mobile prompt should not be translated into a keyboard shortcut. Interface layout, available prompts, and input behavior may differ by device or change during Data Testing. Record each observation within its own platform and current-version context. When a prompt changes or disappears, preserve the older note as historical and verify the current behavior again. Do not assume that a personal remapping, platform default, or community instruction is universal.
When a control is unknown
If the interface does not show a reliable prompt, mark the action unverified or awaiting verification. Use the visible in-game hints and normal platform interface to inspect the current session, but avoid repeated guessing that could turn an unsupported shortcut into published guidance. Missing control data is preferable to a confident but incorrect mapping. Describe the action you are trying to perform and keep it separate from the assumed input. This makes a later verified observation easier to add without rewriting an invented control scheme.