Global Packs in All the Mons

Global Packs is a small utility mod that loads data packs and resource packs for every world, so you don't have to copy them into each new world by hand. If you always run the same quality-of-life data packs, it saves you that chore every time.^[1]

It also exists for modpack creators. Packs placed in its folders get exported with the modpack, so anyone who downloads it gets the custom data straight away.^[1]

This pack includes Global Packs 21.0.6, the NeoForge build for Minecraft 1.21.1.^[2]

How it works

• Data packs: drop them into the datapacks folder in the instance folder. They load automatically whenever you generate a new world. You can also set a custom folder path in the global_packs.toml config file.^[1]
• Pack formats: both .zip files and unpacked folders work, as long as there is a valid pack.mcmeta directly inside.^[1]
• Resource packs: add them to the resourcepacks section of the config and they are force-loaded (required) for the player. The same applies to built-in packs from other mods.^[1]
• Priority: it follows the order in global_packs.toml, and the pack listed first has the highest priority.^[1]

Global Packs is a lightweight utility mod. It automatically loads your favorite data packs and resource packs across all your worlds, so you don't have to copy them into every new world by hand. This section covers how to set it up.^[1]

Unverified The sources here do not show any recipes or quests for this mod in this pack, so there are no recipe blocks in this section.

What it does for you

Data packs placed in the global folder load every time you generate a new world. Modpack creators can use the same setup to make sure players get their custom content right out of the box.^[1]

Adding your own data packs

1. Put your data pack in the datapacks folder inside your instance folder. This works for Minecraft 1.16 to 1.21+. You can also set a custom folder path in the global_packs.toml config file.^[1]
2. Use either a .zip file or an unpacked folder. Either way, it needs a valid pack.mcmeta file, and that file must sit directly inside the folder or zip, not in a sub-folder.^[1]
3. Create a new world. The packs load automatically when a world is generated.^[1]

Forcing resource packs

To force-load resource packs, or built-in packs from other mods, you add them to the matching section of global_packs.toml. Resource packs you add there are force-loaded (required) for the player.^[1]

For example, a resource pack at resourcepacks/FreshAnimations_v1.10.5.zip in your instance goes in the required list under the resourcepacks section of the config.^[1]

Load order and troubleshooting

Priority follows the order in global_packs.toml, and the pack listed first has the highest priority in-game.^[1]

If your packs aren't loading, check these common causes first:^[1]

• The data pack format is outdated for your current Minecraft version.^[1]
• The folder or zip is badly structured, for example with pack.mcmeta buried in a sub-folder.^[1]
• There's a typo in global_packs.toml. If the mod detects an error in the TOML file, it may struggle to load the packs.^[1]

Global Packs isn't a machine or automation mod. It's described as a simple, lightweight utility that loads data packs and resource packs across all your worlds automatically. So there's no power, fluid or item handling to learn here. The mechanics are about where packs go and how they load.^[1]

How data packs load

Once the mod is installed, it generates a /datapacks/ folder. Drop your data packs in there and they load automatically every time you generate a new world, so you don't have to copy them into each world by hand.^[1]

On Minecraft 1.16 to 1.21+, you can put data packs directly in the datapacks folder of the instance. You can also set a custom folder path in the global_packs.toml configuration file. On older versions (1.13 to 1.15), the folder is called global_data_pack (or global_data_packs) and is generated automatically.^[1]

Packs can be .zip files or normal unpacked folders. Either way, all the mod needs is a valid pack.mcmeta file.^[1]

Forcing resource packs and built-in packs

Resource packs, and built-in packs from other mods, don't load just by sitting in a folder. You add them to the matching section of the config. Packs listed there are force-loaded, meaning they're required for the player.^[1]

For example, a resource pack at resourcepacks/FreshAnimations_v1.10.5.zip inside the instance is listed under the resourcepacks section, in its required list, using that relative path. More packs go in the same list, separated by commas.^[1]

Load order and priority

Priority follows the order of entries in global_packs.toml. The pack listed first has the highest priority in-game.^[1]

Why a pack might not load

• The data pack format is outdated for your current Minecraft version.^[1]
• The folder or .zip isn't structured correctly. The pack.mcmeta must sit directly inside the folder or zip, not in a sub-folder.^[1]
• There's a typo in global_packs.toml. If the mod finds an error in the TOML file, it may struggle to load the packs.^[1]

Unverified Which data packs or resource packs this pack actually ships through Global Packs, and whether it changes any of the mod's settings, can't be confirmed from the available sources. No config file for this mod was found in the pack.

All the Mons 1.3.0 ships Global Packs 21.0.6, and the mod has been in the pack since 0.11.0-beta or earlier. There are no pack changelog entries for this mod, so this section only covers the mod's own changelog, from 21.0.2 up to the version you have.^[2]

21.0.6 (the version in this pack)

• The config for builtin datapacks and builtin resourcepacks is now split. The changelog apologises for the inconvenience, so check your config if you edited it by hand.^[3]
• Your config formatting will no longer be overwritten all the time.^[3]
• Packs added through folder entries in the config can now be given a lower priority by specifying a specific file.^[3]

21.0.5

• Added a config option that, when set to true, logs the IDs of all available packs.^[3]
• Added a config option holding a list of pack IDs to enable, which can be used to enable builtin resourcepacks from mods.^[3]

21.0.4 and 21.0.3

• 21.0.4 was a Forge-only fix. This pack runs the NeoForge build, so it doesn't affect you.^[2][3]
• 21.0.3 fixed packs not loading (the changelog says whoops).^[3]
• The load order from the config is now respected. Datapacks and resourcepacks are listed in the same order as in the config, and the first entry in the config has the highest priority in game. The config is converted automatically if you were on 21.0.1 before.^[3]
• The mod now only messes up your config if an error was detected.^[3]
• Force enabled resourcepacks no longer show twice in the resourcepack list.^[3]

21.0.2

• The default config was changed for compatibility with upcoming CF changes.^[3]
• Updating automatically adds the instance folder's datapacks/ folder to the config, and CF will load datapacks from that folder.^[3]
• The config was renamed to global_packs.toml, and it is renamed automatically.^[3]
• Folders listed in the config are now created automatically, and more reliably than before.^[3]