AutoThirdPerson VS architectury-loom

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.

Hiya, just a quick post to mention that my mod that used to be a simple mod written in a couple days using 1 class for 1.12.2 is now a terrifyingly complex mod written over the period of a couple months using 50+ classes for Forge 1.4.7, Forge 1.7.10, Forge 1.12.2, Fabric 1.16.5, Forge 1.16.5, Fabric 1.17.1, Forge 1.17.1, Fabric 1.18.2, Forge 1.18.2, Fabric 1.19.2, Forge 1.19.2, Fabric 1.19.4, and Forge 1.19.4, and I ended up needing to write/maintain not one but two custom pieces of tooling to get everything working. But it's finally pretty much in a publishable state and I hope you enjoy it.

Auto Third Person is a highly configurable mod that puts the camera in third-person automatically when you perform certain actions, like entering a boat, swimming, or flying elytra: modrinth, curseforge, github

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.