Installing Endstone plugins and Bedrock addons

There are two different ways to extend a Bedrock server, and they work completely differently. Which one you use depends on what you're installing.

• Endstone plugins load into the server and add server-side behaviour (permissions, economy, moderation tools, and so on).
• Bedrock addons attach to your world, not the server. They're the same behavior/resource packs you'd use in single-player — custom mobs, items, textures, and mechanics.

Everything below is done from the File Manager and Console in your ServerPrism panel. Both work fine on mobile, so you don't need a desktop for any of this.

Endstone plugins (.whl files)

1. Open File Manager and go to the plugins/ folder.
2. Upload the plugin's .whl file into it.
3. Restart the server from the panel.
4. The plugin auto-loads on boot. Watch the Console — you'll see a line like Loaded plugin: X when it registers successfully.

That's the whole flow. If a plugin needs configuration, it'll usually generate a config file inside plugins/ on first start that you can then edit in File Manager and restart to apply.

You can browse most available plugins under the endstone-plugin topic on GitHub.

Bedrock addons (.mcpack / behavior + resource packs)

Addons attach to a world, so the files go under that world's folder rather than the server root. A .mcpack is just a renamed .zip — inside it you'll find a behavior pack, a resource pack, or both.

1. In File Manager, navigate to your world: worlds/<yourworld>/.

2. Put the behavior pack into worlds/<yourworld>/behavior_packs/ and the resource pack into worlds/<yourworld>/resource_packs/. (An addon may include only one of the two.)

3. Open the pack's manifest.json and note its UUID and version (the header block — "uuid" and "version": [x, y, z]).

4. Register the pack with your world by adding that UUID + version to:

   • worlds/<yourworld>/world_behavior_packs.json (for behavior packs)
   • worlds/<yourworld>/world_resource_packs.json (for resource packs)

   Each entry looks like this:

   [
     {
       "pack_id": "PASTE-UUID-FROM-MANIFEST",
       "version": [1, 0, 0]
     }
   ]
   

   If the file already has entries, add yours to the existing list rather than replacing it.

5. Restart the server. The addon applies to the world on next load.

If the addon doesn't show up in-game, double-check that the UUID matches the one in manifest.json exactly and that the version array matches — a mismatch is the most common reason a pack silently fails to load.

Still stuck?

If you have a specific plugin or addon in mind, open a support ticket with the link and we'll walk you through it — or install it on your server directly so you can see how it works.