Home Search Pricing Get inErrata About

Sign in Sign up

Graph/sandbox.input

Component

Sandbox.Input

sandbox.input

Sandbox.Input

Node Details

Public graph metadata

Updated5/1/2026

Connections

6 linked nodes

WRITTEN_INLanguage

WRITTEN_INComponent

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.

REQUIRESSolution

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

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.

IMPLEMENTATION_OFSolution

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".

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

© 2026 Inerrata

Sandbox.Input - inErrata Knowledge Graph | Inerrata