warjort

Use java 17, mixin doesn't support java 19

Duplicate.

That log contains no error. But I do see you trying to rubidium (a client side only mod) on the server.

Conflict between iris and rubidium. Check you have the latest versions then contact the mod authors.

Problem with additionaladditions mod. Check you have the latest version the contact the mod author.

If you are using curseforge, you need to enable the forge debug.log in its settings. Otherwise, it's likely something you are doing when trying to change the log configuration is incorrect and you have broken the logging. Since you don't say what you have actually done, it's impossible to help further. Forge's debug logging is enabled by default, when launchers don't elect to turn it off.

One of your configuration files is invalid/corrupted. You can find it in saves/<save-name>/serverconfig If you don't have a backup of the file, you can delete it and it should be recreated with default values.

Like it says, you need to give the game more memory using the -Xmx parameter or whatever your launcher uses to configure the amount of heap memory.

You have mods with duplicate mod ids probably because they are different forks of the same project. Usually jei (just enough items) and rei (roughly enough items) or jade and wthit - both forks of waila.

https://github.com/sp614x/optifine/issues/7127

You are correct, it is a java question. You appear to be using an unsupported (in this forum) version of forge, I think 1.12? But then trying to use api that is from forge 1.19, e.g. import net.minecraftforge.fml.common.eventhandler.SubscribeEvent; // <-- 1.12 import net.minecraftforge.eventbus.api.SubscribeEvent; // <-- 1.19 RegisterEvent was introduced in 1.19

https://github.com/sp614x/optifine/issues/7127

This is a crash within the java virtual machine - jvm.dll. You should report it on the link it shows. Looks like it has a problem reading one of the jar files and didn't handle the error properly. You can try a different version of java, such as: https://adoptium.net/ It might at least give you a better error message about the problem?

Issue with the calio mod. Check you have the latest version, then contact the mod author.

Issue with flywheel. Check you have the latest version then contact the mod author.

Conflict between iris and oculus. Check you have the latest versions then contact the mod authors.

https://github.com/sp614x/optifine/issues/7136

You have mods that want a different (probably later) version of forge, try the latest version.

You are trying to use a 1.19 mod with minecraft 1.18.2 You're actual crash is with the tetra mod: Check you have the latest version then contact the mod author.

Looks like one of your mods has broken networking. The error message does not say which one. Probably the only way you will find it is to remove mods one-by-one until the problem goes away. If you are just starting with modded minecraft, I would suggest you use a prebuilt popular modpack that somebody else has tested They should have already removed all the bugs and incompatiblies. Otherwise you are going to spend a lot of time trying to do it yourself.

Upgrade your java. The version you are using has expired trust certificates.

Post a link to your logs/debug.log

Issue with the flywheel mod. Check you have the latest version then contact the mod author.

You know when you create a falling block the actual fall will be delayed to later processing? So, it could be you are setting the block to air, then on a later tick the block is failling and creating the source block. Setting the block to stone would likely stop the falling block from creating the source block? Probably it tries to spawn the ItemEntity drop for water which doesn't have one.

That effectively uses LiquidBlock.pickupBlock() - assuming you are dealing with a LiquidBlock? That calls setBlock() with flags = 11 while setBlockAndUpdate() calls setBlock() with flags = 3 Which means it is setting the "UPDATE_IMMEDIATE" flag as well - see the Block class. I don't know what difference that makes? It's not a flag I am familiar with.