Core Systems for Unitys
Unity core systems are the built-in physics and movement features that make objects behave in a game world. Rigidbody components apply forces and gravity, Colliders detect contact, and the Input System reads player controls. Scripts combine these to move characters, handle collisions and trigger events.
Stage: Unity Essentials · Part of the Unity roadmap · Last reviewed 19 November 2026
What to learn in Core Systems
- Add a Rigidbody and Collider so an object falls, collides and reacts to forces
- Move a character with the Input System and a speed value scaled by Time.deltaTime
- Detect overlaps with trigger colliders and handle them in OnTriggerEnter
- Choose between transform movement, Rigidbody velocity and CharacterController for a given case
- Use physics layers and raycasts to filter what objects interact
Core Systems interview questions
Why should physics code go in FixedUpdate and not Update?
FixedUpdate runs at a fixed time step that the physics engine uses, so forces and velocity changes behave consistently regardless of frame rate. Update runs once per rendered frame and varies. Read input in Update, then apply the resulting forces in FixedUpdate.
What is the difference between a collider and a trigger?
A normal collider blocks other colliders and produces collision callbacks such as OnCollisionEnter. A collider marked Is Trigger does not block movement; objects pass through and OnTriggerEnter fires instead. Triggers suit pickups, zones and detection areas.
Where Core Systems fits in the Unity roadmap
Core Systems belongs to the Unity Essentials stage (beginner level), which takes about 33 hours. Start here.
Other units in this stage
Back to the full Unity roadmap