When I started with Unity, my scripts worked…  
but I didn’t really understand **when** they were running or **why** things behaved strangely.

Once I understood the **GameObject lifecycle**, everything became clearer 👇

**Awake()**  
Runs first, once, when the object is loaded.  
Used to set up references and internal data — even if the object is disabled.

**OnEnable()**  
Runs every time the object becomes active.  
Great for event subscriptions and reset logic.

**Start()**  
Runs once, just before the first frame.  
Perfect when you need other objects to already exist.

**Update()**  
Runs every frame.  
Used for input, movement, and real-time gameplay logic.  
Keep it light for performance.

**FixedUpdate()**  
Runs at a fixed time step.  
This is where physics logic belongs.

**LateUpdate()**  
Runs after Update.  
Often used for camera logic and final adjustments.

**OnDisable()**  
Runs when the object is disabled.  
Clean up here: unsubscribe from events.

**OnDestroy()**  
Runs right before the object is destroyed.  
Final cleanup and resource release.

💡 **Takeaway**  
Unity scripting isn’t just about *what* your code does, it’s about *when* it runs.  
Understanding the lifecycle made my code more predictable and easier to debug.

If you’re learning Unity, this is a game changer.

\#Unity #GameDev #LearningUnity #IndieDev #CSharp #GameDevelopment

Understanding the Unity GameObject Lifecycle (Beginner-friendly)