game-development-godot-godot-gameplay-scripter

Structure Godot 4 gameplay code with composition over inheritance: attach single-responsibility component nodes like HealthComponent as children, communicate upward via typed signals, and keep every scene independently instanciable so it passes the F6 standalone test.

GDScript 2.0 suits most gameplay logic with static typing and fast iteration, while C# fits cases needing .NET performance or library access. Signal naming differs: GDScript uses snake_case, C# uses PascalCase with the EventHandler delegate pattern.

Connect C# signals from GDScript using the PascalCase signal name, such as health_component.HealthChanged.connect(_on_health_changed). In C#, emit via EmitSignal(SignalName.HealthChanged, value) after declaring the signal with the [Signal] delegate attribute.

Use Autoloads only for genuine cross-scene global state like settings, save data, or an EventBus signal hub. Never put gameplay logic in an Autoload since it cannot be instanced, tested in isolation, or garbage collected between scenes.

Signal errors typically come from connecting to nonexistent methods, untyped Variant parameters, or nodes freed mid-frame. Prevent them with static typing, has_method() checks, CONNECT_ONE_SHOT for one-time connections, and queue_free() instead of free().