Scènes comme composants, signaux plutôt que scrutation, GDScript typé.
Constitution — Godot game
Version 1.0.0 · Ratified 2026-11-10
These principles hold for every spec, plan and task of the game. A spec may add rules; it never weakens these.
-
Scenes as components. Each reusable piece (a hitbox, a health bar, a pickup) is its own scene with one root script and is instanced where needed. A scene works when run alone with F6, without its parent.
-
Signals over polling. Children report changes by emitting signals; parents call down and listen up. A script that checks another node's state every frame in
_processinstead of connecting to a signal fails the review. -
Typed GDScript. Every variable, parameter and return value has a static type, and the project sets untyped declarations to report errors. The game runs with no type warnings in the debugger.
-
No fragile node paths. Nodes a script needs are reached with
@exportreferences or%UniqueName, never with longget_node("../../..")paths that break when the tree changes. -
Data in Resources. Item stats, enemy definitions and level settings are custom
Resourcefiles edited in the inspector. Code reads them; it does not hold them as constants. -
Autoloads are few. Only truly global services (save, audio, scene changes) are autoloads, and each one is listed in the plan. Game state is not reached through an autoload when it can be passed in.
-
Tested and exported in CI. Gameplay rules have GUT or gdUnit4 tests that run headless, and CI exports every target platform with the pinned Godot version on each merge. A failed test or export blocks the merge.