PIT OF GOBLIN: How to Cast Magic on Controller When UI Says Q
Direct answer · November 10, 2026 original-source and version check
A developer replied to a controller player that the keyboard Q prompt could be a display error. On controller, clicking the right analog stick is the intended magic button according to that reply.
Jump straight to the steps ↓THE TASK
How to Cast Magic on Controller When UI Says Q
- 01
Make sure you have an ability or spell equipped before assuming controller input has failed.
- 02
Press the right stick inward rather than moving it to a direction; the developer identifies the stick click as the action.
- 03
If the ability still does not activate, note whether you are using an Xbox, PlayStation or third-party controller and whether the same binding appears in the current settings menu.
IMPORTANT LIMITS
What if your result is different?
The confirmed workaround is a developer response to one prompt-label mismatch; it does not fix every unrelated controller issue.
EVIDENCE
Sources for How to Cast Magic on Controller When UI Says Q
- Original player question and replies: How to Cast Magic on Controller When UI Says Q
- PIT OF GOBLIN on Steam
Evidence and version: November 10, 2026 original-source and version check
Controller prompt mismatch: Q is not the Xbox magic action
A developer explicitly replied that a displayed keyboard Q prompt can be a UI display bug for controller players: clicking the right analog stick is the intended magic input, including when the on-screen label is wrong. The original questioner specifically used an Xbox controller; do not silently generalize the same label or mapping to every console and input profile.
Check: confirm that your device is being recognized as a controller, then press the right stick inward at the moment the magic action is available. Success: the character initiates the magic action; merely seeing the Q label unchanged is not a failed control if the action works. If pressing the stick does nothing, record controller model, connected input mode and current build rather than treating the developer’s display-bug explanation as a guaranteed fix for broken binding detection.