I opened Unity for the first time…and immediately got overwhelmed by tabs everywhere. But after writing my first small script, things finally started connecting.
This post is part of my daily learning journey in game development.
I’m sharing what I learn each day — the basics, the confusion, and the real progress — from the perspective of a beginner.
On Day 98 of my game development journey, I explored the Unity Editor and basic C# scripting workflow.
What I Used to Think
I thought Unity would work like a simple drag-and-drop tool.
But after opening the editor, I saw:
- Scene
- Game
- Hierarchy
- Inspector
- Project
Everything looked confusing at first.
What I Realized
Each Unity tab has a specific role.
Scene
Used to build and edit the level.
Game
Shows the final camera output.
Hierarchy
Stores all objects inside the scene.
Inspector
Displays properties of the selected object.
Project
Contains assets, scripts, and project files.
Then I connected Visual Studio Code and created my first C# script.
After declaring a simple variable, I finally understood how scripting connects with Unity objects.
Why This Matters
Unity combines:
- Visual editing
- Programming
The editor handles the scene visually, while C# scripts define behavior.
That’s why Unity uses an external code editor like VS Code.
Example:
public int speed = 5;
Public variables appear in the Inspector, allowing values to be changed without editing code.
What Finally Clicked
Hierarchy = objects
Inspector = properties
Scripts = behavior
Unity’s editor and code work together as one system.
Practical Fix
- Open Unity Hub and create a project
- Install Visual Studio Code
- Set VS Code as the external editor in Unity Preferences
- Create a C# script
- Attach the script to a GameObject
- Declare simple variables to test behavior
One Lesson for Beginners
- Don’t try to learn every tab at once
- Inspector changes based on the selected object
- Public variables appear in the Inspector
- Save scripts before returning to Unity
- Use the Console tab to debug errors
Common Beginner Mistake
Thinking Unity scripting works separately from the editor.
In reality:
- The editor handles visuals
- Scripts control logic
- Both are deeply connected
Why This Matters in Real Projects
Understanding the editor layout is the foundation of learning any engine.
Unity’s workflow is designed around:
- Fast iteration
- Visual editing
- Modular scripting
Learning simple concepts like variables early helps build confidence before moving into larger gameplay systems.
At first, Unity looked complicated.
But once the relationship between the editor and code became clear, the workflow finally started making sense.
Slow progress — but I’m building a strong foundation.
If you’re also learning game development, what was the first thing that confused you when you started?
See you in the next post 🎮🚀
Top comments (0)