Custom signals

Subscribe to a Kawaii runtime event such as WebSocket.OnMessage. Keep the returned connection if you may need to unsubscribe before the event source closes.

Forward values through a Kawaii runtime event object. This is mainly useful when manually exercising listeners of an event supplied by another API.

Listen for the next event from a Kawaii runtime signal and then disconnect automatically. This works well for a single reply or close notification.

Suspend until a Kawaii runtime event fires, then receive its arguments. Use it for a one-off event when you do not need a persistent callback.

Subscribe a callback to a custom Signal. Each Fire call sends its arguments to the callback until the returned connection is disconnected.

Finish using a custom Signal by disconnecting its callbacks and clearing its waiting coroutines. Call it during cleanup for UI or temporary systems.

Remove every callback subscription from a custom Signal while keeping the Signal available for new listeners.

Send an event to the callbacks and coroutines waiting on a custom Signal. Use it after your script changes state that subscribers need to know about.

Subscribe a callback for just the next firing of a custom Signal. The listener disconnects before its callback runs.

Pause the calling coroutine until the next Fire, then receive that firing’s arguments. This is convenient for a short one-time handoff between script tasks.

Create a small custom event for communication between parts of your own script. Unlike a Roblox Instance event, this signal lives entirely in Luau and needs no BindableEvent.

Stop a single callback subscription created by Signal:Connect or Signal:Once. Other listeners on the same custom Signal continue receiving events.