This guide explains how to upload a Minecraft Bedrock world to your CloudNord server and correctly install the Resource Packs (RP) and Behavior Packs (BP) required by the world.

Resource Packs are commonly used for custom textures, models, sounds, UI changes, and other visual features, while Behavior Packs can add or modify gameplay, entities, items, blocks, recipes, functions, and other mechanics.

For a world downloaded from a marketplace, website, creator, or another source, the world may require both packs to work correctly.

---

What you will need

Before starting, make sure you have:

• A Minecraft Bedrock server on CloudNord

• Your Bedrock world

• The Resource Pack(s), if required

• The Behavior Pack(s), if required

• Access to the CloudNord File Manager

Your world and packs may be provided as .zip files. You can upload these directly to the File Manager and use the Decompress option to extract them.

---

1. Stop your server

We recommend stopping the server before uploading or replacing a world or its packs.

1. Open your CloudNord server.

2. Go to the server Console.

3. Click Stop.

4. Wait until the server has completely stopped.

This prevents the server from accessing the files while you are modifying them.

---

2. Open the File Manager

Go to the Files section of your server.

Your Bedrock world should be located at:

/home/container/worlds/level

Open:

worlds → level

This is the directory where your world files should be placed.

---

3. Upload your Minecraft Bedrock world

Upload your world files into:

/home/container/worlds/level

If your world is provided as a ZIP file:

1. Upload the ZIP file.

2. Select the ZIP file.

3. Click Decompress at the top of the File Manager.

4. Wait for the extraction to finish.

After extracting the world, make sure the actual world files are inside the level folder.

For example:

worlds/
└── level/
    ├── level.dat
    ├── levelname.txt
    ├── db/
    ├── world_behavior_packs.json
    ├── world_resource_packs.json
    └── ...

The exact files can vary between worlds.

Important

Make sure you don't accidentally create an extra directory level.

For example, if your files end up like this:

worlds/
└── level/
    └── MyWorld/
        ├── level.dat
        └── db/

the server may not load the world correctly.

Ideally, the world files should be directly inside:

/home/container/worlds/level/

So you should have:

/home/container/worlds/level/level.dat

rather than:

/home/container/worlds/level/MyWorld/level.dat

---

4. What is a Resource Pack?

A Resource Pack controls the visual and audio content of Minecraft.

Depending on the pack, it can add or modify:

• Textures

• Models

• Sounds

• Animations

• UI elements

• Custom item appearances

• Custom block appearances

• Entity appearances

Resource Packs are commonly referred to as RP.

A Resource Pack normally contains a file called:

manifest.json

This file tells Minecraft important information about the pack, including its name, UUID, and version.

---

5. Upload the Resource Pack

Open the following directory:

resource_packs

Then upload your Resource Pack.

If it is provided as a ZIP file:

1. Upload the ZIP.

2. Select the ZIP file.

3. Click Decompress.

4. Wait for the extraction to finish.

A typical structure should look similar to:

resource_packs/
└── MyResourcePack/
    ├── manifest.json
    ├── textures/
    ├── models/
    ├── sounds/
    └── ...

The exact folders depend on the Resource Pack.

---

6. What is a Behavior Pack?

A Behavior Pack controls gameplay-related features.

Depending on the pack, it can add or modify:

• Mobs and entities

• Custom items

• Custom blocks

• Recipes

• Loot tables

• Functions

• Gameplay mechanics

• Entity behavior

• Scripts

• Other gameplay features

Behavior Packs are commonly referred to as BP.

Just like Resource Packs, a Behavior Pack normally contains:

manifest.json

The manifest identifies the pack and contains its UUID and version.

---

7. Upload the Behavior Pack

Open:

behavior_packs

Upload your Behavior Pack.

If it is a ZIP file:

1. Upload the ZIP.

2. Select the ZIP file.

3. Click Decompress.

4. Wait for the extraction to complete.

Your structure should look similar to:

behavior_packs/
└── MyBehaviorPack/
    ├── manifest.json
    ├── entities/
    ├── functions/
    ├── loot_tables/
    └── ...

Again, the exact contents depend on the pack.

---

8. Why does the Resource Pack need to be linked to the world?

This is one of the most important parts of installing Bedrock add-ons.

Simply uploading a Resource Pack to:

resource_packs/

does not necessarily tell your world to use it.

Minecraft Bedrock uses the pack's manifest.json and the world's pack configuration to determine which packs should be loaded.

Inside the Resource Pack's manifest.json, you will normally find information such as:

{
  "header": {
    "name": "My Resource Pack",
    "uuid": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
    "version": [1, 0, 0]
  }
}

The important values here are:

• UUID

• Version

The world can reference these values through:

world_resource_packs.json

---

9. The world_resource_packs.json file

Inside your world directory, you may see:

world_resource_packs.json

For example:

worlds/
└── level/
    ├── level.dat
    ├── db/
    ├── world_resource_packs.json
    └── ...

This file tells Minecraft which Resource Packs the world should use.

A simplified example looks like:

[
  {
    "pack_id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
    "version": [1, 0, 0]
  }
]

The pack_id should correspond to the UUID in the Resource Pack's manifest.json.

The version should also correspond to the version specified by the Resource Pack.

So Minecraft can effectively match:

world_resource_packs.json
        ↓
Pack UUID + Version
        ↓
resource_packs/
        ↓
manifest.json
        ↓
Resource Pack

---

10. The world_behavior_packs.json file

Behavior Packs work in the same way.

The world may contain:

world_behavior_packs.json

This file tells Minecraft which Behavior Packs the world should load.

For example:

[
  {
    "pack_id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
    "version": [1, 0, 0]
  }
]

The UUID and version should correspond to the Behavior Pack's manifest.json.

The relationship looks like:

world_behavior_packs.json
        ↓
Pack UUID + Version
        ↓
behavior_packs/
        ↓
manifest.json
        ↓
Behavior Pack

---

11. Why UUID and version are important

Every Resource Pack and Behavior Pack has its own identifier.

The manifest.json contains information such as:

Pack UUID
Pack Version

The world uses these values to identify the exact pack it needs.

For example:

Resource Pack manifest.json

UUID:
12345678-1234-1234-1234-123456789abc

Version:
1.0.0

The world's:

world_resource_packs.json

should reference the same UUID and version.

If they don't match, Minecraft may not load the Resource Pack correctly.

The same applies to Behavior Packs.

---

12. Complete example

Imagine you downloaded a Bedrock world called Zombie World.

It comes with:

ZombieWorld
ZombieResourcePack
ZombieBehaviorPack

You would have something similar to:

/home/container/
│
├── worlds/
│   └── level/
│       ├── level.dat
│       ├── db/
│       ├── world_resource_packs.json
│       └── world_behavior_packs.json
│
├── resource_packs/
│   └── ZombieResourcePack/
│       └── manifest.json
│
└── behavior_packs/
    └── ZombieBehaviorPack/
        └── manifest.json

The Resource Pack's manifest.json provides its UUID and version.

The world references that UUID and version in:

world_resource_packs.json

The Behavior Pack's manifest.json provides its UUID and version.

The world references those values in:

world_behavior_packs.json

This is how Minecraft knows which packs belong to the world.

---

13. If your world already includes the pack configuration

Many downloadable Bedrock worlds already include:

world_resource_packs.json

and:

world_behavior_packs.json

If these files are included with your world, you normally do not need to create or edit them manually.

Simply make sure the corresponding packs are uploaded to:

/home/container/resource_packs/

and:

/home/container/behavior_packs/

Then make sure their manifest.json files contain the UUID and version expected by the world.

This is usually the easiest and safest way to install a complete downloadable world.

---

14. Do not randomly change the UUID or version

If the world already contains working:

world_resource_packs.json

and:

world_behavior_packs.json

we recommend not changing the UUIDs or versions unless you know exactly what you are doing.

Changing them can cause Minecraft to stop recognizing the packs.

If you need to replace a pack with another version, make sure the UUID and version are correctly configured.

---

15. Check the manifest.json

If a pack isn't loading, open its:

manifest.json

and check the header section.

For example:

{
  "header": {
    "name": "Example Pack",
    "uuid": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
    "version": [1, 0, 0]
  }
}

Make sure:

• manifest.json exists

• The file is inside the actual pack folder

• The UUID is valid

• The version is valid

• The pack is compatible with your Minecraft Bedrock version

---

16. Check dependencies

Some Behavior Packs depend on another Resource Pack or another Behavior Pack.

The manifest.json may contain a section such as:

"dependencies": [
  {
    "uuid": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
    "version": [1, 0, 0]
  }
]

This means the pack requires another pack with that UUID and version.

If a dependency is missing or has the wrong version, the add-on may not work correctly.

---

17. Start the server

Once everything has been uploaded and configured:

1. Return to your CloudNord server Console.

2. Click Start.

3. Wait for the server to finish starting.

4. Connect to the server using Minecraft Bedrock.

5. Check whether the world, Resource Pack, and Behavior Pack are working.

If the world contains a large number of add-ons, the first startup may take longer than usual.

---

18. Troubleshooting

If your Resource Pack or Behavior Pack isn't working, check these things first.

The pack is still a ZIP file

If the server setup requires extracted packs, make sure you have decompressed the ZIP.

You should have:

resource_packs/
└── MyPack/
    └── manifest.json

rather than only:

resource_packs/
└── MyPack.zip

manifest.json is in the wrong location

Incorrect:

resource_packs/
└── MyPack/
    └── MyPack/
        └── manifest.json

Correct:

resource_packs/
└── MyPack/
    └── manifest.json

UUID doesn't match

Check the UUID in:

manifest.json

and compare it with:

world_resource_packs.json

or:

world_behavior_packs.json

Version doesn't match

The version referenced by the world should correspond to the version in the pack's manifest.

Add-on is incompatible

Some Bedrock add-ons only support certain Minecraft versions.

If the pack was created for an older version, it may not work correctly on a newer Bedrock release.

Check the server Console

If the server reports errors while loading the packs, check the Console for messages relating to:

• Invalid manifests

• Missing dependencies

• UUIDs

• Versions

• Scripts

• Unsupported features

• Missing files

These errors can help identify whether the problem is the server configuration or the add-on itself.

---

Recommended folder structure

For a standard CloudNord Bedrock setup, your files should look similar to:

/home/container/
│
├── worlds/
│   └── level/
│       ├── level.dat
│       ├── levelname.txt
│       ├── db/
│       ├── world_resource_packs.json
│       ├── world_behavior_packs.json
│       └── ...
│
├── resource_packs/
│   └── YourResourcePack/
│       ├── manifest.json
│       ├── textures/
│       ├── models/
│       └── ...
│
└── behavior_packs/
    └── YourBehaviorPack/
        ├── manifest.json
        ├── entities/
        ├── functions/
        └── ...

---

Quick summary

The basic process is:

1. Stop the server
        ↓
2. Upload the world
        ↓
3. Extract the world into worlds/level
        ↓
4. Upload Resource Packs
        ↓
5. Extract them into resource_packs/
        ↓
6. Upload Behavior Packs
        ↓
7. Extract them into behavior_packs/
        ↓
8. Check manifest.json
        ↓
9. Check world_resource_packs.json
        ↓
10. Check world_behavior_packs.json
        ↓
11. Start/restart the server
        ↓
12. Join and test

The most important thing to remember is that the manifest.json identifies each pack using its UUID and version, while world_resource_packs.json and world_behavior_packs.json tell the world which Resource Packs and Behavior Packs it should load.

If you're uploading a complete downloadable world, it's best to keep the included pack configuration files intact and upload the matching Resource Packs and Behavior Packs to their respective directories.