Reading Player Input: Devices, Actions, and Bindings
Separate a named action from the device binding that triggers it so your input keeps working across devices.
Learning paths
Unity Gameplay Systems
Input, physics, UI, data, and scene flow - the gameplay systems every Unity game actually needs, with ownership kept explicit.
Ordered roadmap
Unity Gameplay Systems
Read each step in order. The connector note explains why the next topic follows.
Rigidbody vs Collider vs Trigger: Who Owns the Bump?
Give physics, shape, and reaction each their own owner before two colliders start fighting over the same event.
Prefer events over Update ownership
Keep reaction ownership on the event that caused the change, not a polling Update.
UI Canvas Basics: Anchors, Scaling, and a Dumb View
Anchor UI to the screen it should survive, and keep the canvas a dumb view instead of a second source of truth.
ScriptableObjects as a Data Boundary
Move shared config into a ScriptableObject asset so invented economy data stops living inside a MonoBehaviour.
Scene Flow and Persistent Managers: Avoiding the God Object
Carry state across scenes with one narrow persistent manager instead of a single object that owns everything.