---
name: csharp-signals
description: Use when implementing signals in C# — [Signal] delegates, EmitSignal patterns, and async signal awaiting. Triggers on declaring, emitting, connecting, or awaiting a signal from a C# script, and on a signal crossing between C# and GDScript in either direction.
title: csharp-signals
canonical_url: https://skilld.dev/gh/jame581/godotprompter/csharp-signals
last_updated: 2026-11-13T22:06:02.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/awaiting-signals.md](https://skilld.dev/api/skills-raw/jame581/godotprompter/csharp-signals/references/awaiting-signals.md), [references/connecting-gdscript-signals.md](https://skilld.dev/api/skills-raw/jame581/godotprompter/csharp-signals/references/connecting-gdscript-signals.md), [references/custom-signal-patterns.md](https://skilld.dev/api/skills-raw/jame581/godotprompter/csharp-signals/references/custom-signal-patterns.md), [references/disconnecting.md](https://skilld.dev/api/skills-raw/jame581/godotprompter/csharp-signals/references/disconnecting.md).
>
> If the user asked to install this Skill, run `npx skilld install jame581/godotprompter/csharp-signals`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/csharp-signals`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jame581/godotprompter/csharp-signals) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/csharp-signals`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/csharp-signals --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/csharp-signals --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Signals in C# (Godot 4.x)

This skill is **C# only**. For general C# conventions and project setup, see the **csharp-godot** skill. Godot signals in C# require a different mental model from GDScript: delegates declared with `[Signal]`, strongly-typed `+=`/`-=` connections, and mandatory disconnection in `_ExitTree()`. All examples target Godot 4.x with no deprecated APIs.

> **Related skills:** **csharp-godot** for C# conventions and project setup, **event-bus** for global signal hub architecture, **component-system** for signal-based component communication.

---

## 1. Signal Declaration

Signals are declared as `public delegate void` with the `[Signal]` attribute inside a `partial class` that extends a Godot type. The delegate name **must** end with `EventHandler` — Godot strips that suffix to produce the signal name exposed to the engine.

```csharp
using Godot;

public partial class Player : CharacterBody2D
{
    // Signal name in engine: "HealthChanged"
    [Signal] public delegate void HealthChangedEventHandler(int current, int maximum);

    // Signal name in engine: "Died"
    [Signal] public delegate void DiedEventHandler();

    // Signal name in engine: "ItemCollected"
    [Signal] public delegate void ItemCollectedEventHandler(string itemName);
}
```

**Naming rules:**

| Delegate name                   | Engine signal name  |
|---------------------------------|---------------------|
| `HealthChangedEventHandler`     | `HealthChanged`     |
| `DiedEventHandler`              | `Died`              |
| `ItemCollectedEventHandler`     | `ItemCollected`     |
| `PlayerSpawnedEventHandler`     | `PlayerSpawned`     |

Omitting the `EventHandler` suffix is a compile error: the source generator reports GD0201, "The name of the delegate must end with 'EventHandler'".

**Parameter type constraints:** Signal parameters must be `Variant`-compatible: numeric types, `bool`, `string`, enums, Godot structs (`Vector2`, `Color`, …), `StringName`, `NodePath`, `GodotObject` subclasses, `Godot.Collections.Array`/`Dictionary` (including the generic `Array<T>`/`Dictionary<TKey, TValue>`) and packed-array equivalents such as `int[]`. Other C# classes and structs fail the build with GD0202.

---

## 2. Emitting Signals

Use `EmitSignal(SignalName.SignalName, args...)`. The `SignalName` nested class is auto-generated by the Godot source generators at build time — one cached `StringName` per declared signal.

```csharp
using Godot;

public partial class Player : CharacterBody2D
{
    [Signal] public delegate void HealthChangedEventHandler(int current, int maximum);
    [Signal] public delegate void DiedEventHandler();
    [Signal] public delegate void ItemCollectedEventHandler(string itemName);

    [Export] public int MaxHealth { get; set; } = 100;
    private int _currentHealth;

    public override void _Ready()
    {
        _currentHealth = MaxHealth;
    }

    public void TakeDamage(int amount)
    {
        _currentHealth = Mathf.Clamp(_currentHealth - amount, 0, MaxHealth);

        // Type-safe emission — SignalName.HealthChanged is a generated constant.
        EmitSignal(SignalName.HealthChanged, _currentHealth, MaxHealth);

        if (_currentHealth == 0)
            EmitSignal(SignalName.Died);
    }

    public void CollectItem(string itemName)
    {
        EmitSignal(SignalName.ItemCollected, itemName);
    }
}
```

`EmitSignal` does not check its arguments against the delegate. With the wrong argument count, `+=` handlers on a custom `[Signal]` are skipped without an error, and `Connect`/GDScript receivers log `Error calling from signal … Method expected N argument(s), but called with M`. With a wrong type, C# handlers get the value converted or defaulted (`0`, `null`); a typed GDScript receiver logs `Cannot convert argument N from X to Y` and is not called.

---

## 3. Connecting Signals

### The `+=` operator (preferred)

```csharp
using Godot;

public partial class HudLayer : CanvasLayer
{
    private Player _player;

    public override void _Ready()
    {
        _player = GetNode<Player>("../Player");

        // Connect with += — mirrors C# event syntax.
        _player.HealthChanged += OnHealthChanged;
        _player.Died          += OnDied;
        _player.ItemCollected += OnItemCollected;
    }

    private void OnHealthChanged(int current, int maximum)
    {
        GetNode<ProgressBar>("HealthBar").Value = (double)current / maximum * 100.0;
        GetNode<Label>("HealthLabel").Text = $"{current} / {maximum}";
    }

    private void OnDied()
    {
        GetNode<Control>("DeathScreen").Show();
    }

    private void OnItemCollected(string itemName)
    {
        GetNode<Label>("PickupLabel").Text = $"Picked up: {itemName}";
    }
}
```

### Lambda connections

Use lambdas for one-off, short-lived responses. Store the lambda in a field if you need to disconnect it later.

```csharp
// Anonymous lambda — cannot be disconnected by reference later.
_player.Died += () => GetNode<AudioStreamPlayer>("DeathSound").Play();

// Stored lambda — can be disconnected.
private Action<string> _onItemCollected;

public override void _Ready()
{
    _onItemCollected = (itemName) =>
    {
        _collectCount++;
        UpdateCollectDisplay();
    };
    _player.ItemCollected += _onItemCollected;
}

public override void _ExitTree()
{
    _player.ItemCollected -= _onItemCollected;
}
```

### Connecting in `_Ready()`

Connect inside `_Ready()` — or `_EnterTree()` for a node that is removed and re-added, since `_Ready()` runs only once. The node's references are resolved and the scene tree is available at that point. Connecting in the constructor or field initializers may fail because Godot node infrastructure is not yet initialised.

---

## 4. Disconnecting Signals

When a `GodotObject` is freed, Godot disconnects its connections, for emitters and receivers alike. Two cases are **not** cleaned up when the receiver is freed while the emitter lives on: a `+=` on a **custom `[Signal]`**, and a **lambda that captures a variable**. In both, the next emission reaches a disposed object and throws `ObjectDisposedException`, so disconnect with `-=` yourself in `_ExitTree()`. For a node that can leave and re-enter the tree, connect in `_EnterTree()` instead of `_Ready()`, which runs only once.

> See [references/disconnecting.md](https://skilld.dev/api/skills-raw/jame581/godotprompter/csharp-signals/references/disconnecting.md) for the `-=` cleanup pattern, the two cases Godot does not clean up, and a SafeDisconnect helper.

---

## 5. Awaiting Signals

`await ToSignal(node, SignalName.X)` pauses until the signal fires. Returns `Variant[]` of the signal's args. Add a timeout with `Task.WhenAny` or a `CancellationTokenSource` to avoid permanent hangs.

> See [references/awaiting-signals.md](https://skilld.dev/api/skills-raw/jame581/godotprompter/csharp-signals/references/awaiting-signals.md) for basic await, return-value extraction, and both timeout patterns.

---

## 6. Custom Signal Patterns

Three patterns: **typed event args** (wrap signal payload in a Resource subclass), **static event bus** (use C# `static event` as a pure-C# alternative when both peers are C#), **generic signal helper** (one helper per `SignalName.X` to reduce repetition).

> See [references/custom-signal-patterns.md](https://skilld.dev/api/skills-raw/jame581/godotprompter/csharp-signals/references/custom-signal-patterns.md) for full code on each pattern.

---

## 7. Connecting GDScript Signals from C#

When the signal is declared in a GDScript node and the listener is C#, use `node.Connect("signal_name", new Callable(this, MethodName.Handler))`. The `MethodName` generated symbol still works for C# methods.

> See [references/connecting-gdscript-signals.md](https://skilld.dev/api/skills-raw/jame581/godotprompter/csharp-signals/references/connecting-gdscript-signals.md) for the full pattern with both string-name and `MethodName` variants.

---

## 8. Common Mistakes

| Mistake | Symptom | Fix |
|---|---|---|
| Forgetting `EventHandler` suffix on the delegate | Build fails with GD0201: the delegate name must end with 'EventHandler' | Rename to `XxxEventHandler` |
| Wrong parameter types in `EmitSignal` | C# handlers: no error, the value is converted or defaulted (`0`, `null`); typed GDScript receivers: `Cannot convert argument N from X to Y`, handler not called | Match `EmitSignal` args exactly to the delegate signature |
| Connecting to a freed object | `ObjectDisposedException` or silent crash on next signal emission | Guard with `IsInstanceValid` before connecting; store reference safely |
| Not disconnecting a custom `[Signal]` or a capturing lambda | `ObjectDisposedException` on the next emission after the receiver is freed; built-in signals with a method handler are cleaned up automatically | Add a matching `-=` in `_ExitTree()` (or `Dispose()`) for those two cases |
| Passing wrong argument count to `EmitSignal` | `+=` handlers silently not called; `Connect`ed receivers log "Method expected N argument(s), but called with M" | Count signal delegate parameters and match exactly |
| Using static C# events for cross-language signals | GDScript cannot observe the event; no error, just silent non-delivery | Use Godot `[Signal]` for any signal GDScript must receive |
| Double-connecting the same handler | On a custom `[Signal]` the handler fires twice per emission; on a built-in signal the second `+=` logs "already connected" | Check if already connected, or use `ConnectFlags.OneShot`; never call `+=` twice for the same method |
| Awaiting a signal in `_Ready()` before the tree is ready | `NullReferenceException` or signal never resolves because the source node is not yet in the tree | Defer with `await ToSignal(GetTree(), SceneTree.SignalName.ProcessFrame)` first, or move the await to a method called after `_Ready()` |

---

## 9. Checklist

- [ ] Every `[Signal]` delegate name ends with `EventHandler`
- [ ] `EmitSignal` uses `SignalName.XxxName` constants (not raw strings)
- [ ] `EmitSignal` argument count and types match the delegate signature exactly
- [ ] All `+=` connections are in `_Ready()` (not in constructors or field initializers)
- [ ] Every `+=` on a custom `[Signal]`, and every capturing lambda, has a matching `-=`
- [ ] `IsInstanceValid` guards are in place where the signal source may be freed before the subscriber
- [ ] Lambdas stored in fields if disconnection is needed later
- [ ] `async` signal awaits are not blocking `_Ready()` directly; deferred if necessary
- [ ] Cross-language signals (GDScript emitter, C# subscriber) use `Connect("snake_case_name", Callable.From<T>(Method))`
- [ ] Static C# events used only for pure-C# communication paths
- [ ] `RefCounted`-derived wrapper classes used for complex signal payloads, not plain C# classes or structs
