Godot signals: reduce coupling while keeping connection lifetimes explicit

Choose the relationship you need

A door opening and a request to open a door are different interactions. The request needs a responsible recipient that can accept or reject it. The completed opening can interest sound, objectives and interface code independently. Distinguish these relationships before choosing a communication mechanism. It makes the feature easier to understand when another system later wants to observe it.

Signals announce events

Godot signals let objects react to changes without requiring the emitter to know each receiver. [1] Use a signal to announce a completed state change, with enough context for listeners to interpret it. Prefer a direct method call when the caller already owns the target and needs an immediate result. Neither mechanism removes the need for a clear contract about when state changes.

Connections have lifetimes

A normal signal connection to a callable is lost when that callable’s object is freed. is_connected() can check whether a connection exists before connecting or disconnecting. [2] Hiding a panel or temporarily removing it from active use is not the same as freeing it. Define whether its subscription lasts for its whole object lifetime or only while it is participating in the feature.

Example: an airlock control panel

Imagine a panel that requests an airlock opening through a direct method. The airlock checks its interlocks, updates its state and emits airlock_opened only after the opening has actually happened. A sound listener and a mission listener subscribe independently. A temporary status panel subscribes while it is shown, reads an initial state snapshot, and disconnects when its observation period ends. Reopening that panel should produce one active subscription rather than another layer of callbacks. If the airlock opens while the panel is absent, the snapshot shows the correct state on return; the panel does not need a replay of every earlier signal.

Limits and verification

Signals are notifications, not an automatic event history or ownership system. Keep ordering-sensitive operations under one explicit coordinator instead of relying on unrelated listeners to run in a convenient sequence. In C#, captured lambdas and custom signals connected with += have automatic-disconnection exceptions; follow the documented cleanup rules. [3] Test repeated panel opening, listener destruction, scene replacement and an event emitted during teardown. Check both missed updates and duplicate reactions. Match connection APIs and language-specific lifetime behaviour to the Godot version used by the project.

Sources

1. Using signals — Godot Engine contributors.
2. Signal class reference — Godot Engine contributors.
3. C# signals — Godot Engine contributors.