AutoThirdPerson VS carvemelon

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

This means Fabric API's API surface is much smaller compared to Forge's, because you are expected to use Mixin to write your own shit when you need it, instead of relying on the loader or standard library to provide a wide surface of events. Almost every mod, including very simple ones, probably ships with at least a couple mixins. Any given Fabric mod is very likely to be "a coremod" in the Forge terminology.

Carved Melons adds a fruitier analog to the Carved Pumpkin. With a redstone torch, you can make a Melon o' Lantern, that acts like a one-sided redstone block: modrinth, curseforge, github