MineBrushQuick answer: a Bedrock resource pack changes what players see or hear, while a behavior pack changes game data and rules such as entities, loot, spawn rules, items, recipes, and trades. Many add-ons use both layers, but a resource pack and a behavior pack are not automatically a pair.
Choose the layer from the result you want, then confirm the pack manifest before importing anything. A new mob that looks different and acts differently normally needs resources for the visuals and behavior data for the mechanics. A texture-only refresh may need only a resource pack. A recipe-only project may need only behavior data.
Resource pack or behavior pack?
| Player goal | Likely layer | Manifest module type | First place to troubleshoot |
|---|---|---|---|
| Replace textures, models, sounds, or other presentation assets | Resource pack | resources |
Resource Packs activation screen and the resource-pack content folders |
| Change entity behavior, loot, spawning, items, recipes, or trades | Behavior pack | data |
Behavior Packs activation screen and the behavior-pack content folders |
| Add a feature with both custom visuals and custom rules | Usually both | One resources pack plus one data pack |
Both manifests, their UUIDs and any declared dependency |
| Run creator scripts | A scripted add-on route | script in the relevant manifest |
The creator's exact engine, API, dependency, and experimental-feature requirements |
These are layer definitions, not a promise that every project uses the same folder layout. Microsoft’s pack-content reference says the only universally required file for either basic pack type is manifest.json; the rest depends on what the creator built.
Read the manifest before the filename
A filename such as MyAddon.mcpack does not fully describe the pack. Open the creator’s documentation or inspect the pack structure in a safe workspace and check manifest.json. The header identifies the pack. The modules array identifies what the pack contains, and each module has its own UUID and type.
For this comparison, the decisive module values are:
resourcesfor a resource pack;datafor a behavior pack;scriptwhen a project includes a scripting module.
Do not reuse UUIDs when making your own pack. Pack and module UUIDs are identities, not labels. Also treat the manifest version as release identity: Bedrock uses version information when it decides whether an imported pack is an update. A changed ZIP name alone does not create a clean new pack identity.
How companion packs connect
A behavior pack can declare a dependency on a companion resource pack by UUID and version. The referenced UUID and version must match the companion pack’s header. If the resource pack is missing or the values disagree, Bedrock can report a missing dependency instead of silently guessing which file belongs with which behavior pack.
The relationship is explicit only when the creator declares and maintains it. Two packs with similar names are not proof of a dependency. Likewise, a behavior pack without a resource-pack dependency is not necessarily incomplete; it may change recipes, loot, spawning, or other data while using vanilla presentation.
Keep a small tuple for every installed pair:
- behavior-pack name, UUID, and version;
- resource-pack name, UUID, and version;
- declared dependency direction;
- target Bedrock build and any creator-stated experiments;
- the world in which the pair was activated.
Activate the correct layer in a test world
- Back up the world before changing its active packs.
- Import only the files supplied by the same creator release. Do not combine similarly named packs from different pages.
- Create a disposable world that matches the creator’s stated Bedrock version.
- Enable visual-only content under Resource Packs.
- Enable mechanics or data content under Behavior Packs.
- If the project ships a declared pair, activate both matching versions and resolve every dependency warning before entering the world.
- Test one promised feature, exit normally, reopen the world, and check that the feature and active-pack list persist.
The manifest field min_engine_version is a minimum engine boundary. It is not evidence that a pack works on every later Bedrock release. Format changes, experiments, creator scripts, and removed game behavior can still affect a newer build.
Troubleshoot by symptom
| Symptom | Most useful first check | Common category error |
|---|---|---|
| The pack imports but no textures change | Confirm it has a resources module and is active under Resource Packs for this world or global context |
Editing behavior data to repair a visual layer |
| The model appears but uses missing or incorrect textures | Check the companion resource pack, texture references, and exact pack version | Assuming the behavior pack owns every visual asset |
| The entity looks right but does not use the promised mechanics | Confirm the matching data pack is active under Behavior Packs |
Reinstalling only the resource pack |
| Bedrock reports a missing dependency | Compare the dependency UUID and version with the companion pack header character for character | Renaming the archive and expecting the dependency to update |
| An older release remains after import | Compare manifest UUIDs and versions, then check the active world’s selected pack entry | Treating the displayed filename as the pack identity |
| The world works until one pack is removed | Restore the exact pair in a copy and review creator removal instructions | Using a production world as the first uninstall test |
What this guide cannot decide for a specific add-on
A layer comparison cannot prove that an individual download is current, safe, complete, or compatible with your exact Bedrock build. It also cannot determine whether a Realm copies or enforces a pack correctly, whether a device has enough memory, or whether world data survives removal. Those checks belong to the exact creator release and a backed-up test world.
Do not infer performance from pack type. A small behavior pack can contain expensive logic, while a large resource pack can pressure memory or storage. Meaningful performance claims require the exact pack pair, device, Bedrock build, world, graphics settings, and repeatable measurements.
Official Bedrock creator references
- Microsoft: Introduction to Resource Packs
- Microsoft: Introduction to Behavior Packs
- Microsoft: Add-on pack manifest reference
- Microsoft: Manifest dependency reference
- Microsoft: Comprehensive pack contents
Download boundary: this page explains Bedrock pack layers; it does not distribute an add-on. Get a specific pack only from its creator-controlled release page, then verify that release’s own manifest, version, dependency, rights, and device requirements.
PLAYER QUESTIONS
Discussion
Include the exact edition, version and step when asking for help.