Mastering Minecraft Bedrock Manifest.json Architecture & UUID Dependency Routing

The manifest.json file is the root identity certificate for every Minecraft Bedrock add-on pack. A single invalid UUID, mismatched module type, or conflicting version definition causes Bedrock to reject the pack or silently ignore assets.

1. The Core Schema Breakdown

A valid manifest requires two distinct top-level sections: header and modules.

• Header: Defines pack name, description, pack UUID, version tuple [1, 0, 0], and min_engine_version.
• Modules: Defines what content the pack injects. Behavior Packs use "type": "data", Resource Packs use "type": "resources", and Script API packs use "type": "script".

2. UUID v4 Collision and Pairing Rules

Bedrock requires that:

1. The header UUID and module UUID inside the same manifest must never be identical.
2. No two distinct packs in the game may share the same header UUID.
3. When a Behavior Pack depends on a Resource Pack, the BP's dependencies array references the RP's header UUID.

// Example Behavior Pack Dependency:
"dependencies": [
  {
    "uuid": "a7b3c291-89e4-4a22-96b1-094857201938", // RP Header UUID
    "version": [1, 0, 0]
  }
]