Place the Keycaps Q and Ctrl Controls
A focused desktop reference for Q to throw, Ctrl to unlock the mouse, selection confirmation, pile management, and device-specific control checks.
First-party keyboard controls
The official Place the Keycaps listing states Q to throw and Ctrl to unlock the mouse. These are the two desktop bindings that can be published as first-party facts. The listing also labels the experience beta, so the live on-screen prompt should win if a later update changes a binding.
| Key | Published action | Practical check |
|---|---|---|
| Q | Throw | Face a clear staging zone and test with one known duplicate or selected cap |
| Ctrl | Unlock mouse | Confirm the cursor can reach interface controls, then return to play |
| Movement/input | Follow Roblox and live prompts | Do not copy a mobile touch icon into the desktop key list |
Create a safe Q-throw zone
Throwing is useful only when it reduces pile confusion. Choose one edge away from the keyboard board and make it the temporary Q zone. Never throw toward filled slots, the main unsorted pile or another player's active cluster. Read the key legend first; an uncertain modifier belongs in an inspection zone, not a discard zone.
After every few throws, rotate the camera and confirm the zone still contains only deliberately moved caps. If a needed cap was thrown, retrieve it before adding more. The goal is a smaller search surface, not a second uncontrolled pile.
Use Ctrl without losing the selected object
Unlock the mouse when an interface element needs a cursor, then verify the selected cap and held state before continuing. Avoid pressing several controls during a lag spike. If focus does not return, step away from the pile, use Ctrl once, and check whether the cursor or camera state changes.
The timestamped mobile recording at 05:00 shows why device context matters: touch movement, jump and the held-cap tray are visible instead of desktop Q and Ctrl prompts. It corroborates the selection-and-tray workflow, not the keyboard binding itself.
Diagnose a control problem
Record device, input method, server time, selected cap, visible prompt and result. Test one action in an open area. If Q does nothing, verify chat or another text field is not focused and that a cap is actually selected. If Ctrl does not unlock the cursor, check the current Roblox input mode and live settings.
Do not install a macro or unsupported tool to automate throwing. A clean bug report with device and prompt details is more useful during beta, and it avoids turning a control problem into an account or fair-play problem.