caeruleusDraconis
commented
3 months ago Having to support Fabric and Forge at the same time is already a lot of work:
- dealing with the internal differences of fabric and forge, specifically:
- ensuring that world-preview directly or indirectly calls all the hooks of forge / fabric used by other mods for registering structures and biomes
- that forge requires custom thread pools for server side code
- validating that the mod behaves the same on both platforms
- building and publishing two versions of the mod
- etc.
Adding NeoForge support on top of that, would be a lot of work, especially if the projects more heavily diverge in the future. That doesn't mean it will never happen, it is more a "let's wait and see how the popularity of NeoForge develops before trying to support it".
offering a stable platform for your creativity to flourish
Neither Fabric nor Forge (or even Quilt and NeoForge) provide ready to use APIs for this mod. (The Fabric API is only a dependency so that translations work.) In fact, both Fabric and Forge are more of a nuisance, since World Preview "starts" a fake Minecraft """server""" for providing the preview in the Create World Screen. To achieve this, a lot of care has to trick both Fabric and Forge into cooperating and partially initializing other mods so that modded structures and biomes show up.
I highly doubt that any mod loader project would be willing to provide APIs for our specific use case.
I basically just want the mod loader to stay out of my way for this process as much as possible. Oh, and actually load the mod I guess :)
IsaacLiu2009
Feature Request
Embrace NeoForge for a revitalized Minecraft modding experience. It's a new generation of Forge that prioritizes collaboration and respect, offering a stable platform for your creativity to flourish.