How to install Behavior Packs (Addons) on Minecraft Bedrock

Context

Behavior Packs (addons) on Minecraft Bedrock allow you to deeply modify your server's gameplay: mob behaviors, game mechanics, crafting systems, events, and much more.

Thanks to them, you can completely transform your gaming experience without needing client-side mods.

Where to find Behavior Packs?

To download reliable and compatible Minecraft Bedrock addons, here are the main sources:

🌍 MCPEDL → the community reference for Minecraft addons
🌍 ModBay → recent and regularly updated addons
📦 GitHub / Discord → independent creator projects

File Format

To be installed and manually configured on your server hosted at Winheberg, addons must be handled as compressed archives in .zip format.

If you download a pack with an automated extension, simply change the file extension to .zip. You can then open it with any decompression software to check its contents and extract the internal folders.

Installing a Behavior Pack

1. Prepare the archive

Make sure you have the Behavior Pack of your choice as a .zip archive.

2. Extract the files

Right-click your .zip file.
Select the extraction option to get the decompressed folder.

For the pack to be valid, this folder must strictly contain the manifest file at its root:

manifest.json

3. Upload the pack to the server

Log in to your panel.winheberg.com.
Select your instance and open the File Manager.
Navigate to your current world folder.

Drop the extracted folder of your Behavior Pack into the following directory:

behavior_packs

If the behavior_packs folder is not present at this location, you can easily create it manually directly from the panel interface.

4. Handle the Resource Pack (optional)

If your addon also includes visual elements or textures, you must separate the visual part and place it in the folder:

resource_packs

Activating addons on the world

Importing files is not enough; the server engine must index your addons via a configuration file to load them at startup.

1. Access world files

From the File Manager:

Go to the root directory of your server.
Open the world folder (or the custom name of your active map).

2. Create the configuration file

In your world folder, create a new document named exactly:

world_behavior_packs.json

Open it and apply the following JSON structure:

[
  {
    "pack_id": "UUID_OF_THE_PACK",
    "version": [1, 0, 0]
  }
]

3. Retrieve the UUID and version

To correctly fill the JSON file, open the manifest.json document located at the root of your addon folder (extracted from your .zip).

Copy the value of the uuid field to insert it in place of UUID_OF_THE_PACK, and carefully report the three numbers from the version section.

4. Accumulate multiple addons

To activate multiple packs simultaneously, separate the data blocks with a comma respecting JSON array syntax:

[
  {
    "pack_id": "UUID_OF_THE_PACK_1",
    "version": [1, 0, 0]
  },
  {
    "pack_id": "UUID_OF_THE_PACK_2",
    "version": [1, 2, 0]
  }
]

Resource Packs (associated textures)

If your addon strictly requires its textures to work:

Validate that the visual part is uploaded to the general resource_packs folder.
Create a second configuration file in your world folder named:

world_resource_packs.json

Use the same structure and identifiers from the resource part manifest.

Troubleshooting

❌ The server crashes on startup or refuses to launch

JSON Syntax Error: The JSON format is extremely strict. A missing comma at the end of a line or an improperly closed bracket in your world_behavior_packs.json file will cause the instance to crash. Use an online JSON validator to verify your file syntax.
Version Incompatibility: Make sure the addon supports the current version of Minecraft Bedrock running on your server.

❌ The addon is completely ignored and does not appear in-game

Incorrect Internal Directory Structure: Open your directory inside behavior_packs. The manifest.json file must be located immediately at the root of this folder. If it is hidden inside an intermediate subfolder created during extraction, the server won't be able to scan it.

❌ Addon textures display as black and purple checkered blocks

Missing or Undeclared Resource Pack: Most gameplay addons strictly require their twin texture pack to display items properly. Double-check that the assets part is successfully uploaded to the main resource_packs directory and properly indexed inside your world's world_resource_packs.json file.

Administrative Best Practices

Prioritize Backups: Before injecting any new addon or modifying your JSON configuration files, systematically run a full backup from the Backups tab on your panel. A corrupted or poorly coded addon can permanently damage your world save file data.
Handling Load Conflicts: If you run multiple Behavior Packs affecting identical entities (e.g., modifying Zombie attributes), note that the layout order inside the JSON file sets the final priority. The pack placed lowest in the list overrides any matching settings from packs listed above it.
UUID Compliance: Never copy-paste an existing JSON data block just to manually change the name tags. Every single addon carries its own distinct unique identifier (UUID) generated by its creator inside its core manifest.

Need help?

Setting up custom gameplay elements requires high precision in folder structure and JSON file writing.

If your server refuses to start after your modifications or if the configuration files remain inoperative, our technical team is by your side. Open a support ticket from your client area on billing.winheberg.com to get personalized help.

Happy configuration and have fun on your game server! 🎮