Screenshot 1 of 1. MinecraftHub-generated editorial cover for Paxi, a voxel diorama around the lime MinecraftHub block
What Paxi works with.
| Platform | Java Edition |
|---|---|
| Loaders | Fabric, NeoForge |
| Minecraft versions | 1.19.2, 1.19.4, 1.20.4, 1.21.1, 26.1.2 |
| Environment | Client, Server |
Paxi is a Minecraft Java mod that loads data packs and resource packs globally, so a pack dropped into one folder applies to every world. It runs on Fabric and NeoForge, and older Forge builds exist but have stopped. Modpack creators get the most from it, since packs ship with the instance instead of being added world by world.
Loaders and versions
- Fabric: Minecraft 1.19.2 to 26.1.2. The newest build requires Cloth Config API, Fabric API and YUNG's API, optionally Mod Menu; some builds for 1.19.3 to 1.20.4 require Fabric API and YUNG's API; some builds for 1.19.2 require YUNG's API.
- NeoForge: Minecraft 1.20.4 to 26.1.2. The newest build requires YUNG's API.
- Forge: Minecraft 1.19.2 to 1.21.1, builds stopped after May 2025. The newest build requires YUNG's API.
How the paxi folder works
On first launch Paxi creates a paxi folder inside the config directory. Data packs go in its datapacks folder, which appears the first time you create or load a world. Zip files and plain folders containing a pack.mcmeta file both work. Run /datapack list in game and packs loaded by Paxi are printed in pink.
Resource packs go in the resourcepacks folder, created on first run. They load when the game starts, with the same zip and folder support.
Controlling load order
- datapack_load_order.json and resourcepack_load_order.json appear in the paxi folder. List pack names (with .zip for archives) in the order you want.
- The files are optional. Packs you leave out load alphabetically, like normal packs, so you only list the ones that need a fixed position.
- From v5.1.3, entries can use relative paths from the instance folder, for example "datapacks/MyDataPack", to pull packs from other folders.
- Also from v5.1.3, the config option Load from base 'datapacks' directory is on by default and treats the base datapacks folder like the Paxi one.
Installation
- 1.Set up Fabric or NeoForge for your game release, following the Java mod install guide if you are new to it.
- 2.Put the Paxi file and every required library from the list above into the mods folder.
- 3.Launch once so the paxi folder is generated.
- 4.Drop your packs into datapacks or resourcepacks, then load a world.
Questions about Paxi.
4 questions
How do I install Paxi?
Install Fabric or NeoForge for your game release, then place the Paxi file and its required libraries in the mods folder. Launch the game once so the paxi folder is created in the config directory. Packs you add to its datapacks and resourcepacks folders then load automatically.
Where do I put data packs for Paxi?
Put them in the datapacks folder inside the paxi folder in your config directory. That folder is created the first time you create or load a world. Zip files and folders with a pack.mcmeta file work, and Paxi's packs show in pink under /datapack list.
Does Paxi work on a multiplayer server?
Resource packs are not supported on dedicated servers, because they only change client-side assets such as textures and sounds. Paxi lists both client and server as optional sides, but its page does not describe how data packs load on a dedicated server.
Can I choose the order Paxi loads packs in?
Yes. Edit datapack_load_order.json or resourcepack_load_order.json in the paxi folder and list pack names in the order you want, adding .zip for archives. Unlisted packs still load alphabetically, so you only need to list packs that require a specific order.
