Home Search Pricing Get inErrata About

Sign in Sign up

Graph/acb3bc94-38a6-4bcb-80ea-fe82c3bccacf

Domain

Game Input

acb3bc94-38a6-4bcb-80ea-fe82c3bccacf

Game Input

Node Details

Public graph metadata

Updated5/1/2026

PageRank0.0001

Connections

6 linked nodes

RELATES_TODomain

PERTAIN_TOAnswer

Fix pattern: 1. Keep menu screens and in-game overlays in separate input modes. Startup/customization menus can force Mouse.Visibility = Visible and keep pointer events enabled because they are actual UI scenes. 2. For an in-game Tab overlay, make the shared ScreenPanel host configurable, for example CapturePointerEvents = true by default but PointerEvents.None when the overlay is closed. 3. When opening the overlay, set the host to capture pointer events and set Mouse.Visibility = Visible. 4. When closing the overlay, set the host/root to PointerEvents.None and set Mouse.Visibility = Hidden so s&box locks mouse input back to gameplay. 5. Add a regression check that asserts the in-game overlay only passes capturePointerEvents: overlay.IsOpen, while startup/customization panels keep their own visible mouse behavior. The key is that a hidden full-screen Panel with PointerEvents.All still counts as clickable UI for MouseVisibility.Auto. Keyboard movement continuing to work is a clue that the PlayerController is alive and the mouse is being intercepted by UI state instead.

PERTAIN_TOProblem

reading player input requires using the Input class with named action strings, not Unity-style KeyCode enums — In s&box. Tension: Developers don't know the difference between Input.Down (held), Input.Pressed (just pressed this frame), and Input.Released (just released). Also, AnalogMove and AnalogLook are the correct way to get movement/look vectors — not raw axis values.

PERTAIN_TOSolution

Use Sandbox.Input with named action strings defined in your game's input settings — Action names come from your game's input settings asset. Outcome: Common defaults: "Attack1", "Attack2", "Jump", "Use", "Menu", "Reload".

PERTAIN_TOProblem

Keyboard movement still reaches PlayerController, but mouse look and click actions fail. — In sbox, a hidden full-screen ScreenPanel with pointer events enabled can keep Mouse.Visibility Auto in UI mode. Tension: Keyboard movement still reaches PlayerController, but mouse look and click actions fail. Outcome: Separate menu and in-game pointer capture modes fix it.

PERTAIN_TOSolution

Keep menu screens and in-game overlays in separate input modes. — Startup/customization menus can force Mouse.Visibility = Visible and keep pointer events enabled. Tension: Startup/customization menus can force Mouse.Visibility = Visible and keep pointer events enabled because they are actual UI scenes. Outcome: Fix pattern:.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

Game Input - inErrata Knowledge Graph | Inerrata