warjort

Read the other thread and its related links. The crash at that point in the log is usually the buggy AMD driver that has been randomly crashing minecraft for at least the last 10 years. You can confirm this for yourself by searching for "problematic frame" in your launcher_log.txt or upload it to a file sharing and we can confirm it. The fix that works for most people is to either reinstall the latest driver or try a previous version of the driver until you find one that doesn't crash the game. If all that fails, contact AMD or customer support for whoever sells your PC, to get help for your graphics card configuration.

1.19 has such an event https://github.com/MinecraftForge/MinecraftForge/blob/9a25527a54011378c1a1e6b3b6dd0e90bd52fafb/src/main/java/net/minecraftforge/client/event/ScreenEvent.java#L1037 For 1.18, I guess you will need to trap the ESC key using one of the other events in that class.

Your maxFps is wrong in your options.txt If that's not it, https://forums.minecraftforge.net/topic/123416-exit-code-1/#comment-536369

No, that data is not updated to the client by vanilla.

There is no way to listen to those packets/events as far as I can see. Maybe you can submit a patch to MinecraftForge? But it's also not the only place that spawns heart particles, see for example Animal.aiStep() You could add a listener to LivingTickEvent and check Animal.isInLove() - but that data is only available on the server. If you want it on the client you would need to send/broadcast your own packet.

Check you have the latest version then contact the mod author.

https://forge.gemwire.uk/wiki/Sides physical = which computer (really process on that computer) logical = what portion of the code actually runs in that process The only multiplayer environment where that is possible is "open to lan" for the person that shares their game. The logical client is a subset of the physical client. The logical client is just minecraft without the server code. The server code is still always present, its just not used on the client except in single player (or open to lan).

What you have posted is very incomplete. You need to post the logs/debug.log so we can see the debug messages and since this is likely a mod network problem, you should add the following to client and server jvm arguments -Dforge.logging.mojang.level=debug that will let us see Mojang's network logging. You add it in the same place you specify the -Xmx memory value. There is no error in the server log. There are some warnings saying spark is timing out waiting for its statistics. The only other message related to a mod is: but that is not an error. The client log has the following warnings: some of those are not client side only mods. If you really do think the server is "freezing". You need to get a thread dump during the freeze so we can see where it is stuck. https://www.baeldung.com/java-thread-dump If the full logging does not show any additional error information, it is likely the only way you will find the problem mod is by experimenting with removing mods in a test world until you find removing which mod that makes the problem go away. Since this is mopack, you should contact the mod pack authors to see if they have seen this problem before.

Check you have the latest version then contact the mod author.

Please don't post on other people's threads unless you are helping the original poster. And if you don't show all relevant code to reproduce your problem (preferably on github) we can't help. We have no psychic powers. But maybe you want to look at CompassItem.inventoryTick() and its use of isClientSide ? Don't try to continue the conversation here, start your own thread.

Note: This is not the part you added to the beginning of the last line of the run.bat That does not contain a , after Program or a - You need to find where you are passing this.

Can you please stop posting files in the forums and upload them to a file sharing site. That error message says you are passing the java location as a parameter to minecraft. i.e. in the "%*" part of the run.bat You need to explain how you are running the run.bat, i.e. what parameters you are passing to it. And upload your full modified run.bat and user_jvm_args.txt to a file sharing site.

Check you have the latest versions of these mods then contact the mod authors.

Post a link to the logs/debug.log

If that's not it, you need somebody who can help you understand why the server can't bind to the ip address on that port.

https://forums.minecraftforge.net/topic/123572-server-wont-launch-all-the-mods-8-error-message-below/?do=findComment&comment=537079 And we can't help you if you don't post the log when using java 17 - "it does not work" is not a useful bug report.

pirated launchers are not supported here.

Post a link to your logs/debug.log But this doesn't sound like a Forge/Minecraft issue. It sounds like the server can't bind to that ip address for some reason, this is a networking issue. You should contact Hamachi.

The issue is the contents of the files not the names. And that the logs are for different times, so not the same login attempt. Only the launcher_log.txt shows the client connecting to the server and that log never shows debug information. But I don't think the debug.log will give any new information in this case. It looks like one of your mods is just *silently* breaking the network buffer. curseforge lets you download "server packs" if the mod pack author uploaded one but it doesn't let you create or run them.

Post a link to your launcher_log.txt from directly after the crash - see my footer for how to find it with curseforge. Don't post logs in the forum, use a file sharing site.

Use java 17

That is a mod for minecraft 1.19.2, you have 1.19.4

Use the correct version of optifine for your version of forge - see their download page.

That error says one of your jars is corrupt/incomplete. It does not say which one. Try running the following command on each mod jar jar -tf mod.jar That should list the contents of the jar if it is ok or give you the same error if it is broken. "unzip -t" can also be used to test the contents of a zip/jar. Failing that, maybe it is an issue with your native library, like this issue from about a year ago? https://github.com/madler/zlib/issues/613

https://forums.minecraftforge.net/topic/123416-exit-code-1/#comment-536369