Bedrock manifest.json Generator (Format Version 2)
Generate valid, production-ready manifest.json definitions for Minecraft Bedrock Behavior Packs, Resource Packs, Script API modules (@minecraft/server), and Skin Packs with automatic UUID pair generation.
Bedrock Manifest Schema Architecture & Specification
header Identity Object
Defines the pack identity: name (display string), description, uuid (global identifier), version (e.g. [1, 0, 0]), and min_engine_version. The engine version instructs Bedrock whether modern component schemas (like block format version 1.21+) are supported.
modules Payload Array
Declares the content types packaged inside: data for server-side game rules/entities/blocks, resources for client-side textures/models/sounds, script for JavaScript/TypeScript modules, or skin_pack for custom skins.
dependencies Cross-Pack Binding
Enforces strict package links. Linking a companion Resource Pack requires specifying its header.uuid. Integrating the Bedrock Script API requires declaring module dependencies such as @minecraft/server version 2.8.0.
5 Critical Bedrock Manifest.json Pitfalls
1. Suffix Discrepancies in Pack Names ("BP" vs "RP")
Never add "BP" or "RP" suffixes to your pack name inside header.name. Both Behavior and Resource packs should share the EXACT SAME name (e.g. "Kingdoms of Legend"). Minecraft automatically separates them by type in the UI, and differing names breaks unified pack grouping in world settings.
2. Format Version Downgrading (format_version: 1)
Legacy templates from 2018 used format_version: 1. Modern Bedrock features—including subpack selection, custom block components, and Script API modules—strictly require format_version: 2. Downgrading format versions silently disables modern engine hooks.
3. Script API (@minecraft/server) Version Drift
When importing @minecraft/server in scripts, the version specified in dependencies must match the runtime version supported by your min_engine_version. Mismatched major/minor versions cause world loading to abort with failed to create context.
4. Duplicate UUID Collisions Across BP and RP
If you generate a manifest for your Behavior Pack and copy the same file into your Resource Pack, both packs share the same UUID. Minecraft Bedrock will reject the world save with "Duplicate pack detected" and refuse to load custom textures.
5. Omitting Capabilities for Scripting
If your add-on uses Script API eval operations or special experimental APIs, you must include "capabilities": ["script_eval"] in the header. Omitting required capabilities triggers security sandbox exceptions in the Bedrock JavaScript V8/Hermes runtime.