MinecraftForge VS Mekanism

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.

Added support for creating chemicals via JsonThings

Cephylus is actually wrong. The transfer speed does stack in the same manner that the capacity does. I recommend checking it out in the official mekanism wiki. https://wiki.aidancbrady.com/wiki/Universal_Cable And this github issue which confirms it. https://github.com/mekanism/Mekanism/issues/3159

Yep, Mekanism uses it own registry for gases: https://github.com/mekanism/Mekanism/blob/1.19.x/src/main/java/mekanism/common/registries/MekanismGases.java

usually it's easier to go to a mod's repository if it's open sourced, then check src/main/resources or src/generated/resources for the recipes

I think that's only true in older versions. I tried to use omni direction hoppers to interact with it and it works from all side. Also Xnet can interact with it from all sides. This issue is marked completed https://github.com/mekanism/Mekanism/issues/3877 so it should be good.

I found something on the official Github here.

Either way this is an issue with the Mek pipes that is supposed to be fixed on 1.19.1/2 (https://github.com/mekanism/Mekanism/issues/6356)

We use some kotlin code to generate it, so if you can understand this then I'd welcome some contributions: https://github.com/mekanism/Mekanism/blob/patchouli/docs/PatchouliDSL.md