Ugdhar

Step 1: Remove all mods that have the word fabric in them Step 2: If it continues to crash, search each mod on curseforge, and see if you have a fabric version of it that does not contain fabric in the name, delete that mod. Step 3: Profit!

Only 1.18 and 1.19 are supported here, you will need to update as 1.16 is no longer supported

I'm so confused.

I use tmux myself, but I just tried it using screen, and after detaching from the screen session and logging out of my SSH session, then relogging in, my process was still running and I was able to attach to it and it was still doing its thing. Maybe it's your terminal software? I was using Putty.

If you're a beginner with Java, you're going to have a really hard and probably bad time trying to mod Minecraft. My advice is to learn at least basic Java, then come back to this. Although to be honest, you should probably learn more than just basic Java, basic Java is not enough for some of the code used in Minecraft/Forge. Did you look at the Examplemod that came with the MDK? It shows how to register a DeferredRegister, plus there's not a ton of code in it to weed through to find it, it's a single class.

DeferredRegisters need to be registered, if you look at the examplemod that comes with the MDK, it registers item and block deferred registers. I believe they do it in the mod class constructor.

Only 1.18 and 1.19 are supported on these forums. Asking for help with old versions will get your thread locked. It shouldn't open a new window when you download supported versions. Are you making sure you're clicking the "Skip" button in the top right? Otherwise, you may be infected with a virus or malware or some sort of browser issue.

I don't just hang around here waiting for replies, I do other stuff and just come back once in a while. If you want immediate attention, you should join the forge discord. That log does not show a crash, are you sure it is complete and/or that it is the debug.log? And as far as it saying you have Windows 10 when you have 11, I don't have an answer for that one, unless you don't have Windows 11 like you thought?

How are you guys downloading forge? Where from? I just clicked the installer for the latest version, waited for the countdown on the ad page, then clicked Skip, and it downloaded fine for me.

Post the debug.log from the logs folder of your minecraft installation, it might provide some useful information

1.12 is no longer supported, support is only provided for 1.18 and 1.19 currently.

You probably will need to redownload, just make sure you are downloading mods from an appropriate source, do not just google for them. curseforge is probably the primary place for getting mods, just avoid sites with numbers in their names (i.e. minecraft1), and when it doubt check the mod repost list https://stopmodreposts.org/

Side note, I do believe 1.19 requires Java 17, so don't just update your Java 8 to a newer Java 8, you need Java 17

You need to post logs and/or provide more information. There are approximately 1,467,321,236,245 potential problems you could be having, so we need something to narrow down the possibilities

I'd go with tmux or screen for running a terminal you can detach from. https://www.howtogeek.com/671422/how-to-use-tmux-on-linux-and-why-its-better-than-screen/

1.12 is no longer supported, you will need to update to receive support. Information on supported versions can be found here, or at the blue bar link at the top of the forum pages:

There's either a server already running, or something else running on the MC port.

I would wager a problem with rubidium, does it have a newer version maybe?

Nope, that's the changelog

It should be in the same folder as the installer, same name I believe but .log extension.

Unfortunately, 1.12 is no longer supported. More information on supported versions can be found here:

Please post your full debug.log it will have more information in it.

Please post the debug.log it will have more information in it than the crashlog.

Is that the full log? It looks like it ends early, not seeing a crash at the end like before.

Always post new logs if you make a change, and it is still broken. This will both ensure the removed mod is indeed removed, as well as provide information for why it continues to crash.