USAGE
Is "behavior_pack_root" the same as "[behavior_pack]" in subparagraph subfolder?
And where shell the Packages reside? There are two Folders called "behavior_packs", one resides in the com.mojang-folder and the other in the cryptic named worldfolder within minecraftWorlds.
Both didn't run for me. Manifests I did clone and changed 1 and 2 uuids to 3 and 4 in second pack.
--Moevenbaer (talk) 10:33, 17 August 2019 (UTC)
Yes, "behavior_pack_root" is the same as "PACKNAME" in your picture examples.
The directory found at "/com.mojang/behavior_packs" is where behavior packs you have imported into Minecraft go. You can manually import a behavior pack by copying it into this file location. Opening a .mcpack file that is a behavior pack will open Minecraft and import the pack into this folder for you. The behavior packs in this file location should now appear in game under the behavior packs section when editing a world's settings.
When you add a behavior pack to a world, the game copies that behavior pack into the world's folder "com.mojang/minecraftWorlds/crypticworldname/behavior_packs". Packs in this directory are the packs applied to that specific world. I would recommend not copying files into here manually.
I would recommend putting your behavior pack in "/com.mojang/behavior_packs" folder and then applying the pack to your world in game.
Once you have your behavior pack in the right location, make sure that it has a subfolder called "functions". In your example, your behavior pack was "PACKNAME" so your directories should look like the following: "com.mojang/behavior_packs/PACKNAME" and then the function folder should be found at "com.mojang/behavior_packs/PACKNAME/functions". Inside this functions folder is where you want to place the .mcfunction files you want to run. It looks like your directories are set up correctly.
If that still doesn't work, make sure you've specified "min_engine_version" in the pack's manifest. The game needs this to be able to run the correct version of commands from the function. Here is an example manifest that should work, although you'll need to fill in the UUID sections yourself:
{
"format_version": 1,
"header": {
"description": "Testing Functions",
"name": "Function Behavior Pack",
"uuid": "UUID GOES HERE,
"version": [1, 8, 0],
"min_engine_version": [1, 8, 0]
},
"modules": [
{
"description": "",
"type": "data",
"uuid": "UUID2 GOES HERE",
"version": [1, 8, 0]
}
]
}
Mpecreatortoolkit (talk) 20:44, 19 August 2019 (UTC)