What Is an Add-on Manager for Minecraft Bedrock and What Can It Do?

An add-on manager is a tool that lists the behavior packs and resource packs attached to a Minecraft Bedrock world and lets you enable, disable, or remove them without hand-editing the world's files. It's useful when you want to change a world's add-ons after creation, when a pack is causing errors or conflicts, or when you've accumulated packs you no longer use. Desktop world editors such as Bedrock Toolchest include add-on management as one of their features, alongside things like game rule editing and inventory editing.

Add-ons, behavior packs, and resource packs

In Bedrock, an "add-on" is usually a bundle of one or both of these pack types:

• Behavior packs carry the logic: new entities, items, blocks, loot tables, scripts, and changes to existing game behavior.
• Resource packs carry the presentation: textures, models, sounds, UI, and language files.

A world stores which packs it uses, so the same add-on can be active in one world and absent in another. That per-world attachment is exactly what an add-on manager reads and writes.

What an add-on manager lets you do

The core job is managing the list of packs attached to a world:

• View every behavior and resource pack currently linked to the world, including ones you may have forgotten about.
• Enable or disable a pack without deleting it, so you can test whether it's the cause of a problem.
• Remove packs you no longer want, which also detaches their content from the world.
• Install or attach a new pack to an existing world rather than starting a fresh one.

Because these actions happen on the world's pack list, they take effect the next time the world loads.

Why not just drop packs into the world folder?

You can manage packs by moving files into a world's folders by hand, but it's easy to get wrong:

• A behavior pack and its matching resource pack must both be attached, or you get missing textures or non-functional content.
• Pack UUIDs and versions must line up between the manifest and the world's references. A mismatch can make the pack silently fail to load.
• Leftover entries for deleted packs can produce load errors or "missing dependency" warnings.
• Manually editing world data risks corrupting the world if something is malformed.

A manager handles the bookkeeping — matching behavior and resource packs, writing correct references, and clearing out stale ones — so you avoid broken or conflicting packs.

Common tasks

Installing a new add-on into an existing world: open the world in the manager, add the pack, and confirm both its behavior and resource components are attached. Load the world to verify the content appears.

Toggling packs on or off: disable a pack to isolate a conflict, load the world, and see whether the problem goes away. Re-enable it if it wasn't the cause.

Cleaning up unused packs: remove packs you've stopped using so the world's pack list stays short and free of dangling references.

What an add-on manager can't do

• It doesn't edit the internal behavior of a pack — changing a mob's stats or a script's logic means editing the pack itself, not the manager.
• It doesn't convert Java mods into Bedrock add-ons; the two formats aren't interchangeable.
• It manages which packs a world uses, not the packs' contents.

Where to find one

Add-on management is typically bundled into a broader Bedrock world editor rather than sold as a standalone tool. Bedrock Toolchest, a free desktop app for Windows and Linux that edits Bedrock worlds, lists add-on management among its features — the same app also covers game rules, inventories, villager trades, and chunk pruning. If your goal is only to attach or remove packs for a world, any world editor that exposes the pack list will do the job.