Addons

Addons extend IgniteSky with standalone jars. You drop them in a folder, IgniteSky loads each on startup, hands it a typed API, and tears it down cleanly on shutdown or reload. This page is the operator side; if you want to write one, see the Addon API.

Installing an addon

    1. Drop the jar in

      Put the addon jar in plugins/IgniteSky/addons/.

    2. Load it

      Start the server, or run /is admin addons reload to load it without a restart.

    3. Confirm it loaded

      Run /is admin addons to list everything currently loaded, with name, version and description.

CommandWhat it does
/is admin addonsList loaded addons
/is admin addons reloadDisable and reload every addon from disk

What each addon gets

ResourceDetail
Its own classloaderIsolated from other addons
A private data folderaddons/<name>/
A persistent key-value storeaddons/data/<name>.json
A bad addon cannot crash your server

If an addon fails to load or errors, IgniteSky logs it and skips it. The server stays up and the other addons keep running.

Typed, not reflective

Addons talk to IgniteSky only through the public API, as a real compile time dependency. There is no reflection into internals, which means addons keep working across updates instead of breaking when an internal field is renamed.

Edit this page on GitHub