Chapter 3 Further Reading

Godot Documentation and References

Godot Engine Official Documentation (docs.godotengine.org)
The primary reference for everything Godot. The "Getting Started" section walks through project setup, the scene system, and GDScript fundamentals. The "GDScript Reference" is where you'll go when you need to look up syntax, built-in functions, or class methods. The documentation is comprehensive, well-organized, and searchable --- use it before searching forums. Press F1 inside the Godot editor to search the built-in docs directly.

GDScript Reference (docs.godotengine.org/en/stable/tutorials/scripting/gdscript/)
The dedicated GDScript language reference covers variables, functions, control flow, signals, classes, type hints, annotations (@export, @onready, @tool), and patterns specific to GDScript. Bookmark this page. You'll return to it constantly for the first several weeks.

Godot Recipes (kidscancode.org/godot_recipes/)
KidsCanCode maintains a collection of practical Godot tutorials organized by topic: 2D movement, physics, UI, tilemaps, audio, shaders, and more. Each recipe is a self-contained tutorial solving a specific problem. When you need to implement something and the official docs feel too abstract, check here for worked examples.

Prototyping and Design Process

Stone Librande, "One-Page Designs" (GDC 2010)
A GDC talk by the creative director of SimCity (2013) and Diablo III arguing that every game's design should fit on a single page. Librande demonstrates how one-page visual design documents communicate game concepts more effectively than 100-page text documents. This talk directly inspired the one-page concept document format used in this chapter. Available on the GDC Vault.

Jesse Schell, The Art of Game Design: A Book of Lenses (3rd edition, 2019)
Chapter 7 ("The Game Begins with an Idea") and Chapter 8 ("The Game Improves Through Iteration") are particularly relevant to this chapter's discussion of prototyping and design documentation. Schell's "Lens of the Prototype" asks: "What is the cheapest, fastest way to test whether this design works?" --- a question this chapter answers with paper prototypes and PICO-8-scale proofs of concept.

Jeremy Gibson Bond, Introduction to Game Design, Prototyping, and Development (3rd edition, 2021)
A practical textbook that bridges design and programming, with extensive coverage of Unity and C#. The prototyping chapters (Part II) cover paper prototyping, digital prototyping, and the transition between them in more detail than any other textbook. Useful as a complement to this book, especially if you want to see the same principles applied in a different engine.

Constraint-Driven Design

Lexaloffle PICO-8 Website (lexaloffle.com/pico-8.php)
The official PICO-8 site includes the game browser (thousands of free, playable games), documentation, and community forums. Explore the game browser sorted by "Featured" to see what master-level design looks like within extreme constraints. The PICO-8 Celeste prototype is playable directly in the browser.

Adam LeDoux, Bitsy Game Maker (bitsy.org)
Bitsy is free and runs entirely in the browser. You can build and publish a complete game in under an hour. Even if you never use Bitsy for a "real" project, building one game in it will teach you more about spatial storytelling and constraint-driven design than a week of reading.

"Celeste Classic" Source Code (github.com/ExOK/Celeste2pico8)
The PICO-8 source code for the original Celeste prototype is publicly available. Reading it is an education in constrained programming --- how to implement responsive platformer physics, state management, and level design in under 8,192 tokens. Compare the prototype code to the concepts in this chapter's GDScript examples to see how the same design principles manifest in different tools.

Tools and Workflows

Scott Hanselman, "Git Branching and Merging for the Real World" (various presentations)
If version control is new to you, start with a tutorial on Git fundamentals rather than trying to learn it from documentation. Hanselman's presentations are accessible and practical. For game-specific Git workflows, search for "Git for game developers" --- there are several community guides addressing the specific challenges of versioning game assets (large files, binary formats).

draw.io (app.diagrams.net)
A free, browser-based diagramming tool ideal for the flowcharts and menu flow diagrams discussed in this chapter. No account required. Supports export to PNG, SVG, and PDF. The simplest tool that does everything you need for design documentation diagrams.

Games to Play

Celeste (2018, Maddy Thorson / Extremely OK Games)
Play the full version after playing the PICO-8 prototype (free on Lexaloffle's site). Notice how the core mechanic --- movement, jump, dash --- survived the transition from 128 x 128 pixels to full resolution essentially unchanged. This is proof that prototyping works: the core was validated in four days and carried a 7-10 hour masterpiece.

Hollow Knight (2017, Team Cherry)
A Metroidvania made by three people that competes with games made by teams of hundreds. Pay attention to the combat feel (the weight of the nail swing, the impact feedback), the environmental design (how each area establishes mood through visuals and music), and the scope discipline (every room earns its place). A case study in what's possible when a small team with a clear vision uses tools effectively.

Brotato (2023, Blobfish)
A roguelike auto-shooter made in Godot by a solo developer. Play it to see what the engine you're learning is capable of in the hands of one skilled person. Notice the simplicity of the core loop (survive waves, collect items, upgrade) and how that simplicity produces emergent complexity through item interactions.