Build & ship Free~5 minutes
Update a pack you already installed
Updating a Minecraft pack is the step that trips people up. Do it right and Minecraft quietly replaces the old version. Do it wrong and you end up with the same pack listed three times in your world — with no version numbers to tell them apart. Here's how to update cleanly, and how to dig out if you're already in the mess.
The one rule: always bump the version and
re-export from the same MiniBench project. That keeps the pack's identity stable, so Minecraft
treats the import as an update — not a brand-new pack.
-
Make your change
Open your project and edit away — here we add a setblock … glowstone to top the house with a light. Anything you change, add, or remove is fair game. -
Bump the version — the step that matters
Open manifest.json and raise the version with the steppers — here 1.0.1 → 1.0.2. Minecraft uses the version to decide whether an import is an update: same pack identity + a higher version = replace the old one. Skip this and Minecraft may ignore the import or, worse, keep a stale copy. -
Re-export and re-import
Tap Export, choose Minecraft in the share sheet, and let it import — exactly like the first time. Because you exported from the same project, the pack keeps its identity and this comes in as version 1.0.2 over 1.0.1. -
Check the world's Behavior Packs
Here's the part most guides skip. Open the world, pause → Settings → Behavior Packs. Active is what the world is actually running; My Packs is everything available. An already-open world doesn't always hot-reload an update — this screen is where you confirm the new version is the one that's on. -
Watch out for duplicates
This is the annoying failure mode: the same pack, Redstone Manor, listed three times — no version numbers, all active. It happens when copies with different identities pile up (importing a fresh copy instead of updating, or re-importing a pack back into MiniBench, which gives it a new identity). And note Minecraft's own warning: packs are applied bottom to top, so a stale copy sitting above your new one silently wins.
If you already have duplicates
- · In Settings → Behavior Packs → Active, tap each extra copy and remove it (drag it out of Active) until only one remains.
- · Not sure which is newest? They don't show versions, so the safe move is to remove all copies from the world, then re-add just the current one from My Packs.
- · Then re-run your /function — the world is now on a single, known version.
To avoid it entirely: keep one project per pack in MiniBench, always bump the version, and re-export from that project. Don't re-import your own .mcpack back into MiniBench just to edit it — open the original project instead.
New to the whole flow?
See a pack go from blank to in-game the first time.
Your first pack, end to end