Minecraft:Manifest.json: Difference between revisions

Revision as of 15:55, 9 April 2026

Template:Exclusive manifest.json is a Template:W that contains metadata information for the Minecraft package format. It is required by resource packs, Minecraft:behavior packs, Minecraft:skin packs, and world templates in order to be successfully imported into the game.

JSON format

Version 3

Template:Nbt: The root tag.
- Template:Nbt: The syntax version used in the manifest file. In this section, it is version Template:Cd.
- Template:Nbt: External information about the pack.
  - Template:Nbt: Specific to world templates. Whether a random seed should be generated on world creation.
  - Template:Nbt: Specific to world templates. A vector Template:Cd representing the version of the vanilla resource and behavior packs to apply.
  - Template:Nbt: A description of the pack. Can be text or a translation key.
  - Template:Nbt: Locks the pack from being used as a global pack, rendering it impossible to use on other player's worlds or servers.
  - Template:Nbt: Specific to world templates. If enabled, the player can not modify the world options.
  - Template:Nbt: A vector Template:Cd representing the minimum version of the game the pack can run on.
  - Template:Nbt: The name of the pack. Can be text or a translation key.
  - Template:Nbt: Specific to resource packs. Represents at which level the pack can be applied. Template:Cd packs can be applied to a world, Template:Cd in global resources and Template:Cd anywhere. Defaults to Template:Cd.
  - Template:Nbt: A unique identifier for the pack. Must be of the form Template:Cd, where x in a hexadecimal number (0-9 or a-f).
  - Template:Nbt: A string of the form Template:Cd or vector Template:Cd representing the current version of pack. Used to handle updates to the pack.
    - Template:Nbt: Name in front of preRelease.
    - Template:Nbt: First version number, for Minecraft:Marketplace packages this value always needs to be greater than 0.
    - Template:Nbt: Second version number.
    - Template:Nbt: Third version number.
    - Template:Nbt: Name in front of version.
- Template:Nbt: Describes modules which are content types that the pack may contain.
  - Template:Nbt: A module object in the list.
    - Template:Nbt: An internal description of the module.
    - Template:Nbt: The type of the module, can be: Template:Cd (resource pack), Template:Cd
    - ),Template:Cd (Minecraft:Character Creator item or cape), Template:Cd, Template:Cd, or Template:Cd (scripting).
    - Template:Nbt: An identifier unique to the module. Must be of the form Template:Cd, where x in a hexadecimal number (0-9 or a-f).
    - Template:Nbt: A string of the form Template:Cd or vector Template:Cd representing the current version of pack. Used to handle updates to the pack.
      - Template:Nbt: Name in front of preRelease.
      - Template:Nbt: First version number.
      - Template:Nbt: Second version number.
      - Template:Nbt: Third version number.
      - Template:Nbt: Name in front of version.
    - Template:Nbt: Specific to script modules. The language the scripts are written in. Only supports Template:Cd.
    - Template:Nbt: Specific to script modules. Relative path to the main script file.
- Template:Nbt: Describes external dependencies that the pack requires. The dependency may be another pack, or a script module.
  - Template:Nbt: Describes a pack dependency.
    - Template:Nbt: Template:Cd of the pack dependency.
    - Template:Nbt: The name of the pack. Can be text or a translation key.
    - Template:Nbt Template:Nbt: Template:Cd of the dependency to use.
  - Template:Nbt: Describes a script module dependency.
    - Template:Nbt: Template:Cd of the script module. Optional
    - Template:Nbt: Name of the script module, used for importing the Script API.
    - Template:Nbt Template:Nbt: Template:Cd of the dependency to use.
- Template:Nbt: Optional features that can be enabled.
  - Template:Nbt: A capability to enable, can be:
    - Template:Cd – specific to Minecraft:Minecraft Education chemistry features.
    - Template:Cd – used internally in the game in the vanilla Minecraft:Bedrock Editor resource pack, and for importing @minecraft/server-editor script module.<ref>https://wiki.bedrock.dev/scripting/api-modules</ref>
    - Template:Cd – experimental custom UI based on HTML and JavaScript. Unsupported since 1.18.10.28.<ref>https://bedrock.dev/docs/1.18.0.0/1.18.10.28/UI</ref>
    - Template:Cd – enables dynamic code execution in scripting via eval() function or Function() constructor.<ref>https://wiki.bedrock.dev/scripting/api-environment</ref>
    - Template:Cd – enables PBR features specific to ray tracing, which only supports MER subset. Compatible with Vibrant Visuals.
    - Template:Cd – enables PBR features specific to Minecraft:Vibrant Visuals with full MERS support.
- Template:Nbt: Metadata on the pack, currently mandatory in this version.
  - Template:Nbt: List of creators of the pack, currently mandatory in this version.
    - Template:Nbt: The name of a creator of the pack.
  - Template:Nbt: License the pack is distributed under.
  - Template:Nbt: Tools used to generate the manifest.
    - Template:Nbt: The name of the list element should be the name of a tool used to generate the manifest. It must be made of simple characters and can be up to 32 characters long.
      - Template:Nbt: A string of the form Template:Cd representing a version of the tool used to modify the manifest.
  - Template:Nbt: If set to Template:Cd, indicates the pack is meant as part of an Minecraft:add-on. This allows the add-on to not disable achievements when activated.
  - Template:Nbt: URL to a website.
- Template:Nbt: List of sub-packs used in the pack, which can be enabled and disabled individually.
  - Template:Nbt: A sub-pack in the list
    - Template:Nbt: Name of the folder where the sub-pack is located.
    - Template:Nbt: In-game display name of the sub-pack
    - Template:Nbt: Designates the minimum amount of RAM required to run the sub-pack (each tier represents 250 MB)
    - Template:Nbt: Denotes the optimal platform for a subpack (values range 1–5).
- Template:Nbt: Order-dependent list of settings the player can modify in the game's UI.
  - Template:Nbt: A read-only label, used for describing or breaking up the sections of the settings area.
    - Template:Nbt: Template:Cd
    - Template:Nbt: Text value of the label.
  - Template:Nbt: A binary toggle.
    - Template:Nbt: Template:Cd
    - Template:Nbt: Textual, user-visible label for the toggle.
    - Template:Nbt: Programmatic identifier for the value of this toggle.
    - Template:Nbt: Default value of this setting.
  - Template:Nbt: A sliding that allows for setting of a number within a range.
    - Template:Nbt: Template:Cd
    - Template:Nbt: Textual, user-visible label for the slider.
    - Template:Nbt: Programmatic identifier for the value of this slider.
    - Template:Nbt: Minimum value for the slider.
    - Template:Nbt: Maximum value for the slider.
    - Template:Nbt: Incremental "notches" for the slider.
    - Template:Nbt: Default value of the slider.

Version 2

Template:Nbt: The root tag.
- Template:Nbt: The syntax version used in the manifest file. In this section, it is version Template:Cd.
- Template:Nbt: External information about the pack.
  - Template:Nbt: Specific to world templates. Whether a random seed should be generated on world creation.
  - Template:Nbt: Specific to world templates. A vector Template:Cd representing the version of the vanilla resource and behavior packs to apply.
  - Template:Nbt: A description of the pack. Can be text or a translation key.
  - Template:Nbt: Locks the pack from being used as a global pack, rendering it impossible to use on other player's worlds or servers.
  - Template:Nbt: Specific to world templates. If enabled, the player can not modify the world options.
  - Template:Nbt: A vector Template:Cd representing the minimum version of the game the pack can run on.
  - Template:Nbt: The name of the pack. Can be text or a translation key.
  - Template:Nbt: Specific to resource packs. Represents at which level the pack can be applied. Template:Cd packs can be applied to a world, Template:Cd in global resources and Template:Cd anywhere. Defaults to Template:Cd.
  - Template:Nbt: A unique identifier for the pack. Must be of the form Template:Cd, where x in a hexadecimal number (0-9 or a-f).
  - Template:Nbt Template:Nbt: A string of the form Template:Cd or vector Template:Cd representing the current version of pack. Used to handle updates to the pack.
- Template:Nbt: Describes modules which are content types that the pack may contain.
  - Template:Nbt: A module object in the list.
    - Template:Nbt: An internal description of the module.
    - Template:Nbt: The type of the module, can be: Template:Cd (resource pack), Template:Cd (Minecraft:behavior pack), Template:Cd (Minecraft:Character Creator item or cape), Template:Cd, Template:Cd, or Template:Cd (scripting).
    - Template:Nbt: An identifier unique to the module. Must be of the form Template:Cd, where x in a hexadecimal number (0-9 or a-f).
    - Template:Nbt Template:Nbt: A string of the form Template:Cd or vector Template:Cd representing the current version of pack. Used to handle updates to the pack.
    - Template:Nbt: Specific to script modules. The language the scripts are written in. Only supports Template:Cd.
    - Template:Nbt: Specific to script modules. Relative path to the main script file.
- Template:Nbt: Describes external dependencies that the pack requires. The dependency may be another pack, or a script module.
  - Template:Nbt: Describes a pack dependency.
    - Template:Nbt: Template:Cd of the pack dependency.
    - Template:Nbt: The name of the pack. Can be text or a translation key.
    - Template:Nbt Template:Nbt: Template:Cd of the dependency to use.
  - Template:Nbt: Describes a script module dependency.
    - Template:Nbt: Template:Cd of the script module. Optional
    - Template:Nbt: Name of the script module, used for importing the Script API.
    - Template:Nbt Template:Nbt: Template:Cd of the dependency to use.
- Template:Nbt: Optional features that can be enabled.
  - Template:Nbt: A capability to enable, can be:
    - Template:Cd – specific to Minecraft:Minecraft Education chemistry features.
    - Template:Cd – used internally in the game in the vanilla Minecraft:Bedrock Editor resource pack, and for importing @minecraft/server-editor script module.<ref>https://wiki.bedrock.dev/scripting/api-modules</ref>
    - Template:Cd – experimental custom UI based on HTML and JavaScript. Unsupported since 1.18.10.28.<ref>https://bedrock.dev/docs/1.18.0.0/1.18.10.28/UI</ref>
    - Template:Cd – enables dynamic code execution in scripting via eval() function or Function() constructor.<ref>https://wiki.bedrock.dev/scripting/api-environment</ref>
    - Template:Cd – enables PBR features specific to ray tracing, which only supports MER subset. Compatible with Vibrant Visuals.
    - Template:Cd – enables PBR features specific to Minecraft:Vibrant Visuals with full MERS support.
- Template:Nbt: Metadata on the pack.
  - Template:Nbt: List of creators of the pack.
    - Template:Nbt: The name of a creator of the pack.
  - Template:Nbt: License the pack is distributed under.
  - Template:Nbt: Tools used to generate the manifest.
    - Template:Nbt: The name of the list element should be the name of a tool used to generate the manifest. It must be made of simple characters and can be up to 32 characters long.
      - Template:Nbt: A string of the form Template:Cd representing a version of the tool used to modify the manifest.
  - Template:Nbt: If set to Template:Cd, indicates the pack is meant as part of an Minecraft:add-on, this also allows the addon to not disable achievements when activated.
  - Template:Nbt: URL to a website.

Old versions

Version 1

The previous iteration of manifest.json only ever contains few basic information about the package, such as header, modules, and dependencies, being very similar to version 2 without the modern features.

These manifest files are documented from multiple built-in resource packs, which are found in the game's directory:

Template:Nbt: The root tag.
- Template:Nbt: The syntax version used in the manifest file, version 1.
- Template:Nbt: The pack's display information.
  - Template:Nbt: A description of the pack. Can be text or a translation key.
  - Template:Nbt: The name of the pack. Can be text or a translation key.
  - Template:Nbt: A unique identifier for the pack. Must be of the form Template:Cd, where x in a hexadecimal number (0-9 or a-f).
  - Template:Nbt: An array consist of three integer numbers representing the current version of pack.
  - Template:Nbt: An array consist of three integer numbers representing the minimum version of the game the pack can run on.
- Template:Nbt: Describes modules which are content types that the pack may contain.
  - Template:Nbt: A module object in the list.
    - Template:Nbt: An internal description of the module.
    - Template:Nbt: The type of the module, can be: Template:Cd (resource pack), Template:Cd (Minecraft:behavior pack), and Template:Cd.
    - Template:Nbt: An identifier unique to the module. Must be of the form Template:Cd, where x in a hexadecimal number (0-9 or a-f).
    - Template:Nbt: An array consist of three integer numbers representing the version of the pack.
- Template:Nbt: Describes external dependencies that the pack requires.
  - Template:Nbt: Describes a pack dependency.
    - Template:Nbt: Template:Cd of the pack dependency.
    - Template:Nbt: The name of the pack. Can be text or a translation key.
    - Template:Nbt: An array consist of three integer numbers representing the version of the pack.

Version 0

The very first version of manifest.json, at the time was named pack_manifest.json, is used back in the v0.16.0 alpha versions. Its syntax is very different from version 1, containing the header object with different properties that would be renamed in the next iteration. Notably, modules and dependencies are contained inside the header object.

It is retroactively called version 0 in the Creator Documentation. Additionally, when the pack containing this manifest is loaded in later versions, it would get converted to version 1 with the new manifest.json, while the old pack_manifest.json would get backed up as pack_manifest.json.old.<ref>https://learn.microsoft.com/en-us/minecraft/creator/reference/content/versiondisambiguation?view=minecraft-bedrock-stable</ref>

Version 0 resource packs are separated into the client and server packs, both serve very similar purposes to the modern resource pack (client) and behavior pack (server).

These manifest files are documented from multiple built-in resource packs, which are found in the game's directory:

Template:Nbt: The root tag.
- Template:Nbt: The pack's display information.
  - Template:Nbt: A unique identifier for the pack. Must be of the form Template:Cd, where x in a hexadecimal number (0-9 or a-f).
  - Template:Nbt: The name of the pack. Can be text or a translation key.
  - Template:Nbt: An array consist of three integer numbers representing the current version of pack.
  - Template:Nbt: A description of the pack. Can be text or a translation key.
  - Template:Nbt: Describes modules which are content types that the pack may contain.
    - Template:Nbt: A module object in the list.
      - Template:Nbt: An internal description of the module.
      - Template:Nbt: The type of the module, can be: Template:Cd (client) and Template:Cd (server).
      - Template:Nbt: An identifier unique to the module. Must be of the form Template:Cd, where x in a hexadecimal number (0-9 or a-f).
      - Template:Nbt: A string formatted like X.Y.Z representing the version of the pack.
  - Template:Nbt: Describes external dependencies that the pack requires.
    - Template:Nbt: Describes a pack dependency.
      - Template:Nbt: Template:Cd of the pack dependency.
      - Template:Nbt: The name of the pack. Can be text or a translation key.
      - Template:Nbt: A string formatted like X.Y.Z representing the version of the pack.

History

Template:Empty section

External links

Template:Cite
Manifest file examples in the bedrock-samples provided by Mojang:
- Template:Cite
- Template:Cite

References

Navigation

Template:Navbox Bedrock Edition

pt:Manifest.json uk:Manifest.json zh:Manifest.json

@@ Line 1: / Line 1: @@
 {{DISPLAYTITLE:<samp>manifest.json</samp>}}
 {{exclusive|bedrock}}
-<code>'''manifest.json'''</code> is a {{w|manifest file}} that contains metadata information for the ''Minecraft'' package format. It is required by [[Minecraft:resource pack]]s, [[Minecraft:behavior pack]]s, [[Minecraft:skin pack]]s, and [[Minecraft:world template]]s in order to be successfully imported into the game.
+<code>'''manifest.json'''</code> is a {{w|manifest file}} that contains metadata information for the ''Minecraft'' package format. It is required by resource packs, [[Minecraft:behavior pack]]s, [[Minecraft:skin pack]]s, and world templates in order to be successfully imported into the game.
 == JSON format ==
@@ Line 28: / Line 28: @@
 **** {{nbt|string|description}}: An internal description of the module.
 **** {{nbt|string|type}}: The type of the module, can be: {{cd|"resource"}} (resource pack), {{cd|"data"}}
-**** ),{{cd|"persona_piece"}} ([[Minecraft:Character Creator]] item or [[Minecraft:cape]]), {{cd|"[[Minecraft:Skin pack|skin_pack]]"}}, {{cd|"[[Minecraft:World template|world_template]]"}}, or {{cd|"script"}} ([[Minecraft:scripting]]).
+**** ),{{cd|"persona_piece"}} ([[Minecraft:Character Creator]] item or cape), {{cd|"[[Minecraft:Skin pack|skin_pack]]"}}, {{cd|"world_template"}}, or {{cd|"script"}} (scripting).
 **** {{nbt|string|uuid}}: An identifier unique to the module. Must be of the form {{cd|"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"}}, where x in a hexadecimal number (0-9 or a-f).
 **** {{nbt|string|version}}: A string of the form {{cd|"A.B.C"}} or vector {{cd|[A,B,C]}} representing the current version of pack. Used to handle updates to the pack.
@@ Line 45: / Line 45: @@
 *** {{nbt|compound}}: Describes a script module dependency.
 **** {{nbt|string|uuid}}: {{cd|uuid}} of the script module. ''Optional''
-**** {{nbt|string|module_name}}: Name of the script module, used for importing the [[Minecraft:Script API]].
+**** {{nbt|string|module_name}}: Name of the script module, used for importing the Script API.
 **** {{nbt|int-array}}{{nbt|string|version}}: {{cd|version}} of the dependency to use.
 ** {{nbt|list|capabilities}}: Optional features that can be enabled.
 *** {{nbt|string}}: A capability to enable, can be:
-**** {{cd|"chemistry"}} &ndash; specific to ''[[Minecraft:Minecraft Education]]'' [[Minecraft:chemistry]] features.
+**** {{cd|"chemistry"}} &ndash; specific to ''[[Minecraft:Minecraft Education]]'' chemistry features.
 **** {{cd|"editorExtension"}} &ndash; used internally in the game in the vanilla [[Minecraft:Bedrock Editor]] resource pack, and for importing <code>@minecraft/server-editor</code> script module.<ref>https://wiki.bedrock.dev/scripting/api-modules</ref>
-**** {{cd|"experimental_custom_ui"}} &ndash; experimental custom UI based on HTML and JavaScript. Unsupported since [[Minecraft:1.18.10.28]].<ref>https://bedrock.dev/docs/1.18.0.0/1.18.10.28/UI</ref>
+**** {{cd|"experimental_custom_ui"}} &ndash; experimental custom UI based on HTML and JavaScript. Unsupported since 1.18.10.28.<ref>https://bedrock.dev/docs/1.18.0.0/1.18.10.28/UI</ref>
-**** {{cd|"script_eval"}} &ndash; enables dynamic code execution in [[Minecraft:scripting]] via <code>eval()</code> function or <code>Function()</code> constructor.<ref>https://wiki.bedrock.dev/scripting/api-environment</ref>
+**** {{cd|"script_eval"}} &ndash; enables dynamic code execution in scripting via <code>eval()</code> function or <code>Function()</code> constructor.<ref>https://wiki.bedrock.dev/scripting/api-environment</ref>
-**** {{cd|"raytraced"}} &ndash; enables PBR features specific to [[Minecraft:ray tracing]], which only supports MER subset. Compatible with Vibrant Visuals.
+**** {{cd|"raytraced"}} &ndash; enables PBR features specific to ray tracing, which only supports MER subset. Compatible with Vibrant Visuals.
 **** {{cd|"pbr"}} &ndash; enables PBR features specific to [[Minecraft:Vibrant Visuals]] with full MERS support.
 ** {{nbt|compound|metadata}}: Metadata on the pack, currently mandatory in this version.
@@ Line 107: / Line 107: @@
 *** {{nbt|compound}}: A module object in the list.
 **** {{nbt|string|description}}: An internal description of the module.
-**** {{nbt|string|type}}: The type of the module, can be: {{cd|"resource"}} ([[Minecraft:resource pack]]), {{cd|"data"}} ([[Minecraft:behavior pack]]), {{cd|"persona_piece"}} ([[Minecraft:Character Creator]] item or [[Minecraft:cape]]), {{cd|"[[Minecraft:Skin pack|skin_pack]]"}}, {{cd|"[[Minecraft:World template|world_template]]"}}, or {{cd|"script"}} ([[Minecraft:scripting]]).
+**** {{nbt|string|type}}: The type of the module, can be: {{cd|"resource"}} (resource pack), {{cd|"data"}} ([[Minecraft:behavior pack]]), {{cd|"persona_piece"}} ([[Minecraft:Character Creator]] item or cape), {{cd|"[[Minecraft:Skin pack|skin_pack]]"}}, {{cd|"world_template"}}, or {{cd|"script"}} (scripting).
 **** {{nbt|string|uuid}}: An identifier unique to the module. Must be of the form {{cd|"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"}}, where x in a hexadecimal number (0-9 or a-f).
 **** {{nbt|int-array}}{{nbt|string|version}}: A string of the form {{cd|"A.B.C"}} or vector {{cd|[A,B,C]}} representing the current version of pack. Used to handle updates to the pack.
@@ Line 119: / Line 119: @@
 *** {{nbt|compound}}: Describes a script module dependency.
 **** {{nbt|string|uuid}}: {{cd|uuid}} of the script module. ''Optional''
-**** {{nbt|string|module_name}}: Name of the script module, used for importing the [[Minecraft:Script API]].
+**** {{nbt|string|module_name}}: Name of the script module, used for importing the Script API.
 **** {{nbt|int-array}}{{nbt|string|version}}: {{cd|version}} of the dependency to use.
 ** {{nbt|list|capabilities}}: Optional features that can be enabled.
 *** {{nbt|string}}: A capability to enable, can be:
-**** {{cd|"chemistry"}} &ndash; specific to ''[[Minecraft:Minecraft Education]]'' [[Minecraft:chemistry]] features.
+**** {{cd|"chemistry"}} &ndash; specific to ''[[Minecraft:Minecraft Education]]'' chemistry features.
 **** {{cd|"editorExtension"}} &ndash; used internally in the game in the vanilla [[Minecraft:Bedrock Editor]] resource pack, and for importing <code>@minecraft/server-editor</code> script module.<ref>https://wiki.bedrock.dev/scripting/api-modules</ref>
-**** {{cd|"experimental_custom_ui"}} &ndash; experimental custom UI based on HTML and JavaScript. Unsupported since [[Minecraft:1.18.10.28]].<ref>https://bedrock.dev/docs/1.18.0.0/1.18.10.28/UI</ref>
+**** {{cd|"experimental_custom_ui"}} &ndash; experimental custom UI based on HTML and JavaScript. Unsupported since 1.18.10.28.<ref>https://bedrock.dev/docs/1.18.0.0/1.18.10.28/UI</ref>
-**** {{cd|"script_eval"}} &ndash; enables dynamic code execution in [[Minecraft:scripting]] via <code>eval()</code> function or <code>Function()</code> constructor.<ref>https://wiki.bedrock.dev/scripting/api-environment</ref>
+**** {{cd|"script_eval"}} &ndash; enables dynamic code execution in scripting via <code>eval()</code> function or <code>Function()</code> constructor.<ref>https://wiki.bedrock.dev/scripting/api-environment</ref>
-**** {{cd|"raytraced"}} &ndash; enables PBR features specific to [[Minecraft:ray tracing]], which only supports MER subset. Compatible with Vibrant Visuals.
+**** {{cd|"raytraced"}} &ndash; enables PBR features specific to ray tracing, which only supports MER subset. Compatible with Vibrant Visuals.
 **** {{cd|"pbr"}} &ndash; enables PBR features specific to [[Minecraft:Vibrant Visuals]] with full MERS support.
 ** {{nbt|compound|metadata}}: Metadata on the pack.
@@ Line 145: / Line 145: @@
 The previous iteration of <code>manifest.json</code> only ever contains few basic information about the package, such as <code>header</code>, <code>modules</code>, and <code>dependencies</code>, being very similar to version 2 without the modern features.
-These manifest files are documented from multiple built-in resource packs, which are found in the [[Minecraft:Microsoft.MinecraftUWP|game's directory]]:
+These manifest files are documented from multiple built-in resource packs, which are found in the game's directory:
 <div class="treeview">
 * {{nbt|compound}}: The root tag.
@@ Line 158: / Line 158: @@
 *** {{nbt|compound}}: A module object in the list.
 **** {{nbt|string|description}}: An internal description of the module.
-**** {{nbt|string|type}}: The type of the module, can be: {{cd|"resource"}} ([[Minecraft:resource pack]]), {{cd|"data"}} ([[Minecraft:behavior pack]]), and {{cd|"skin_pack"}}.
+**** {{nbt|string|type}}: The type of the module, can be: {{cd|"resource"}} (resource pack), {{cd|"data"}} ([[Minecraft:behavior pack]]), and {{cd|"skin_pack"}}.
 **** {{nbt|string|uuid}}: An identifier unique to the module. Must be of the form {{cd|"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"}}, where x in a hexadecimal number (0-9 or a-f).
 **** {{nbt|int-array|version}}: An array consist of three integer numbers representing the version of the pack.
@@ Line 169: / Line 169: @@
 === Version 0 ===
-The very first version of <code>manifest.json</code>, at the time was named <code>pack_manifest.json</code>, is used back in the [[Minecraft:v0.16.0 alpha]] versions. Its syntax is very different from version 1, containing the <code>header</code> object with different properties that would be renamed in the next iteration. Notably, <code>modules</code> and <code>dependencies</code> are contained inside the <code>header</code> object.
+The very first version of <code>manifest.json</code>, at the time was named <code>pack_manifest.json</code>, is used back in the v0.16.0 alpha versions. Its syntax is very different from version 1, containing the <code>header</code> object with different properties that would be renamed in the next iteration. Notably, <code>modules</code> and <code>dependencies</code> are contained inside the <code>header</code> object.
 It is retroactively called version 0 in the [https://learn.microsoft.com/en-us/minecraft/creator/reference/content/versiondisambiguation?view=minecraft-bedrock-stable Creator Documentation]. Additionally, when the pack containing this manifest is loaded in later versions, it would get converted to version 1 with the new <code>manifest.json</code>, while the old <code>pack_manifest.json</code> would get backed up as <code>pack_manifest.json.old</code>.<ref>https://learn.microsoft.com/en-us/minecraft/creator/reference/content/versiondisambiguation?view=minecraft-bedrock-stable</ref>
@@ Line 175: / Line 175: @@
 Version 0 resource packs are separated into the ''client'' and ''server'' packs, both serve very similar purposes to the modern resource pack (client) and behavior pack (server).
-These manifest files are documented from multiple built-in resource packs, which are found in the [[Minecraft:Microsoft.MinecraftUWP|game's directory]]:
+These manifest files are documented from multiple built-in resource packs, which are found in the game's directory:
 <div class="treeview">
 * {{nbt|compound}}: The root tag.
@@ Line 213: / Line 213: @@
 [[Category:Development]]
-[[Minecraft:pt:Manifest.json]]
+pt:Manifest.json
-[[Minecraft:uk:Manifest.json]]
+uk:Manifest.json
-[[Minecraft:zh:Manifest.json]]
+zh:Manifest.json