Inspect, link, and update plugins

Before you begin

You need access to a game server whose agent supports plugin inspection. Installing or replacing jars also needs the applicable file and plugin actions. Keep the original runtime console available.

A companion-plugin integration and a catalog link are different. An integration exposes plugin-specific runtime data. A catalog link associates an installed plugin with a release source for metadata and update checks.

Inspect an installed plugin

1. Open Plugins on the intended server.
2. Find the plugin in Installed Plugins and review its version and state.
3. Confirm the plugin identity before selecting an action.
4. If an integration panel is missing, check that the plugin loaded successfully and that the agent reports its capability.

Use the original startup log to investigate a plugin that fails before EnderDash can inspect it.

Link release metadata

Open Link plugin, search for the matching project, and choose the correct provider and project. Confirm the author and project identity before choosing Link or Relink.

A similar name is not enough to identify a trusted release source. A catalog link does not install or enable a runtime plugin by itself.

Apply a supported update

1. Review the linked release and its runtime compatibility.
2. Preserve the current jar and plugin configuration outside the replacement path.
3. Use the available update action, such as Update now, when the runtime supports it.
4. Follow the plugin's restart requirements. Do not assume an updated jar hot-reloads safely.
5. After restart, verify the installed version, startup log, and a relevant plugin operation.

If you use a manual upload, choose the correct plugin directory in Files and verify the resulting jar before restarting.

Investigate an unavailable operation

The server can support inspection without supporting a particular installation or update workflow. Check the runtime, catalog compatibility, agent permissions, and filesystem access.

For plugin-specific panels, read plugin integrations. For replacement files, use file transfers.