Come chat with us and we will get back to you as soon as possible!
Contact SupportHolyHosting
Holy Team

Minecraft Bedrock addons let you change how a world behaves without using Java mods or traditional plugins. Most addons include a behavior pack, and many also include a resource pack for textures, models, sounds, or UI changes. When installed correctly, everyone joining the server can use the same content instead of each player having to guess what goes where.
This guide explains two common methods: adding packs to an existing Bedrock server world, or activating the addons in singleplayer first and then uploading that world to your server.

Download the addon you want to use from a trusted source such as CurseForge, MCPEDL, or the creator's own website. Bedrock addons usually come as `.mcpack` or `.mcaddon` files. Save them somewhere easy to find, such as your desktop, because hunting for one tiny file in Downloads is a hobby nobody asked for.
Avoid encrypted Marketplace content for Bedrock Dedicated Servers. Marketplace packs are normally licensed to the purchasing account and often do not work properly when uploaded to a public server. Addons from third-party sites are usually the better option for server use.
Before changing anything, create a backup of the current world. Addon installation changes files inside the active world folder, and a backup gives you a clean rollback point if the pack is incompatible or the JSON is entered incorrectly. Also confirm the addon supports your server's Bedrock version. A pack made for an older release may import successfully but still fail once entities, items, or scripts try to load.
Recent Bedrock server changes make this more hands-on than simply uploading one file. You will need to extract the addon, upload its folders, then register the pack IDs in your world files.
Next, open the `manifest.json` file inside the behavior folder with a text editor.

Copy the UUID and version values near the top of the file. Keep them in a note for later, since they are required when activating the pack in the world configuration.

After that, compress the extracted `behaviors` folder into `behaviors.zip`, and compress the `resources` folder into `resources.zip`. Keep both zip files ready for upload.
If the addon contains only a behavior pack or only a resource pack, upload and register only the part that exists. Some packs split these folders into separate downloads, so read the creator's instructions before assuming something is missing.





Once both folders are extracted, rename them to something recognizable, such as the addon name. This is optional, but it helps when you later manage several packs on the same server.
Open your active world folder inside the `worlds` directory. In that world folder, create a new file named `world_behavior_packs.json`.

Add the following structure, replacing `UUID` and `version` with the values copied from the behavior pack manifest:
```json [ { "pack_id": "UUID", "version": [version] } ] ```

Save the file, then create another file named `world_resource_packs.json` for the resource pack. Use the UUID and version from the resource pack manifest if it has separate values.
When both JSON files are saved, return to the main panel and start the server. Join from Minecraft Bedrock to confirm the addon loads correctly.
If you already have a Bedrock world where the addon works in singleplayer, you can export that world and upload it to the server. This is often easier because the world already contains the addon references.
If the pack is not enabled in the singleplayer world yet, import it first.



If the addon also has a resource pack, check the Resource Packs section and activate it there too.


You can also use your operating system's file properties menu to change the extension. If you rename the world itself, use standard letters, numbers, spaces, hyphens, or underscores. Special characters can create avoidable server path issues.
For larger worlds, an external FTP program is usually more reliable than a browser upload.




After the restart, join the server from Minecraft Bedrock and check whether the addon content appears in game.
To load more than one behavior pack or resource pack, add another object to the matching world JSON file. The format should look like this:
```json [ { "pack_id": "first-uuid", "version": [1, 0, 0] }, { "pack_id": "second-uuid", "version": [1, 0, 0] } ] ```
Each entry needs a comma between it and the next one. Missing commas, extra brackets, or a version written in the wrong format can stop the pack from loading. JSON is strict, and it will not politely guess what was meant.
If uploads fail in the browser file manager, switch to FileZilla, Cyberduck, or another full FTP client. Large worlds and addon folders are more stable that way.
If FTP will not connect, compare the host, port, username, and password with the values shown in your panel. A copied space at the start or end of a field is enough to cause a login failure. If the details are correct, reset the password and try again.
If a world does not appear after upload, make sure the server has an extracted folder inside `worlds`. The server cannot load the world directly from `.zip` or `.mcworld` format.
If the uploaded singleplayer world is missing from Minecraft Bedrock on Windows, restart the game and confirm it was placed in the correct local folder:
```text ...\AppData\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\minecraftWorlds ```
If the server starts but players cannot join, temporarily remove the newest addon and restart. This helps confirm whether the pack itself is blocking connections. Also check whether the pack uses experimental features, scripts, or beta APIs, since those may require matching world settings or may not be supported on every server build.
If an addon works in singleplayer but not on the server, check that the behavior pack and resource pack were both activated before export, or that the UUID and version values were copied correctly for manual installation. If the addon fails everywhere, it may be outdated or broken for your current Bedrock version.
Come chat with us and we will get back to you as soon as possible!
Contact SupportMake every block, mob, and tool in Minecraft look like Lego pieces. This guide walks through downloading, installing, and running Brickcraft on both client and server.
Learn how to install Litematica for Minecraft, load schematic files, position blueprints, and use the material list for survival builds.
Set up Valhelsia Enhanced Vanilla for Minecraft, install the client profile, configure your server, and learn the early skills, items, and fixes that help the pack run smoothly.