CONTROL WITH INTENT
Use controls to make experiments easier to read
Pause and Step are not only convenience buttons. They help you see whether a material fell because of gravity, changed because of heat or reacted after another element touched it. That makes a recipe easier to troubleshoot and a screenshot easier to reproduce.
Filtering is equally important when a palette grows large. Search a short material name, select it, clear the filter when you are done, and save before you begin a more destructive test. These small habits reduce the amount of random trial and error in an open-ended sandbox.
Because the interface can change, this page uses plain-language actions instead of pretending that one shortcut list will remain correct forever. Check the current UI whenever a key or modifier seems different.
The most useful Sandboxels controls are the ones that help you observe a cause and an effect. Pause before placing a precise layer, step forward when you want to see the next movement, and reset when a test has too many variables. These actions turn a busy simulation into a sequence you can inspect instead of a result you have to guess about.
Mouse input is usually best for drawing a line, spreading a small pile or selecting a target area. Touch input may use larger buttons, a different palette position or gestures that are not available on a desktop. If the same action feels unavailable on a phone, look for a collapsed toolbar or the current mobile help before assuming the feature was removed.
Keyboard shortcuts are helpful when they are visible and stable, but they should never be the only way to learn the interface. Use the current help panel for modifiers such as Shift, especially after an update. The companion controls table gives you a memory aid; it cannot override the behavior of the build you opened.
A good control routine also protects your work. Save a world before testing a large reaction, keep a clean copy before enabling a mod and capture a screenshot when a layout or result is difficult to describe. If a control appears to do nothing, confirm that the simulation is not paused, that the correct tool is selected and that the pointer is inside the play area.
Use this Sandboxels controls reference together with the task guides. The Filter guide focuses on narrowing a palette, the recipe guides focus on placing inputs and the experiment on this site demonstrates Pause, Step, Reset and Screenshot. Linking an action to a real task is faster than memorizing a list without knowing when the shortcut helps.
When a control is difficult to find, check the order of the interface before checking the key. Some builds place the palette, toolbar and simulation buttons in different areas, especially on narrow screens. Expand the relevant drawer, confirm the current selected tool and then try the action again. This simple sequence avoids confusing a hidden control with a disabled one.
The Sandboxels controls table is also useful for communication. A note such as “pause, step twice, then screenshot” gives another player a repeatable observation sequence. A vague note such as “try the shortcut” does not. When you write a guide or report a bug, name the input, the action and the expected visible change so the context survives across devices.
If a key works in one browser but not another, compare focus and browser shortcuts before blaming the simulation. A text field, browser tab or accessibility setting may be receiving the input. Click the play area, close an open search field and check the current help panel. The companion Sandboxels controls reference can guide the action, but the active browser still determines which input reaches the simulation.
Keep the controls you use most visible in your own notes: select, place, pause, step, reset, save and screenshot. A short personal list is often more reliable than a long list of rarely used modifiers, especially when the interface changes.
