Skip to content
ROMOSLAYERARK PLUGINS
Getting Started

Updating Plugins

How to move a server to a newer plugin build safely.

Updating replaces the plugin build on each server. On a cluster, move every map to the same version so behaviour stays consistent between them.

Standard update

  1. Stop the server.
  2. Replace the plugin file with the new build.
  3. Start the server.
  4. Confirm the startup log reports the version you expect.

Hot reload

Some plugins can be updated without downtime. Writing the new build alongside the existing one with an .ArkApi suffix lets the loader pick it up, unload the running plugin and reload it in place:

path
<PluginName>.dll.ArkApi

Check the individual plugin's documentation before relying on this — it is confirmed for StructurePickUpBalance, not for every plugin.

Configuration is read at load

Editing a configuration file does nothing until the plugin reloads. If you change config during a live session, say so plainly to whoever is testing — the change is not active until a restart or reload.

Release notes

Each plugin has its own changelog listing what changed in a release — for example the ClusterSync changelog.