FarPlaneTwo VS MinecraftForge

I also know that FarPlaneTwo is supposed to do something similar, but I'm sure I didn't test that.

for 1.12.2 there exists https://github.com/PorkStudios/FarPlaneTwo

Far Plane 2 https://github.com/PorkStudios/FarPlaneTwo/tree/dev/voxel-mode-is-no-longer-restricted-to-rendering-voxels

FarPlaneTwo

Pretty much, trying to find a mod like Bobby or FarPlaneTwo, but for 1.18. Neither of those are compatible with 1.18 so does anyone know anything similar to those? Thanks!

I've found that chunk render distance has a very large impact on fps. If you play on 1.18, setting the simulation distance down allows you to play at 32 render distance fine. If you play earlier versions, mods like Distant Horizons, Bobby, C2ME, or FarPlaneTwo are quite useful.

https://github.com/PorkStudios/FarPlaneTwo have fun

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.