MinecraftForge VS fabric

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.

This is a topic that was partially addressed during 2019 https://github.com/FabricMC/fabric/issues/463

Their reasoning is here

https://github.com/FabricMC/fabric/issues/1166 Here’s the reasoning behind the 81,000 number

What error message are you getting, theres someone who had a simmilar issue and it turned out it was due to a problem with spigot server side. https://github.com/FabricMC/fabric/issues/849

Fabric's Lead Developer as a Tyrant philosophy isn't necessarily bad; there are significant benefits to having a very unified vision and avoiding design by committee. But it necessarily limits throughput at that Tyrant, and in Fabric's case, that lead to a generally slow level of progress on a lot of important aspects, partly because people spent a lot of time in Discord talking about making a perfect Fluid API, or Config API, and never actually got around to making one, and partly because once they were made it'd spend the better part of a year with things sitting in PR or only as an issue. Forge had a similar problem back in the 1.6-1.7 days (until it finally just got in the habit of getting people sick of having to deal with dependencies and just merging in a best extant normal-person library), but Forge could get away with that when the alternative was vanilla. From a user's perspective, if you want a config system, or standardized (not-TechReborn) energy api, this matters.

FIX! I downloaded it using the same link using wget instead of curl, and it worked immediately. I have no clue why it worked with wget and not curl. Any further insight would be appreciated. Working command: wget https://github.com/FabricMC/fabric/releases/download/0.56.1%2B1.18.2/fabric-api-0.56.1+1.18.2.jar.

Since you develop the mod, you could probably set up a login network channel to send a small "I am installed" packet when a client logs in.

https://github.com/Wurst-Imperium/Wurst7/issues/625 https://github.com/FabricMC/fabric/issues/2145

Their identifier is fabric:textures/gui/creative_buttons.png. They can be found on GitHub.