Here is the full four-week plan. No experience needed — not a single line of code ever written, not one tutorial watched. If you can open a browser, you can start today.
Three honest expectations
Four weeks is not enough time to build the game you are imagining. It is exactly enough time to finish a small one — and finishing is the skill nobody teaches.
- You will not build Skyrim.You will build one small, complete, playable game. One finished project teaches more than ten ambitious abandoned ones, and it is the only kind anyone can actually play.
- You will get stuck. Repeatedly.Getting unstuck is the real skill being trained. Reading an error message calmly instead of panicking is most of what separates a beginner from an intermediate.
- Age is not the obstacle. Inconsistency is.Three sessions of 45 minutes beat one heroic Saturday. People start this at 60 and ship. People start at 22 and quit in week two. The variable is the calendar, not the birth year.
Choosing your tool
| Tool | Best if you | Cost | Code | Verdict |
|---|---|---|---|---|
| Scratch | Have never programmed anything | Free | Blocks | Optional warm-up |
| GDevelop | Want games without writing code | Free | Visual events | Good alternative |
| Godot 4 | Want a real engine | Free, open source | GDScript | This plan |
| Unity / Unreal | Aiming at industry work | Free tier | C# / C++ | Later, not now |
If you have never written a single line of code anywhere, spend two evenings in Scratch first. It is not beneath you. It removes a month of confusion because it teaches you what a loop and a variable actually feel like before you have to type them.
Setup: 45 minutes, once
- Download Godot 4 from godotengine.org. No account, no installer, no payment. It is a single file you run.
- Open it, create a new project and choose the 2D renderer. Do not change any other setting.
- Bookmark the official “Your first 2D game” tutorial. It is free, and it is the spine of this plan.
- If you have never written code anywhere: spend two evenings on Scratch first. It is not beneath you and it removes a month of confusion.
The editor, and a thing that moves
Get comfortable inside the editor and put something on screen that responds to you.
What you’ll learn
- Nodes and scenes — and why everything is one
- The scene tree
- Sprite2D and the inspector
- Attaching your first script
- _process(delta) and frame time
- Reading keyboard input
The three sessions
- 01Tour the editor. Make a 2D scene, add a Sprite2D, press play.45 min
- 02Attach a script. Move the sprite with code alone, no keyboard input yet.60 min
- 03Read the arrow keys. Move the sprite, and keep it inside the window.60 min
A character you can drive around a window with the arrow keys.
Rules, collisions and a score
Turn a moving sprite into something that can be won and lost.
What you’ll learn
- Area2D and collision shapes
- Signals — and why they beat checking every frame
- Variables and game state
- Timers
- Instancing a scene at runtime
- Groups
The three sessions
- 01Add collision shapes. Connect your first signal and print something.60 min
- 02Spawn objects on a timer, at random positions.60 min
- 03Add a score variable and a game-over state that stops play.60 min
A real game loop: start, play, lose, restart.
Make it feel good
The distance between a tech demo and a game is feedback.
What you’ll learn
- AnimatedSprite2D and sprite sheets
- AudioStreamPlayer and free sound effects
- Tweens for movement that has weight
- CanvasLayer and UI that stays put
- GPUParticles2D
- Screen shake
The three sessions
- 01Animate the player. Add two sound effects from Kenney.nl or jsfxr.60 min
- 02Build a HUD: a score label and a message label that survive scene changes.60 min
- 03Add juice: a tween on pickup, a particle burst, a small screen shake.60 min
A game that reacts to the player instead of just obeying them.
Ship it
Put it in front of another human being. This is the week that actually counts.
What you’ll learn
- A main menu as its own scene
- Switching scenes and restarting cleanly
- Export templates
- The HTML5 export and what breaks in it
- Publishing on itch.io
- Writing a two-line game description
The three sessions
- 01Build a main menu and a working restart flow.60 min
- 02Export to HTML5. Fix what breaks. Something always breaks.60 min
- 03Publish on itch.io and send the link to exactly one person.45 min
A public URL of a game you made, that a stranger can play in a browser right now.
Where this goes next
Stay in Godot. Learn GDScript properly, then try 3D. Rebuild the same small game, better. Each rebuild is faster than the last.
Learn the crafts around the code: pixel art in Aseprite or Krita (both free), sound in jsfxr, music in LMMS.
Enter a game jam. Ludum Dare, GMTK Jam, or any itch.io jam. A weekend deadline teaches more than a month alone.
Free resources worth your time
- Godot official docs — the “Your first 2D game” tutorial, start to finish. Free, no account.
- Learn GDScript From Zero — a free interactive app by GDQuest, no browser tab juggling required.
- Kenney.nl — thousands of free game assets, no attribution required. The best gift to any beginner.
- jsfxr — retro sound effects generated in the browser in seconds. No account, free download.
- OpenGameArt — free art and music under permissive licences.
- itch.io — where you publish, and where you play what other beginners made. More instructive than any course.
Ship log — what you actually finished
Print this page or copy the table somewhere. Write down what you actually finished each week, not what you planned to finish. The gap between those two things is the most useful data you will collect.
| Week | What I actually finished | Date |
|---|---|---|
| 01 | ||
| 02 | ||
| 03 | ||
| 04 |
Frequently asked questions
Why Godot and not Unity or Unreal?
Unity and Unreal are industry-standard tools, but they are also significantly more complex to set up and learn. Godot 4 is free, open source, and installs as a single file with no account required. The concepts you learn in Godot transfer directly to Unity if you ever need it — the reverse is much harder.
Do I need to know math?
Not for this plan. You will use addition, subtraction and the concept of a random number. The geometry of 2D games becomes relevant later, when you choose to go deeper. It is not a prerequisite.
How is this different from watching YouTube tutorials?
Watching is not practising. A tutorial teaches you how someone else solved a specific problem. This plan gives you a structure for solving your own problems, in order, with a finished game at the end of each week instead of a half-finished copy of someone else’s project.
What if I fall behind?
Restart the week, not the whole plan. If week two takes three weeks, that’s fine — the goal is the deliverable at the end, not the calendar. The only real failure mode is stopping entirely.
Can I do this on a Mac?
Yes. Godot 4 runs on Windows, macOS and Linux. The HTML5 export works the same on all three. A Mac made in the last six years will handle it without any issue.
What does “shipping on itch.io” mean exactly?
You create a free account on itch.io, upload the HTML5 export Godot generates, and get a public URL. Anyone in the world can open it in a browser and play your game immediately, at no cost to you or them.
Is game development a viable career?
The games industry is large and does employ a wide range of roles — programmers, artists, designers, audio engineers, producers. It is also competitive. This plan is not a career path; it is a skill foundation and a way to find out whether you genuinely enjoy the craft before investing more time in it.
What if I built a kids’ game instead?
The skills are identical. If someone in your household is learning to make games with Scratch and you want to build alongside them at a higher level, this plan pairs well with our free 4-week kids’ plan.
The requirement was never talent, and it was never youth. It was finishing one small thing, and then starting the next one.