Porting the mod to 1.21

[NikOverflow]

I would like to backport the mod to older versions and port it to other mod loaders. I have no idea how to structure the whole thing without making maintenance too tedious. If you have any ideas on how I can structure the whole thing without using the existing multi-version/multi-loader templates, as these do not meet my requirements, please write to me here and let me know how I can solve the problem.

This issue has a low priority at the moment.

I port mod to new Minecraft versions by opening new branches 😃

[NikOverflow]

I port mod to new Minecraft versions by opening new branches 😃

@NorthRealm In theory this is a way but I don't like that way. My biggest issue is with common stuff. I don't want to copy the api and stuff that is the same everywhere. The reason why I need help is to find a better solution for that. Do you understand what I mean?

For the same common things independent of Minecraft (Abstract API things, etc), possibly host in a dedicated repository and publish as a separate maven then import back into the mod.
For multiloader, one of the common approaches is adding gradle subprojects 🤦‍♂️
For multiversion, my approach is opening branches. Lots of stuff need Minecraft. Barely any better way to it.

[NikOverflow]

For the same common things independent of Minecraft (Abstract API things, etc), possibly host in a dedicated repository and publish as a separate maven then import back into the mod. For multiloader, one of the common approaches is adding gradle subprojects 🤦‍♂️ For multiversion, my approach is opening branches. Lots of stuff need Minecraft. Barely any better way to it.

Or I do that with branches too. That I create an api branch and common branch. These branches will be published to my custom maven server. The api is already published for clients like Liquid Bounce.

[nefcomplex]

What about Stonecutter or Stonecraft (based on Stonecutter)? The main feature of Stonecutter is that it's possible to write code for all of the game versions in a single branch without duplication, and Stonecraft adds Architectury Loom on top of that for multiloader mods. For example see https://github.com/meza/Stonecraft-template/blob/main/src/main/java/com/example/ExampleMod.java

[NikOverflow]

What about Stonecutter or Stonecraft (based on Stonecutter)? The main feature of Stonecutter is that it's possible to write code for all of the game versions in a single branch without duplication, and Stonecraft adds Architectury Loom on top of that for multiloader mods. For example see https://github.com/meza/Stonecraft-template/blob/main/src/main/java/com/example/ExampleMod.java

This is interesting. Thank you for sharing and I didn't heard about that. I will look into it if I have some time.

[NikOverflow]

I now have the idea how I do that and I will do it if I have more time.

[NikOverflow]

If I backported that mod to the 1.21 then I will close this issue.