I teach Godot by making you build, not watch.
Coding Quests is a Godot 4 learning platform built around one idea: you actually learn game development by finishing real systems, not by collecting half-watched tutorials. Every course is a quest. You write real GDScript, beat encounters, and walk away with a working system you understand well enough to reuse in your own game.
Why I built this
Most people who set out to learn Godot get stuck in tutorial hell. You follow along, the project works on screen, and then you open a blank scene of your own and realize none of it stuck. The problem isn't effort. It's that watching someone else type is not the same skill as building something yourself.
So I flipped it. Instead of long videos you passively watch, each Coding Quests lesson drops you into the editor with a real problem to solve. You write the code. The encounter checks it. When it clicks, you move on. By the end of a quest you haven't watched an inventory system get built, you've built one.
“I wasted years in tutorial hell, following along then freezing on a blank scene. So I built the guide I wish I'd had: write real GDScript, get it checked, and walk away with a whole game you actually understand.”
Omar · Creator of Coding Quests
How the quests work
- Build complete systems. Each quest ships a real, finished feature for Godot 4.x, the same way you'd build it in a production project.
- Learn the why, not just the steps. I focus on the patterns (state machines, Resources, components) so the knowledge transfers to your own game.
- Start free. Several full quests are free with no card required. A membership unlocks the rest of the library.
What you'll build
Drag-and-drop items, stacking, and grid UI built on Resources.
An 8-direction CharacterBody2D controller with a follow camera.
Combat-aware 3D enemies that chase, circle, attack, and react.
Weighty third-person movement, dodge rolls, and lock-on strafing.
File I/O, JSON serialization, save slots, and versioning.
Component-based stats, modifiers, XP curves, and level-ups.
See the full catalogue on the quests page or read free tutorials on the blog.
How the lessons are made
Every quest is built from a real Godot 4.7 project that runs. The project is written first, then the lessons are cut from it. So the code you are taught is the code that shipped, not a snippet written to look good on a page.
AI-assisted tools are used in parts of the CodingQuests content workflow. Omar is responsible for what is published, and reported issues are reviewed and corrected.
Alongside that, some checks run automatically on every build, because a machine is better at them than a person reading 313 lessons. Every graded exercise has a reference solution that has to execute and produce the expected output. Other checks look for quiz answers that do not line up, code checks that would pass on broken code, and lessons that ask you to write something they never showed you.
That last check exists because it was a real problem. A review in August 2026 found lessons that described a result without ever showing the code behind it. Most of them were polish steps at the end of a lesson. Those were rewritten, and the build now fails if a new lesson does the same thing.
If a step still expects something you were never taught, that is a defect and we want to know. Use Report an issue inside any lesson. It sends the quest, the lesson and the exact step along with your note, so nobody has to guess which part broke.
Get in touch
Ready to actually build something?
Pick a free quest and write your first real Godot system today. No card needed.
Browse the quests