Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWhen a Minecraft Bedrock server add-on does nothing, the files are usually present but not activated, identified with the wrong UUID or version, still compressed, placed in the wrong world, or blocked by a dependency, conflict, client download, or game-version change. Bedrock calls these extensions add-ons: behavior packs change gameplay, resource packs change textures, sounds, and other assets, and some projects use both.
Playing with friends? Godlike.Host runs hosted Minecraft Bedrock servers from 10 data-center locations, with free DDoS protection.
Work through the checks below in order. Back up the world before changing packs, stop the server before editing files, restart after each meaningful change, and read the log after every restart. That method finds most failures without guessing.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Minecraft | Java & Bedrock Deluxe Collection | Windows Digital Code | $39.99 | Buy on Amazon |
| 2 |
|
Minecraft - Bedrock Edition PS4 | $42.98 | Buy on Amazon |
| 3 |
|
Minecraft - Nintendo Switch | $29.83 | Buy on Amazon |
| 4 |
|
Minecraft | $6.99 | Buy on Amazon |
| 5 |
|
Minecraft: Switch Edition | $32.65 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Start with the symptom
The symptom tells you which layer to inspect first. Use this table before changing several files at once.
| What you see | Most likely layer | First check | Scope |
|---|---|---|---|
| The pack appears in the file manager but has no effect | Activation, path, or identity | Confirm the extracted folder and the world pack JSON entry | Usually one pack or one world |
| The behavior pack loads but textures or sounds are vanilla | Missing resource pack or dependency | Compare the behavior pack dependency UUID with the resource pack header UUID | That add-on pair |
| Players see no custom textures | Client-side download or resource-pack loading | Check the resource-pack entry and whether clients accepted the download | Each connecting client |
| The server refuses to start after an upload | Invalid JSON or incompatible pack | Read the startup log, then remove pack entries to isolate the offender | Whole server |
| The server starts, but blocks or entities break after an update | Game-version compatibility | Back up, identify the update, and retest each pack separately | Packs affected by the update |
| Two add-ons work alone but not together | File conflict or load order | Disable one, then test the other; inspect overlapping files | The conflicting pair |
What counts as a Bedrock server mod
Bedrock does not use the Java Edition mod-loader model. Its official term is add-on. A behavior pack contains gameplay definitions such as entities, recipes, components, or rules. A resource pack contains client assets such as textures, models, sounds, and language files. A complete add-on may require both.
#1 Best Overall
- DELUXE COLLECTION — Includes Minecraft: Java & Bedrock Edition, three Bedrock add-ons, three exclusive Character Creator items, and 700 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
Putting a folder in behavior_packs or resource_packs only makes it available to the server. It does not enable the pack in a particular world. Loading has two separate stages:
- The server must be able to find an extracted pack folder with a readable
manifest.json. - The world must list that pack in its behavior-pack or resource-pack JSON file, with matching identity and version data.
Microsoft’s Bedrock documentation describes shared top-level pack folders that can be used by any world and per-world pack folders that apply only to one world. Choose the scope deliberately: a shared folder is convenient for several worlds, while a per-world copy prevents an experimental pack from changing another world.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsFix the folder and archive first
Extract .mcpack and .mcaddon files
Bedrock Dedicated Server reads pack directories, not the downloaded archive itself. If your host’s file manager will not open an .mcpack or .mcaddon, make a copy, rename that copy to .zip, extract it locally, and upload the resulting folder. Do not leave the archive as the only item in behavior_packs or resource_packs.
Open the uploaded directory and check that manifest.json is directly inside it. A common extraction mistake creates an extra level such as PackName/PackName/manifest.json. In that case, the server sees the outer folder but cannot find the manifest at the expected level; move the inner pack folder up one level.
Use the directory that matches the pack type
- Gameplay content belongs in
behavior_packs. - Textures, sounds, models, and other client assets belong in
resource_packs. - If the download contains both, preserve both folders and place each in its corresponding directory.
For a pack used by only one world, use that world’s pack directories under worlds/<world-name> when your server layout provides them. A shared top-level folder does not automatically activate the pack for every world; activation is still controlled by the selected world’s JSON files.
Activate the pack in the correct world
Check the two world pack files
Inside the folder for the running world, inspect world_behavior_packs.json for behavior packs and world_resource_packs.json for resource packs. These files tell the server which available packs to load. A folder copied to a top-level directory but omitted from the relevant world file remains inactive.
- Stop the server so it cannot rewrite files while you edit them.
- Confirm the server’s active world name in its configuration or startup output.
- Open
worlds/<world-name>, not a similarly named backup or template world. - Open the behavior or resource pack JSON file that matches the pack.
- Make sure the pack has an entry containing the UUID and version from its manifest.
- Save the file, start the server, and inspect the log before joining.
If the pack works in a test world but not your main world, the files are probably valid and the main world’s activation entry, folder name, or world selection is wrong. If it fails in every world, continue with the manifest and compatibility checks.
Rank #2
- Play and share with friends on console, mobile and Windows 10
- discover community creations in the new in-game store
- access new mini games and game modes through servers
Match the manifest UUID and version exactly
Use the header identity
Open the pack’s manifest.json. The UUID used to activate a pack is the UUID in the manifest’s header object. A UUID from a module object, a filename, or a download page is not a substitute. Copy the header UUID exactly, including every character and hyphen.
Keep the version synchronized
The header also contains a version array. The version recorded in the world pack JSON must match that header version. An otherwise correct folder can be ignored when the UUID is right but the version is stale, or when the version is right but the UUID belongs to an older revision of the pack.
When replacing a pack with a newer download, treat it as a new deployment: compare the new header UUID and version with the existing world entry rather than assuming the old values still apply. Remove obsolete entries if the publisher changed the pack identity.
Recommended Free Tools
Distinguish engine fields
min_engine_version, when present in a manifest, declares the minimum engine version required to parse that pack’s JSON. It is not the pack’s activation UUID or its world-entry version. The world’s base_game_version controls how vanilla elements behave in that world. Changing either field casually can create a different compatibility problem, so first restore the values supplied with the pack and test on the server version you actually run.
Repair behavior-pack dependencies
A behavior pack can depend on a resource pack. In that case, the dependency UUID recorded by the behavior pack must equal the resource pack’s header UUID. The two packs can be in the right directories and both can have valid manifests yet still fail to load together if the dependency points to an old resource-pack identity.
- Open the behavior pack manifest and list every dependency UUID.
- Open the manifest for the required resource pack.
- Compare each dependency with the resource pack’s header UUID, not its module UUID.
- Update the world resource-pack entry if the resource pack’s header version changed.
- Restart and check the log for a missing or ignored pack message.
If the add-on’s download includes a matched pair, keep the pair from the same release. Mixing a behavior pack from one release with a resource pack from another is a frequent cause of missing visuals or partial loading.
Read the restart log instead of guessing
Restarting is required after changing world pack files, but the restart itself is also a diagnostic test. Read the server log immediately after startup and search for the pack name, UUID, and words such as not found, ignored, invalid, or dependency.
Rank #3
- Minecraft is a game about placing blocks and going on adventures
- Explore randomly generated worlds and build amazing things from the simplest of homes to the grandest of castles
- Play in creative mode with unlimited resources or mine deep into the world in survival mode, crafting weapons and armor to fend off the dangerous mobs
- Play on the go in handheld or tabletop modes
- Includes Super Mario Mash-Up, Natural Texture Pack, Biome Settlers Skin Pack, Battle & Beasts Skin Pack, Campfire Tales Skin Pack; Compatible with Nintendo Switch only
A warning equivalent to was not found and was ignored
generally means the world entry does not resolve to an available pack. Check, in this order, the active world folder, the extracted directory name, the header UUID, and the version. Do not keep changing unrelated settings until that warning is gone.
Use a restart cycle for each test: stop, change one thing, start, read the log, then join with a fresh client session. Changing five packs and two JSON files at once removes the evidence needed to identify the cause.
Recover when the server crashes or will not start
Validate JSON syntax
One missing comma, quote, or closing bracket can prevent the server from reading a world pack file. If the crash begins immediately after an edit, compare the file with a JSON validator or restore the last known-good backup and re-enter one entry at a time. Do not add comments to JSON files; standard JSON does not allow them.
Bisect the pack list
When the syntax is valid but startup still fails, isolate the pack rather than deleting the world.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Back up the world folder and both world pack JSON files.
- Remove all pack entries while leaving the extracted folders in place.
- Restart. If the server starts, the world itself is usable and one listed pack is the trigger.
- Add one pack entry, restart, and read the log.
- Continue until the failing pack or combination is identified.
- Test the suspected pack in a disposable copy of the world before returning it to production.
If the server still fails with every entry removed, the problem is not being caused by pack activation alone. Check the server version, recent configuration changes, world corruption, and the startup log’s first error rather than later cascade messages.
Resolve conflicts between two add-ons
Two packs can target the same definition. For example, two behavior packs may both replace player.json. They cannot both provide independent replacements for that file; according to common Bedrock hosting guidance, only the first applicable pack wins. The result can look random when load order changes, but it is a conflict, not a missing installation.
- Disable one pack in the world behavior or resource JSON.
- Restart and test the remaining pack in the same scenario.
- Swap which pack is enabled and test again.
- If each works alone, compare the files they both change.
- Keep one replacement, obtain a compatible combined release, or remove the feature that cannot coexist.
Do not solve a conflict by copying files from one pack into another unless you understand the pack’s manifest, namespaces, dependencies, and update path. A manual merge can make future updates impossible to diagnose.
Rank #4
- Skins! We have biome settlers, city folk, town folk, and more!
- The Nether and all its inhabitants. Fight Ghasts and make friends with Pigmen
- Cross platform play for up to five players between Pocket Edition and Windows 10
- Revamped touch controls, controller support, and a controller mapping screen
- Enhanced Weather effects! Accumulating snow and more
Check what the connecting player must do
Resource-pack-only add-ons
Textures, sounds, and other resource assets are delivered to connecting clients. A player who declines the download, joins with a stale cached pack, or disconnects before the transfer completes may continue seeing vanilla assets even though the server loaded the pack correctly. Have that player reconnect and accept the prompt; test with a second client to distinguish a server problem from a single client’s cache or settings.
Behavior packs that require acceptance
Gameplay-changing behavior packs can also require each player to accept a download prompt on first join. A player who rejects it may see ordinary visuals or fail to interact with the custom content while other accepted players work normally.
Forcing a resource download
One hosting guide recommends texturepack-required=true in server.properties to require the texture pack. Treat that as version-specific guidance rather than a universal fix: confirm that the setting is supported by your Bedrock server build, make a backup of the configuration, restart, and verify the prompt with a test account. A forced download cannot repair a wrong UUID, missing world entry, or broken resource pack.
Enable required experimental gameplay options
Some add-ons depend on experimental gameplay toggles in the world settings. Without the required toggle, a pack may appear enabled while its custom components, entities, or scripts do nothing.
- Read the add-on’s manifest or release notes for the named experiment.
- Back up the world before enabling it; experimental options can affect future compatibility.
- Enable the option in the world’s settings using the Bedrock server’s supported configuration method.
- Restart and test the exact feature that previously failed.
Do not enable every experiment as a blanket remedy. Extra toggles make later troubleshooting harder and may change vanilla behavior unrelated to the add-on.
Account for a game-version update
Compatibility can change even when you touch no files. A hosting report about the Bedrock 26.50 update says protocol behavior changed for some older packs: they started successfully but later broke blocks or entities. That report is not confirmed by an official Microsoft source, so treat it as a warning rather than a guaranteed 26.50 behavior.
When a problem begins immediately after an update:
- Back up the world and copy the current pack folders.
- Record the Bedrock server version and the pack release versions.
- Test the world with all nonessential packs disabled.
- Re-enable packs one at a time and test their affected blocks, entities, recipes, or visuals.
- Check whether the pack author provides a release for the new game version.
- Keep the backup and a known-good server build available until the complete pack set passes testing.
A pack that loads without a startup error is not necessarily compatible. Verify the actual gameplay systems it changes.
Best Value
- Explore randomly-generated worlds and build amazing things from the simplest of homes to the grandest of castles
- Play in Creative Mode with unlimited resources or mine deep into the world in survival mode, crafting weapons and armour to fend off the dangerous mobs
A clean installation procedure
Use this sequence when you want to eliminate installation mistakes rather than troubleshoot an existing deployment.
- Back up first. Stop the server and copy the entire world folder, including its pack JSON files.
- Prepare the files. Extract every
.mcpackor.mcaddon; ensure each pack folder containsmanifest.jsonat its top level. - Separate pack types. Place behavior folders in
behavior_packsand resource folders inresource_packs, using the shared or per-world location intentionally. - Read the manifests. Record each header UUID, header version, dependency UUID, and any required minimum engine version or experiment.
- Select the real world. Confirm the exact world directory the server starts, then open its
world_behavior_packs.jsonandworld_resource_packs.json. - Activate matching entries. Add the header UUID and matching version to the correct world file; add both behavior and resource entries when the add-on requires both.
- Validate syntax. Check commas, brackets, quotation marks, and duplicate or obsolete entries.
- Start and inspect. Restart once, read the log, and resolve any not-found, ignored, invalid, or dependency warning before inviting players.
- Test one feature. Join with a client, accept any download prompt, and test the specific gameplay or visual change.
- Add the next pack only after success. This preserves a clear cause-and-effect trail and makes conflicts easy to identify.
Use a symptom-based decision path
Nothing changes in the world
Confirm the world pack JSON entry first, then verify the header UUID and version, then check that the server is running the world folder you edited. If the log says the pack was ignored, fix identity or path data before checking experiments.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →The pack is listed but visuals are missing
Check that the resource pack is extracted, listed in world_resource_packs.json, and referenced by the behavior pack’s dependency UUID. Reconnect a client and accept the download. Test with another client before changing server files.
Only one feature fails
Check the required experiment and the pack’s minimum engine requirement. Then look for another pack replacing the same definition. A partial failure after a game update points toward compatibility rather than activation.
The server crashes after adding several packs
Restore the backup, validate both JSON files, remove all entries, and re-add packs one at a time. The first entry that reproduces the crash identifies the pack; if each works alone but the combination fails, investigate a conflict.
Prevent the next outage
- Keep a dated backup before installing, updating, or enabling experiments.
- Store the original archive and the extracted folder so you can reproduce the installation.
- Record each pack’s header UUID and version alongside the world name.
- Use one test world for new add-ons before changing a busy survival world.
- Restart and read the log after every world JSON change.
- Install behavior and resource packs from the same release when they are distributed as a pair.
- Remove stale entries when replacing a pack whose UUID or version changed.
- After a Bedrock update, test blocks, entities, recipes, textures, and sounds rather than relying on a clean startup.
The reliable mental model is simple: a Bedrock add-on must be an extracted, readable folder; the active world must explicitly list it; the listed UUID and version must match the manifest; dependencies must point to the correct headers; and clients and game versions must support what the pack changes. Checking those layers in that order is faster and safer than repeatedly reinstalling the same archive.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
