How to Share a Paxi Setup in a Modpack

Why Paxi Helps Modpacks

Paxi lets you bundle global datapacks and resource packs so every player gets them automatically on new worlds. This avoids the common problem of players joining without essential packs and seeing missing textures or broken datapack features.

Packaging the Files

Place your datapacks in config/paxi/datapacks and your resource packs in config/paxi/resourcepacks. If load order matters, edit config/paxi/datapack_load_order.json to define the sequence. Keep all filenames consistent, because Paxi matches entries by name.

Distributing to Players

Include the entire config/paxi folder in your modpack export. When players install the pack, Paxi will read these folders on startup and apply the packs to their new worlds. No manual enabling is required on their end.

Testing Before Release

Generate a brand-new world in a clean instance and run /datapack list to verify the datapacks loaded. Check a few textures or sounds from your resource packs to confirm they applied. Because forced resource packs cannot be disabled in-game, test carefully so you do not ship a broken or unwanted pack.

Updating Later

When you change a pack, update the files in the paxi folders and re-export. Players who already generated worlds may need a new world to see datapack changes, while resource pack changes apply on the next launch.