Gotchas

This page collects common issues and misunderstandings within code that uses NamedSignal (and Signal libraries in general).

Signals do not communicate across Luau VMs or network

NamedSignal is a pure-Luau implementation, and as such cannot facilitate communication between Luau VMs, and also cannot communicate across the network boundary. Roblox engine APIs should be used instead, such as the Actor Messaging API or RemoteEvent Instance.

Errors are not logged when using coroutine resumption

Errors don't get logged in the output when using coroutine invoke resumption, enable USE_TASK_LIBRARY in the main NamedSignal module to get error information (if available).

const USE_TASK_LIBRARY = true

Re-entrancy does not yield

Unlike other Signal libraries that implement deferred mutations, NamedSignal does not yield the calling thread for re-entrant firing. See 'Not Quite to Spec' for detailed information and reasoning.

As such, deferred mutations that immediately follow in the same listener can precede mutations made by the next listener in line to be invoked.

For example, with 2 listeners:

-- Listener #1:
	Signal:Fire()     -- This never yields!
	Signal:Connect()  -- Queued before Listener #2 runs

-- Listener #2:
	Signal:Connect()

If you for some reason require the fire to yield, you can use the following:

-- Listener #1:
	Signal:Fire()
	Signal:WaitNow() -- Waits until the end of the current invocation
	Signal:FireNow() -- Fires immediately
	Signal:Connect()