warjort

Post a link to your logs/debug.log for help with minecraft forge. This forum is not curseforge: https://support.curseforge.com/en/support/home

Rubidium is a broken client side only mod that will crash your game when loaded on the server.

Use java 17

That run.bat still shows you using the run.bat from the environment PATH You had it correct before in an earlier post.

There's really no such thing. It's an artifact of the rendering. The player has a position, some rotation fields that say which direction it is pointing and its pose (e.g. if it is sleeping, swimming, etc.) If you want to see the exact calculation used during the rendering, look at the LivingEntityRenderer and PlayerRenderer, e.g. the code around setupAnim() and setupRotations() But you shouldn't base any real processing on that. Those values are just a "guesstimate" by each client. The server has the real authoritative values. For the server, the legs never swing.

The last line of the run.bat has the basic format java forge-configuration %* The part you need to change is the "java" to be the fully qualified path. You showed that before. The %* is any parameters you pass to run.bat like run.bat nogui Instead you seem to be passing the -C:Program, Files\etc for some reason. Which is why it breaks.

The only parameters you pass to the run.bat are the ones minecraft understands, like nogui Read the comments in the run.bat file. I'm not going to click on some random url. Post the files to a known file sharing site.

You must have a model per item, that's how its worked since I think 1.13? You can use datagen if you want to programmatically generate lots of models: https://forge.gemwire.uk/wiki/Datageneration https://forge.gemwire.uk/wiki/Datageneration/States_and_Models This code generates the "standard" item model with a texture the same name as the item, so instead just hard wire the texture to your common one. https://github.com/MinecraftForge/MinecraftForge/blob/c8f9e59fef4c52875601014c9fa18e41be619d0f/src/main/java/net/minecraftforge/client/model/generators/ItemModelProvider.java#L36 That's how Mojang does theirs, although they use a slightly more complicated "ModelTemplates" system, see the vanilla ItemModelGenerators.

Conflict between those 2 mods, check you have the latest versions then contact the mod author(s).

That's private. Read my footer for how to find the launcher_log.txt

Please don't post logs in the forum. https://forums.minecraftforge.net/topic/123416-exit-code-1/#comment-536369

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

Post a link to your launcher_log.txt from directly after the crash.

Broken client side only mod that crashes when installed on a server.

I doubt croptopia has anything to do with it. It's just what it was loading when it found the duplicate from the 2 imst mods.

I have underlined the mods likely causing this problem. Illuminations is the most likely. The logs/debug.log might have further information.

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.