Drop pak mods into Minecraft Dungeons: the ~mods folder method

Minecraft Dungeons takes mods as Unreal pak files you place in a specific folder, and getting that folder right is most of the battle. This guide installs a pak mod, explains the alphabetical load order, and adds the Blueprint Loader for mods that need it.

Find your Paks folder

1. In Steam, right-click Minecraft Dungeons and choose Manage, then Browse local files.
2. In the folder that opens, go to Dungeons\Content\Paks.
3. Create a new folder here named ~mods, with the leading tilde exactly as written.

That tilde matters. The game looks for the ~mods folder specifically, and leaving it off is the most common reason a mod does not load.

Install a pak mod

1. Download the mod. It is a .pak file, sometimes inside a .zip you extract first.
2. Copy the .pak into the ~mods folder you created.
3. Launch the game. The mod is active.

To uninstall, delete the .pak from ~mods. Nothing else changes.

Control load order

The game loads paks in alphabetical order, and a mod later in the alphabet overwrites one earlier. When two mods touch the same content, the later name wins.

• To force a mod to load last, rename its file so it sorts later, for example by adding a zz_ prefix.
• To make one load first, give it an aa_ prefix.
• Keep a note of your renames so you remember what each pak is.

Add the Blueprint Loader for advanced mods

Some mods do more than swap assets; they run Unreal blueprints. Those depend on the community Blueprint Loader.

1. Download the Blueprint Loader and install its pak into ~mods like any other.
2. Install the mods that require it.
3. Launch. The loader lets those mods register blueprints that run on their defined triggers.

If a mod's page says it needs the Blueprint Loader, it will not work without it.

Where to find mods

The Dungeons scene is split across two sites, and it is worth checking both.

• Nexus Mods hosts most reskins, model swaps, and gameplay tweaks, with a familiar download-and-install flow.
• CurseForge carries mods and the authoring tools, including the Dungeons Mod Kit.

Whichever site a mod comes from, the install is the same: get the .pak into your ~mods folder. Read each mod's page for dependencies, since some require the Blueprint Loader and will not work without it.

A note on authoring

If you want to make mods rather than just install them, the Dungeons Mod Kit is the official-style toolset, built on Unreal Engine 4 version 4.22. The version pin is strict: installing a newer Unreal release and pointing the kit at it causes hard-to-diagnose problems, so match 4.22.x exactly. The kit is what separates simple texture swaps from mods that add or rewire content, because it gives you the editor the game was built with.

Common gotchas

• The mod did nothing. Check the folder is named exactly ~mods, with the tilde, under Content\Paks.
• Two mods conflict. Load order is alphabetical. Rename so the intended mod loads last.
• A blueprint mod fails. It needs the Blueprint Loader installed first.
• A patch broke a mod. Updates can invalidate paks. Look for an updated version on the mod's page.
• You put paks straight in Paks. They belong inside the ~mods subfolder you created, not loose in Content\Paks.
• A rename did not change anything. Only the file name affects order, not the mod's display name. Rename the actual .pak file.

Where to go next

For the wider context on the Dungeons scene and what OpenMods catalogues, see the Minecraft Dungeons overview.