Minecraftforge: Add a way for modpacks to ship datapacks in the same way they can ship configs.

Created on 24 Oct 2019 · 6Comments · Source: MinecraftForge/MinecraftForge

I recently released a mod that is extensible via datapacks, but I realized that this might actually be limiting for end users.

Right now datapacks are dependent on the end user to know how to install a datapack (in vanilla), or to use a mod that provides the specific datapack for the modpack.

The issue is that you end up with each modpack requiring a mod to be created to add datapacks.

Feature Stale

Source

ExpensiveKoala

Most helpful comment

Here you go @ExpensiveKoala https://www.curseforge.com/minecraft/mc-mods/drp-global-datapack does it in the same way Resource Loader does.

Tfarcenim on 24 Oct 2019

👍2 🚀1

All 6 comments

Doesn't a datapack loader already exist that can load external datapacks in the same way Resource Loader handles resource packs without requiring a secondary mod?

Tfarcenim on 24 Oct 2019

+1 for the ability for a mod to expose multiple datapacks (instead of just one for the entire mod. think how MC exposes both the default RP and the programmer art RP). But it'd be tricky to declare exactly what resources go in which pack.

in the meantime, mods like resource loader (if it's ported?) can take responsibility of exposing everything in a given folder as a pack.

williewillus on 24 Oct 2019

@Tfarcenim I don't know if one already exists like that, but I also don't want to point people to use a mod to customize a feature that is using a vanilla mechanic... if that makes sense. I leave it up to the forge maintainers to decide if this should be a forge feature or be left up to mods to be created to handle this specific task.

@williewillus I agree on that +1, but it should be it's own issue/PR.

ExpensiveKoala on 24 Oct 2019

Here you go @ExpensiveKoala https://www.curseforge.com/minecraft/mc-mods/drp-global-datapack does it in the same way Resource Loader does.

Tfarcenim on 24 Oct 2019

👍2 🚀1

This issue has been automatically marked as stale because it has not had activity in a long time. If this issue is still relevant and should remain open, please reply with a short explanation (e.g. "I have checked the code and this issue is still relevant because ___." or "Here's a screenshot of this issue on the latest version"). Thank you for your contributions!