It needs to be the exact same UUID that the pack has defined in the header section of it's manifest file. This is the unique identifier of the pack that this pack depends on. In order to submit any content to the marketplace, the version a value will need to be set to a value greater than 0. This can be used to further identify changes in your pack. This is the version of the module in the same format as the pack's version in the header. This should be different from the pack's UUID, and different for every module. This is a unique identifier for the module in the same format as the pack's UUID in the header. Can be any of the following: resources, data, client_data, interface, world_template or javascript. This is not user-facing at the moment but is a good place to remind yourself why the module is defined. This is a short description of the module. The new pack will replace the old one if the version is higher, and ignored if it's the same or lower. The version number is used when importing a pack that has been imported before. This is the version of your pack in the format. We recommend using an online service to generate this and guarantee their uniqueness, UUIDs are written in the format xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx where each x is a hexadecimal value (0-9 or a-f). This is a special type of identifier that uniquely identifies this pack from any other pack. This is the name of the pack as it appears within Minecraft. You should always use the highest version currently available when creating packs. This helps the game identify whether any backwards compatibility is needed for your pack. This is a required field for resource and behavior packs. This is the minimum version of the game that this pack was written for. This will lock the player from modifying the options of the world. This option is required for any world templates. It will appear in the game below the name of the pack. We use this to determine what version of the base game resource and behavior packs to apply when your content is used. This is the version of the base game your world template requires, specified as. Section containing the metadata about the file such as authors and licensing information. Section containing optional features that can be enabled in Minecraft. Section containing definitions for any other packs that are required in order for this manifest.json file to work. Section containing information regarding the type of content that is being brought in. Section containing information regarding the name of the pack, description, and other features that are public facing. This may be 1 for skin packs or 2 for resource, behavior, and world packs. The syntax version used in the manifest file. To learn more about how to get started with writing manifest.json files in Minecraft: Bedrock Edition, you can view the Introduction to Resource Packs Tutorial.

Json minecraft jar