apathy VS MultiLoader-Template

To expand this to multi-loader and multi-version - the way I've been doing it is to add a "core" subproject that doesn't have any external dependencies, then instead of having xplat and forge subprojects you have xplat-1.19.4 and forge-1.19.4 subprojects. Here's one of my mods using this technique, here's another.

That first one is still Beta for Forge. Check here for issues/updates/yada - https://github.com/quat1024/apathy

There is unfortunately no in-game config GUI but I tried to make the file as detailed as I could, and fill it with lots and lots of comments. There are some more details here.

The two main ways I know of are "Multiloader-Template style" and "using Architectury-Loom". Archloom is a big Gradle plugin that tries to do everything for you, multiloader-template is less of a software package and more of a code style. I'm not familiar with archloom but i've written a bunch of mods with the multiloader-template style.

This mod wouldn't be possible without Statement Library, which does all the heavy lifting (that said, it is required on both server and client). Also thanks to Jaredlll08 and Darkhax for creating Multiloader Template!

As a developer I want as many players to enjoy my work as possible, that's why I prefer both and have worked on tools to make it easier for developers to release for both.

Regardless of what you choose, If you do want to support both down the line there is a template by Darkhax, jaredlll08 and a few others which makes compiling for both easier by having a common source https://github.com/jaredlll08/MultiLoader-Template

It's the end of the world as we know it.

You can clone https://github.com/jaredlll08/MultiLoader-Template and see how it works, I know that ForgeGradle fixed a bug they had with multiproject configurations, but I'm not sure if any of the other problems are solved.