How to Install and Use Datapacks on Your Minecraft Server

Your players want one-player sleep. They want a crafting recipe for bundles. They want creeper explosions that don't leave craters in the landscape. And you want to give them these things without installing Forge, without migrating to Paper, without breaking vanilla compatibility for the purist in your group who insists on playing with an unmodified client.

Datapacks solve this problem. They're Minecraft's native customization layer — built into the game since 1.13, requiring no server software changes, no client mods, and no external dependencies. A datapack is just a folder with some JSON files that Minecraft reads when the world loads. Drop it in, reload, done.

This guide covers the full workflow: what datapacks can actually change, where to find good ones, how to install them on your server, and how to troubleshoot when something goes wrong.

What Datapacks Can Do

Datapacks modify the data-driven parts of Minecraft — the systems defined in JSON rather than compiled code. This gives you more flexibility than you might expect, but also clear boundaries.

Things datapacks can change

The most popular use cases are quality-of-life recipes (like VanillaTweaks' craftable bundles or stackable potions), loot tweaks (like guaranteed blaze rods or better mob head drops), and small gameplay changes (like one-player sleep or anti-enderman-griefing).

Things datapacks cannot change

Datapacks work within vanilla Minecraft's framework. They cannot:

• Add new blocks, items, mobs, or textures (those require mods or resource packs)
• Change the fundamental mechanics of combat, movement, or physics
• Run arbitrary code or interact with external systems
• Modify the client interface or HUD

If you need new content rather than tweaks to existing content, you're looking at mods. But if you want to adjust how existing systems behave — and keep your server joinable by any vanilla client — datapacks are the right tool.

Finding Datapacks

Three sources cover most of what you'll ever need.

VanillaTweaks

vanillatweaks.net is the gold standard for quality-of-life datapacks. It's a curated collection from the Hermitcraft community, organized by category. You pick the tweaks you want from a checklist, and it generates a single combined datapack for download.

Popular picks include:

• One Player Sleep — anyone can advance to morning without waiting for the whole server
• Multiplayer Sleep — configurable percentage required (50%, 25%, etc.)
• Anti Creeper Grief — creepers still explode and deal damage, but don't destroy blocks
• Anti Enderman Grief — endermen can't pick up blocks
• Wandering Trades — hermit-style mini-blocks, custom heads, and decorative items from the wandering trader
• Craftable Bundles — because the bundle recipe is still "coming soon" after several versions

VanillaTweaks also offers resource packs and crafting tweaks. If you're building a pack for your SMP, start here.

Modrinth

Modrinth has grown beyond mods to host datapacks, resource packs, and shaders. Search with the "Datapack" filter, and you'll find everything from minor tweaks to elaborate overhauls. Each pack lists its supported Minecraft versions, so you can filter for compatibility with your server.

The rating and download counts give you a rough quality signal. Check the version history — a datapack last updated two years ago might not work with current Minecraft versions.

Planet Minecraft

planetminecraft.com has a broader range, from polished community projects to one-off experiments. Quality varies more than Modrinth or VanillaTweaks, so read the comments and check when it was last updated.

Planet Minecraft is particularly good for niche ideas — obscure recipe changes, specific adventure-map mechanics, or unusual world generation tweaks that haven't made it into the major repositories.

Installing Datapacks

A datapack is a folder (or a .zip file) that goes in your world's datapacks directory. That's it. No installer, no dependencies, no server restart required if you use the reload command.

Step 1: Download the datapack

Download your chosen datapack. It will be either:

• A .zip file (keep it zipped — Minecraft reads zipped datapacks directly)
• An unzipped folder containing pack.mcmeta and a data folder

Either format works. Don't unzip files that are meant to stay zipped, and don't zip folders that are meant to stay unzipped. Check the download page if you're unsure.

Step 2: Locate your world's datapacks folder

On your Minecraft server, datapacks go in:

<your-world-folder>/datapacks/

For most servers, the world folder is named world by default (configurable in server.properties via the level-name setting). So the path is usually:

world/datapacks/

If you're running multiple dimensions, note that datapacks apply to the entire server — you only need to add them to the main world folder, not to world_nether or world_the_end.

Step 3: Upload the datapack

You have two options on Swelis:

Option A: File Manager (no software required)

Open the Swelis control panel, go to your Minecraft service, and click Files. Navigate to world/datapacks/, then drag and drop your datapack file or folder into the browser window. The upload happens directly — no FTP client needed.

Option B: FTP

If you prefer a dedicated client (FileZilla, WinSCP, Cyberduck), connect using the FTP credentials from your service dashboard. Navigate to /world/datapacks/ and upload there. FTP is faster for bulk uploads if you're adding many datapacks at once.

Step 4: Enable the datapack

If your server was running when you uploaded the datapack, run this command in the server console:

/reload

This reloads all datapacks without restarting the server. Players stay connected, the world stays loaded, and the new datapack becomes active immediately.

To verify it loaded, run:

/datapack list

This shows all enabled and disabled datapacks. Your new datapack should appear in the "available" list with [file/your-datapack-name] formatting.

The /datapack Commands

Minecraft's built-in /datapack command manages everything. Here's the full reference.

The priority system matters when two datapacks modify the same thing. A datapack that runs "last" wins — its loot table or recipe overrides earlier ones. For most servers with a handful of non-conflicting datapacks, you can ignore priority entirely. But if you're stacking multiple packs that touch the same game systems, use enable <name> last for the one you want to take precedence.

Example workflow

You've uploaded three datapacks: vanilla-tweaks.zip, custom-recipes.zip, and extra-loot.zip. Your server is running. In the console:

/reload
/datapack list

Output shows all three as available but disabled. Enable them:

/datapack enable "file/vanilla-tweaks.zip"
/datapack enable "file/custom-recipes.zip"
/datapack enable "file/extra-loot.zip"

Note the exact name format: file/ prefix plus the exact filename including extension, in quotes. Tab completion works in the console, so you can type /datapack enable file/ and press Tab to cycle through available packs.

Troubleshooting

When a datapack doesn't work, the problem is almost always one of these.

"Datapack not showing in /datapack list"

The datapack isn't in the right folder, or it's malformed.

Check the folder structure. A valid datapack has this layout:

your-datapack/
├── pack.mcmeta
└── data/
    └── (namespace folders with functions, recipes, etc.)

If you uploaded a .zip file, the structure inside the zip should match this. Some downloads nest the datapack inside an extra folder — you end up with world/datapacks/download-folder/actual-datapack/pack.mcmeta when it should be world/datapacks/actual-datapack/pack.mcmeta.

Unzip, fix the nesting, and re-upload.

"Datapack shows as available but won't enable"

Usually a version mismatch. Check the pack.mcmeta file inside the datapack:

{
  "pack": {
    "pack_format": 48,
    "description": "My cool datapack"
  }
}

The pack_format number must match your Minecraft version. For 1.21.x servers, you need pack format 48. Older datapacks with lower format numbers may still work, but Minecraft will warn you. Much older datapacks (format 10 or below) often fail silently because the underlying JSON structure changed.

Check the datapack's download page for an updated version, or look for a fork that's been maintained.

"Datapack enabled but nothing changed"

Three possibilities:

1. The datapack affects something you haven't tested. If you installed a loot table change, you need to kill a mob or open a chest to see it. If you installed a recipe, open a crafting table. Verify you're testing the right thing.

2. Another datapack has higher priority and overrides it. Run /datapack list enabled and note the order. Datapacks listed later override earlier ones. If your recipe pack appears before another pack that also modifies recipes, the later one wins.

3. The datapack has a syntax error. Check your server logs (in the logs/ folder or via the console panel). JSON parse errors appear when the world loads or when you run /reload. A single misplaced comma can break an entire datapack.

"Server crashed after adding datapack"

Datapacks are data, not code — they can't crash a server in the traditional sense. But a datapack with extremely aggressive world generation settings or a function that loops infinitely can freeze or choke the server.

If you can't join or the server hangs on startup, connect via FTP or file manager and move the problematic datapack out of the datapacks folder. Restart the server. It will load without that datapack, and you can investigate what went wrong.

Managing Multiple Datapacks

Servers often run five or more datapacks simultaneously. A few practices keep things manageable.

Use VanillaTweaks' combined pack

Instead of downloading ten separate datapacks from VanillaTweaks, use their picker to generate a single combined pack. One file, one enable command, no priority conflicts between tweaks.

Document what you have

Keep a note (in your server docs, a Discord channel, or a text file) listing:

• What datapacks are installed
• Where you downloaded them from
• What Minecraft version they were built for
• Why you added them

When you update Minecraft versions, you'll know exactly what needs checking.

Test before going live

Before adding a new datapack to your main world, test it in a singleplayer world or a staging server. This is especially important for world generation changes — those are difficult to undo once chunks have generated.

Back up before changes

Take a backup before adding or removing datapacks that affect world generation or loot tables. On Swelis, click Backups in your dashboard and create a manual backup. If the datapack breaks something, you can restore to the pre-change state. For more on backup workflows, see the backup strategies guide.

Datapacks vs. Plugins vs. Mods

Datapacks occupy a specific niche. Understanding where they fit helps you pick the right tool.

If you want one-player sleep and nothing else, a datapack is the right choice — it takes thirty seconds to install and works forever. If you want a full economy system with shops and auctions, you need plugins on Paper or Purpur. If you want new dimensions, magic systems, and technology trees, you're in mod territory.

Many servers mix approaches. A Paper server can run datapacks alongside plugins. A Forge server can run datapacks alongside mods. They're not mutually exclusive — datapacks are just the lightest-weight option for the subset of changes they support.

Quick Reference

Related Guides

• Minecraft Server Console Commands Cheat Sheet — full reference for console commands including /reload and /datapack
• Minecraft server.properties Explained — configure level-name and other world settings
• A Complete Tour of the Swelis Control Panel — navigate the file manager, backups, and console
• One-Click Modpack Install — if you decide datapacks aren't enough and want full modpacks
• Paper, Purpur, Fabric, or Forge? — comparing server software when you need more than datapacks offer
• Backup Strategies for Game Servers — always back up before adding datapacks that modify world generation