GuidesOnly show guides for your app
GuidesGuidesAdd datapacks from the panel's Datapacks page, understand why they live inside a world, and activate, list, and remove them cleanly with /reload and /datapack.
Datapacks change your world using nothing but vanilla Minecraft — custom recipes, new loot, tweaked world generation, custom functions — and, crucially, players install nothing on their end. That makes them the friendliest way to add content to a survival server. This guide covers the panel's Datapacks page, where the files actually go, and how to switch them on, list them, and remove them without leaving junk behind.
| At a glance | |
|---|---|
| You need | A running Minecraft Java server and a world |
| Time | Ten minutes |
| Plan | Any |
A datapack belongs to one specific world. It lives in that world's folder, under <world>/datapacks — so a pack installed to your survival world does nothing for a second world on the same server. This single fact explains every "why didn't it work" further down: install to the world your server actually loads (the one your level-name points at). More on worlds: Manage your worlds.
Open the Datapacks page from your server menu. It searches Modrinth, the community's datapack index.
<world>/datapacks for you. You'll see a confirmation naming the world it installed to.💡 Tip: No world in the dropdown, or the wrong one selected, and the install has nowhere to go — the page will ask you to pick a world first. Generate or upload a world on the Worlds page if you don't have one yet.
Got a .zip from elsewhere (a friend, a creator's site)? Install it by hand:
datapacks folder (create datapacks if it isn't there)..zip as-is — don't unzip it. A datapack is a zip containing a pack.mcmeta and a data/ folder; the server reads the zip directly.Minecraft only notices a new datapack when it (re)loads packs. Two ways:
/reload in the Console — reloads datapacks live, no downtime. Great for a quick recipe or loot tweak.🎯 Good to know:
/reloadre-runs datapacks and reloads some plugin data, but it is not a fix-all — a misbehaving plugin can dislike it. When something looks half-applied after a/reload, restart and check again before assuming the pack is broken.
Check what's active any time with /datapack list in the console — it prints the enabled and available packs. /datapack enable "<name>" and /datapack disable "<name>" turn a specific one on or off without deleting it.
To remove one for good:
/datapack disable "file/<name>.zip" in the console..zip from <world>/datapacks./reload (or restart) so the server drops it.Removing a datapack stops its rules going forward, but it does not undo what it already did — blocks it generated or items it created stay in the world. That's normal; datapacks change the world, they don't sandbox it.
Run /datapack list — your pack should appear under the enabled list. Then check its effect in-game: try the new recipe, look for the new loot, or explore fresh chunks for worldgen packs. If it's a function pack, its functions show up under /function tab-completion.
/reload. Confirm with /datapack list on the world your level-name loads./datapack list shows it "available" but not "enabled" — enable it: /datapack enable "<name>"..zip; the server expects the zip (or a single folder containing pack.mcmeta), not its loose contents scattered in datapacks.