Need Help

Hey, thanks for reading this!

If you don't have a lot of experience with gradle, you probably don't even want to continue. But if you do...

So the way that Minecraft modding works is that there's a modloader (in our case Fabric) and there's Minecraft. Fabric itself provides a handy API to interact with the Minecraft code. Both of them tend to change quite significantly between version upgrades.

All the versions are handled in the gradle.properties file. Aside from this, the artifacts need to be published in a way where they're tied to a specific version of Minecraft. You can see that here

The problem

Supporting multiple versions of Minecraft.

How do others do it?

Other projects tend to have specific branches for specific Minecraft versions. This means that whenever there's a new feature added to the mod, they need to add it as many times as many different MC versions they support.

What I want to explore

I believe there has to be a way to use gradle subprojects to achieve the support of multiple Minecraft versions. I imagine extracting the points in my code that interface with Minecraft from the core of its functionality.

In this super simple codebase, this is the only line that interfaces with Minecraft. This mixin would be different for every MC version.

How I imagine things to go

I would run build from the project root and that would generate the artifacts for MC 1.18.x, 1.19.x, 1.20.x, etc, appropriately named. I can then tweak the release logic to make that happen based on file naming conventions.

Can you help me with this?

If so, hit me up on discord: houseofmeza, @meza on T2, @vsbmeza on twitter or even here in discussions or a PR. Thanks!