MultiLoader-Template VS MinecraftForge

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.

Squirrel: https://github.com/MinecraftForge/MinecraftForge/blob/1.20.x/fmlearlydisplay/src/main/resources/squirrel.png

I found this. Give it a good read. It's kind of old but there might be some kind of help in there. https://github.com/MinecraftForge/MinecraftForge/issues/7558

it crashed bcz of Error java.lang.reflect.InvocationTargetException, probably mods. Also there is Duplicate key exeption, i dont know what caused it - there is a guys on github which had the same issue, try asking for their help: https://github.com/MinecraftForge/MinecraftForge/issues/5556

Does this happen in newly created worlds? Forge had an issue that was patched that caused the removal of dimension mods to break worlds. However it should be working in forge post v43.1.

I looked in LivingEntity and it looked to me like water movement physics are still hardcoded to affect all non-lava fluids in the travel function. https://github.com/MinecraftForge/MinecraftForge/issues/8608 is listed in the fluid API commit as the go-to source for info and it mentions a "fluid motion" setting but I don't see it. I get the feeling the documentation is outdated but that's literally the only documentation I can find anywhere about this api. Very frustrating.

According to this PR, it's been fixed but it's still present in 43.2.2.