warjort

Read the deprecation comment on that method.

You need java 17 for minecraft 1.19

Issue with the better than llamas mod. Check you have the latest version then contact the mod author.

The chipped mod wants the ctm mod installed.

Change your max fps to be larger than 0, either in the options menu or the options.txt

You need to show the logs/debug.log so we can see the error. Or report it to the mod author if you know the mod having the problem.

Mojang changed how items are added to the creative mode screen in 1.19.3 This will require any mod that adds new items to be changed. It will affect most mods. So, make sure your mods say they are compatible with 1.19.3

minecraft 1.19.2 needs java 17

Did your mods say they are compatible with 1.19.3 when you downloaded them?

You are telling it to open the crafting table menu instead of your EggingTableGui? Since your block is not a crafting table block, it will close the gui in its stillValid() check.

Oculus issue: https://github.com/Asek3/Oculus/issues/243

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

The error does not really identify a mod. But it could be flywheel since that modifies the code in this area, or it could be a conflict with optifine? Check you have the latest version of flywheel and try without optifine.

Issue with jeed, check you have the latest version then contact the mod author.

One of your config files is invalid/corrupted. If you don't have a backup of the file, you can delete it and it should be recreated with default values.

You need to post your logs/debug.log so we can see the full error.

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.