Project Setup

Introduction ​

This page will guide you through the steps required to create your first "working" add-on and view it in game. If you're joining on android, you should follow this alternative guide:

The com.mojang Folder ​

The com.mojang folder is a special folder where Minecraft stores data (Add-ons, Worlds, Player info...). Minecraft understands this location, and all files we access or create will be placed somewhere in this folder!

You should create a shortcut to the com.mojang folder on your Desktop or on your mobile device, so you can easily access it at any time. The exact location of the com.mojang folder will depend on your device OS.

Windows ​

On windows, the com.mojang folder is located within your app-data folder.

Tip: You can type %appdata% into the searchbar to jump directly into the C:\Users\<USERNAME>\AppData\ folder.

C:\Users\<USERNAME>\AppData\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang

Android ​

Android 11 or older: Phone > games > com.mojang

Android 12 and newer: Phone > Android > data > com.mojang.minecraftpe > files > games > com.mojang

ChromeOS ​

Before you can see the com.mojang in your files, make sure to change the File Storage Location to External in your Minecraft Settings:

• Go to Minecraft Settings.
• Navigate to Settings > General > Storage.
• Change the File Storage Location to External.

After that you can access the com.mojang folder in your Android Subsystem:

My Files > Play Files > Android > data > com.mojang.minecraftpe > files > games > com.mojang

iOS ​

My iDevice > Minecraft > games > com.mojang

Development Packs ​

We will develop our add-on in development_behavior_packs and development_resource_packs. When you make changes within these folders, you can exit and re-enter a world with the packs applied, to automatically reload the content. This allows you to quickly test your add-on without reloading Minecraft.

resource_packs and behavior_packs on the other hand contain stable add-ons, including those imported via .mcpack. We can ignore these folders for now.

Your Workspace ​

First of all, you will need to create the proper folders in suitable locations and set up your workspace. The remainder of this guide assumes you are using VSCode. You may also follow along with other editors.

Let's create your first add-on workspace in Visual Studio Code now.

1. Open VSCode (Visual Studio Code, the code editor)
2. Create a folder named "your_pack_name_RP" in development_resource_packs. I'll refer to this folder as RP
3. Create a folder "your_pack_name_BP" in development_behavior_packs. I'll refer to this folder as BP.
4. Go to File > Add folder to workspace... and choose BP. Do the same with RP.
5. Press File > Save Workspace as... to save the workspace file to your Desktop. Whenever you're working on your add-on, all you have to do is open the workspace by double-clicking, and you will get quick access to both BP and RP folders.

BP Manifest ​

The manifest is a file that identifies your pack to Minecraft. Every pack has one manifest. A folder with a correctly formatted manifest will show up in Minecraft, and we consider this the "minimal" pack before we can add additional content.

Manifest files are written in json. If this isn't familiar to you, you can learn more about json here.

First, create a new file in your BP folder by right-clicking on the folder and selecting New File. Call the file manifest.json. To begin, you can copy paste the following code into the file.

{
    "format_version": 2,
    "header": {
        "name": "pack.name",
        "description": "pack.description",
        "uuid": "...",
        "version": [1, 0, 0],
        "min_engine_version": [1, 16, 0]
    },
    "modules": [
        {
            "type": "data",
            "uuid": "...",
            "version": [1, 0, 0]
        }
    ]
}

Manifest Explained ​

• "format_version" defines what version of manifest syntax you are using. Version 2 is the most recent stable version; use it.

• "name" is the name of your behavior pack. "description" will show up under it in-game. We are defining these files in "code form" so we can translate them later into other languages. For more information about localization, look here.

• The "UUID" field is essential, and will be discussed in more detail below.

• "version" defines the version of your add-on. When you import an add-on with a newer version on a device with an older version installed, the more recent version will overwrite the older one. You don't need to change the version if you have the add-on in development_*_packs folders and only use them on private worlds.

• "min_engine_version" defines the minimum Minecraft client version that'll be able to read your add-on. The number specified here should match the version number of the game, unless you're planning for backwards compatibility with older versions.

• In "modules", the "type" is defined to be "data". This makes your pack a Behavior Pack.

UUID Explained ​

A UUID (Universally Unique Identifier) identifies your pack for other programs (in this case, Minecraft) to read. It looks something like this: 5c830391-0937-44d6-9774-406de66b6984

NEVER USE THE SAME UUID TWICE. You can generate your own UUIDs here or, if you use VSCode, you can install this extension. Many other tools like bridge. generate UUIDS automatically. Every manifest file uses two different UUIDs.

To ensure that your add-on will work correctly you should generate two new UUID's which you will paste into the BP manifest.json file, at each "...". When you are finished, it should look something like this:

"uuid": "5c830391-0937-44d6-9774-406de66b6984"

RP Manifest ​

The next step is to create the manifest.json for the RP. The format for a resource-pack manifest is nearly identical to a BP manifests except that the type is resources, which marks the pack as a Resource Pack.

Copy the following code into your newly created RP/manifest.json and insert your own UUIDs.

{
    "format_version": 2,
    "header": {
        "name": "pack.name",
        "description": "pack.description",
        "uuid": "...",
        "version": [1, 0, 0],
        "min_engine_version": [1, 16, 0]
    },
    "modules": [
        {
            "type": "resources",
            "uuid": "...",
            "version": [1, 0, 0]
        }
    ]
}

Pack Icon ​

The pack icon is an image file which identifies how your add-on will look in-game. If you have a low-resolution square image, you can use it. Otherwise, download and use this example icon:

You should place a copy of your desired image into both the RP and the BP. The image needs to be named pack_icon.png

Language Files ​

The last thing to do is setup language support for your add-on. You will need to create a language file for both the RP and the BP. You can learn more about how Minecraft handles localization here.

pack.name=Wiki Resource Pack
pack.description=A Ghostly Guide

pack.name=Wiki Behavior Pack
pack.description=A Ghostly Guide

["en_US"]

["en_US"]

Checking Your Work ​

If you have done everything correctly, your packs should show up in Minecraft now! If you don't see your pack, you should follow the troubleshooting guide.

Turn on Content Log ​

Content Log is an extremely important debugging tool, which you should always have on.

Turn on both content log settings in settings > creator. This will show you any errors in your add-on when you enter a world with it applied. You can open the content log GUI in-game by pressing ctrl+h or by pressing Content Log History in the creator settings panel. Learn more about the content log here.

Creating Your Testing World ​

Now we create a world to test your new add-on!

1. Click "Create new world";

2. Ensure that the following settings are set.

   

3. Now activate your behavior pack, and your resource pack. You can do this by selecting the packs, and clicking 'apply'.

4. Now click 'Create'!

Overview ​

Here is how your project should look, after completing this page:

Remember that in future, we will represent com.mojang/development_behavior_packs/guide_RP/ as RP, and com.mojang/development_behavior_packs/guide_BP/ as BP.

What You Have Learned ​

Your Progress So Far ​