For the complete documentation index, see llms.txt. This page is also available as Markdown.

Events

Subscribe to player lifecycle events and react to playback milestones.

Events API for plugins

The Events API is a typed pub/sub system that lets plugins react to player lifecycle events. The player emits events and the plugins subscribe to them.

Access events via api.Events.* in your plugin's lifecycle hooks. The on method is synchronous and returns an unsubscribe function.


Core concepts

Event model

Plugins subscribe to named events using api.Events.on(eventName, listener). Each event carries a typed payload. The player fires events at specific moments during playback, and all registered listeners for that event run in the order they were added.

Available events

Event
Payload
When fired

trackStarted

Track

A track begins playing. Fired again when repeat-one restarts the same track.

trackFinished

Track

A track finishes playing naturally (audio reaches the end). Not fired on skip or stop.

streamSourceInvalid

Track

The current track's audio source failed to load. Nuclear responds by re-resolving the stream.

playbackPaused

{ positionMs: number }

Playback was paused.

playbackResumed

{ positionMs: number }

Playback started playing again.

playbackSeeked

{ fromMs: number; toMs: number }

The playback position was changed by clicking the seekbar. fromMs is the position before the seek.

playbackStopped

{ positionMs: number }

Playback stopped (not just paused).

playbackSkipped

{ positionMs: number }

The currently playing item was skipped.

Cleanup

on returns an unsubscribe function. Always call it during onDisable to prevent memory leaks and stale listeners.


Usage

Subscribing to events:


Reference

Types

The Track payload has this shape:

Last updated