warjort

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

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

Issue with ineedblock mod. Check you have the latest version then contac the mod author.

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

When I said I was using that as an example. You need to post all new information. For example, here you changed the build.gradle, but you haven't shown what you changed. The error above suggests you have no maven repositories defined, or they are misconfigued in some way. I suggest if you don't know what you are doing, you download the MDK, confirm it works and then change it your needs. Otherwise this thread is going to be very long while we painfully try to get every bit of important information from you about you have done.

Issue with computercraft (cc-tweaked) mod. From the error, it looks like the version you have is for an early beta release of 1.19?

https://github.com/sp614x/optifine/issues/7127 Install the latest optifine preview release.

hmmmm

That does not show an error. It's also not the logs/debug.log If that really is the full log, post a link to your launcher_log.txt (and do it before restarting the launcher). From where it crashes, it looks like you have a mod that failed to apply a mixin to a main minecraft class. Probably because the mod is not compatible with 1.19.2 or it conflicts with another mod.

That's impossible. How can you get an error about parchment, if you are not using parchment? And people that just say "it does not work", overestimate our psychic powers. Post a link to the log showing the error.

"That's not how the force works!". The source code you are looking at, is a decompiled/deobfuscated version of the minecraft code. It is there for reference only. Modifying your local copy of this is not going to change how other people's minecraft works. If you want to modify that code for real, get a job with Mojang. 🙂 To modify attributes of entities you didn't write, you need to apply AttributeModifiers to them. To apply them to entities as they spawn, you can use the EntityJoinLevelEvent. See for example, Mob.finalizeSpawn() for how to apply an attribute modifier to a living entity.

I don't know then. All the information we have is that you have something taking too long on the server thread. And the one crash report you posted showed it was doing something in applied energistics. Without new information, I suggest you contact the authors of that mod.

That is the server tick timeout error. It can't be a crash after 3 seconds.

This is not the mixin support forum. I believe there is a 3rd party modding channel on forge's discord where you might get help as well?

You originally reported the 60 second timeout on the server thread crash. If it crashes after 3 seconds you have some other error. But you don't post a link to the logs/debug.log to show what that is.

This usually means one of your forge configuration files is invalid/corrupted. You can find them in the config folder. e.g. config/fml.toml If you don't have a backup of these files, you can delete them and they should be recreated with default values.

You have mods that are not compatible with 1.19.3

Same error and answer as an hour ago. i.e. You need to use the latest preview version of optifine if you have any mods that bake their own models.

The correct one is the debug.log with no other ending.

I'm not going to look at it, unless you post the logs/debug.log so we can all the information. The first thing the debug.log shows is all the mods you have installed.

It's not installed according to forge. Maybe you have the issue where the mod was downloaded with the file .jar.zip file ending? Mods need to have .jar as the ending. In fact, there is an alternate error that says you have 3 mods missing.

Since it looks like you have the spark mod installed did you try looking at its analysis of what is using time on the server thread?

You have something taking too long on the server thread. When the 60 second timeout happened it was doing something with applied energistics.

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