Game Development with Godot 4: A First Course

Preface

From your first node to a finished point-and-click adventure with Popochiu

y2kmallrat · First edition, October 2026

Written for Godot 4.7 (stable) and Popochiu 2.2.1.

An unofficial guide. This book is an independent educational work. It is not produced, endorsed, or sponsored by the Godot Foundation, by Carenalga, or by the Popochiu project or Godot Engine contributors. All text in it was written for this book.

Godot Engine is Copyright (c) 2014-present Godot Engine contributors and Copyright (c) 2007-2014 Juan Linietsky and Ariel Manzur, released under the MIT License. Popochiu is a free, open-source Godot plugin by Carenalga and contributors, released under the MIT License. Thank you to both communities.

"Godot" and the Godot logo are trademarks of the Godot Foundation. The book uses the names only to refer to the software.

Copyright © 2026 y2kmallrat. The text, diagrams, screenshots and cover art of this book are licensed under the Creative Commons Attribution-NonCommercial 4.0 International license (CC BY-NC 4.0, https://creativecommons.org/licenses/by-nc/4.0/). You may share and adapt them with credit to the author, but not for commercial use. The example code is released under the MIT License.

Preface

This book teaches you to make games with Godot, a free and open-source game engine. It assumes you have never opened Godot before. It does assume you have met the basic ideas of programming, such as variables, loops and functions, in a language like Java, C or Python. If you have not, Chapters 3 and 4 move slowly enough to follow, but expect to reread them.

The book has two aims. The first is to give you a real foundation in Godot: the editor, the scene system, the GDScript language, 2D graphics, physics, interfaces, animation, sound, saving data and shipping a finished program. These skills transfer to any kind of 2D game. The second aim is to apply that foundation to one genre, the point-and-click adventure, using a Godot plugin called Popochiu. By the last chapter you will have built Weird Hotel, a small, strange adventure game with two rooms, an inventory, item puzzles, a talking frog, a mini-game, a boss fight, death and respawn, save files and a Windows build.

Like a school textbook, this book covers more than the final project strictly needs. Part II teaches physics bodies, tilemaps and menus even though an adventure game uses little of them. You will need them for your second game, and Popochiu makes much more sense once you know what it is built on.

How this book is organized

How each chapter works

Every chapter follows the same pattern, so you always know where you are:

1. Learning objectives: what you will be able to do by the end.
2. Key terms: the new words, defined up front.
3. Numbered sections: the lesson itself, with worked examples and short Try it activities.
4. Lab: a longer hands-on project with numbered steps and an expected result.
5. Chapter summary: the main ideas in a few bullets.
6. Review questions: check your understanding. Answers are in Appendix D.
7. Exercises: graded Practice (easy), Apply (medium) and Challenge (hard).
8. Common mistakes: symptom, cause and fix for the errors beginners hit most.
9. Further reading: official documentation pages to go deeper.

Callout boxes appear throughout:

Note: extra detail worth knowing.

Warning: something that can lose work or cause confusing bugs.

Why it works: the reasoning behind a technique.

Try it: a small activity to do right now.

How to study with this book

• Type the code; don't paste it. Typing forces you to read every line, and the typos you make teach you to read error messages.
• Run often. Every lab step leaves the project in a working state. Run the game after each step, not only at the end.
• Make it work with boxes first. Use plain shapes and placeholder text. Gameplay is the point; art comes last.
• Commit after every working step. Chapter 11 teaches git. From Part III on, every lab ends with a commit.
• Do the review questions before checking Appendix D. Getting one wrong and then understanding why is worth more than reading the answer.
• When stuck, ask for an explanation, not a fix. Appendix F shows how to use an AI assistant as a tutor rather than a ghostwriter.

About versions

Godot and Popochiu both change over time. This book was written against Godot 4.7 and Popochiu 2.2.1, the stable pairing as of October 2026. Popochiu only supports specific Godot versions, so Chapter 13 shows you how to check the version table before installing. If a menu name or button label on your screen differs slightly from the book, the idea is almost always the same. Where the book could not confirm a detail for your exact version, it says so and tells you where to check.

A suggested 15-week schedule

For a one-semester course, or for self-study at about 4-6 hours a week:

Prefer to read offline? PDF (16 MB)