ChampionAsh5357

Use the installer to create the server, then run one of the `run` scripts (bat or sh depending on os). Nothing more to it.

You may want to update your Java 8 version to a new one, but otherwise: The version you are using is no longer supported on this forum. Please update to a modern version of Minecraft to receive support. Currently supported versions are 1.19.3 (Latest), 1.19.2, and 1.18.2 (LTS).

Please provide the debug.log from the logs folder in your game directory.

Seems to be an issue with nebs, try removing it.

Some client side mod is likely on the server since it is attempting to load a client-only class. You should take a look through your mod list and find any that are only client side.

Please provide the entire debug.log from the logs folder. This doesn't tell us much except that maybe it could be your drivers.

It means the mod needs a 1.19.3 version of Forge to load. You are currently playing on a 1.19.2 version of Forge

The version you are using is no longer supported on this forum. Please update to a modern version of Minecraft to receive support. Currently supported versions are 1.19.3 (Latest), 1.19.2, and 1.18.2 (LTS).

Well judging by this, it would seem that there is an access violation. If you repeat this process through a normal machine (and not PojavLauncher), does it work? If it does, then the error could be the launcher denying permission to perform the remapping.

Probably is then. If all the mods worked prior to the custom datapack being added, then there should be no issue. If it didn't, you could try removing stoneholm since it seems to be where the error is slightly originating from.

Unless they crash your game, probably not.

Please provide the log as a gist or a pastebin. Apologies, but we do not download files from the internet.

So the warnings applied are for mixins, configs, and commands. For the case of mixins, it seems like the class that it is applied to cannot be found. However, since the mixin is most likely marked as optional, it returns a warning in the game instead of erroring. The config warning is either because the config is not present. In that case, it just generates the config. For commands, it means when running the command, the argument being provided could be interpreted in many different ways. Though, it likely won't cause an effect on you if you are playing in a singleplayer world.

Is it a full crash, or does it just kick you out of the world? If it just kicks you out, what is the response it shows on the screen.? I don't necessarily see anything wrong with this.

So, when you say json, do you mean a normal structure or a jigsaw structure?

Since you're performing the rendering yourself in the method, it shouldn't draw to the screen if the method isn't being called. So, I'm unsure what the issue you are describing is.

Your file association is most likely incorrect. You can run Jarfix to fix this.

Seems to be an integration error between a minimap mod ad vault. Most likely the mod versions do not support each other. Otherwise, you'll most likely have to remove one or the other.

Please provide a pastebin or a gist with the debug.log instead.

What are you trying to do specifically? Additionally can you provide the entire log so that we can get the error in context?

Makes sense since there is no fix for OptiFine. OptiFine currently does not support Forge 1.19.3. However, that doesn't change the underlying issue that OptiFine is a mod which breaks almost any mod which tries to do any sort of custom rendering. A fix, as I mentioned, would be to use alternative mods rather than OptiFine. If you want to fix OptiFine, tell them to care more about mod compatibility. Apologies if my original explanation was not clear.

If that command is being run every tick, maybe, but that seems doubtful. You can try loading a new world and see if that is actually the case. If so, then you most likely need to find out what command you executed and see if there is a turn off switch for reporting.

Well, you may have Java 17 on your computer, but Java 19 is being used to run this jar. So, you either need to update the PATH environment variable such that it finds the Java 17 jar first or change the `java` to the exact executable in the correct version.

Most likely, one of these mods is causing the issue. So either, oculus, flyre_lib, or unionlib from what I'm reading.

You need to use Java 17, not Java 19.