Implement Godot GDScript Production Patterns

Provides production patterns for building games in Godot 4.x with GDScript, covering core architecture (Nodes, Scenes, Resources, Signals, Groups) and seven concrete implementation patterns: a signal-driven state machine (a StateMachine autoload paired with a State base class and per-state scripts like PlayerIdle), autoload singletons for global game state (a GameManager tracking score, pause, and game-over plus a decoupled EventBus for player, enemy, item, and level signals), resource-based data objects (WeaponData and CharacterStats as Resource subclasses so combat stats live separately from game logic), object pooling for frequently spawned entities (an ObjectPool that grows on demand and recycles instances such as PooledBullet), a component system built from Area2D-based HealthComponent, HitboxComponent, and HurtboxComponent nodes for decoupled combat, async scene management (a SceneManager that loads scenes on a background thread with progress signals and transition effects), and an encrypted save system (a SaveManager using FileAccess.open_encrypted_with_pass alongside a Saveable component that collects and restores per-node position and custom data). Each pattern ships as runnable GDScript with class_name declarations, typed exports, and explicit signal definitions, plus a set of performance tips (caching node references, avoiding per-frame allocations, static typing, disabling processing when off-screen) and best-practice do's and don'ts.

Use it when building a game with Godot 4, implementing gameplay systems in GDScript, designing scene architecture, managing game state across scenes, or optimizing GDScript performance. Skip it for anything outside Godot or GDScript game development, or when the task calls for a different engine or domain entirely.

Input is a described game system or performance question; output is one or more of the seven GDScript patterns above, delivered as copy-ready code (state machine, singleton, resource, pool, component, scene manager, or save system) plus the performance tips and best-practice guidance that go with it. The skill also documents the underlying Godot architecture (Node, Scene, Resource, Signal, and Group relationships) and GDScript language basics - signals, @export and @onready annotations, static typing - that the patterns build on.

Built for the Godot 4.x engine and its native GDScript language; patterns use Godot APIs directly (FileAccess, ResourceLoader, Area2D, CanvasLayer, Node.PROCESS_MODE flags) with no external dependencies. Points to the official Godot documentation, GDQuest tutorials, and Godot Recipes as further reading.

Godot 4 game developers who need battle-tested GDScript architecture rather than ad hoc scripts - from state management and combat systems to scene transitions and save and load - plus concrete performance guidance for keeping games running smoothly.