Ugdhar

Unfortunately 1.16 is no longer supported on these forums. Currently supported versions are 1.18 and 1.19. More information here:

If the mod is open source, then it is completely fine, and likely one of the reasons the mod author made their mod open source to begin with. If you release a mod, perhaps include the authors of open source mods that have given you help/inspiration in your credits/thanks/readme.

It should be in C:/Users/azuzw/AppData/Roaming/.minecraft/logs

Your version of minecraft/forge is no longer supported. Currently supported versions are 1.18 and 1.19. You will need to update to receive support here.

Also, I do not believe you can use Optifine on a server, as it's a client performance mod, so if this is from your server, remove optifine from it.

Please post your debug.log, it contains information that isn't in the crashlog that might help figure out what your problem is. Also, using official launcher, or another one? The more info available, better chance of figuring it out

Both of those logs use Java 19

The jar installer will run on (mostly) any operating system, including Windows. Forge only works for the Java edition of Minecraft, so if you are playing the Java edition (even on Windows), then you can use forge/mods. If you are running the actual Minecraft Windows version, you cannot use forge, since that version is not written in Java. If the installer is failing to run, make sure you have Java installed, and if it still does not run, it's possible that your jar file association was hijacked by some other program, in which case you should be able to fix it by googling the jarfix program.

Which web browser are you using? I've seen people mention trying to use a browser other than google chrome. *EDIT: Actually, just ran into this post, check it out and give it a try:

This thread you posted in is totally unrelated, but I've seen people suggest downloading forge using a browser other than google chrome, as it seems to be having issues with the adfocus site

Considering that the log format of the official launcher is different, that is impossible. Please post the log from the official launcher.

I would give it a try with the official launcher, and post the debug.log if you still have troubles

That's not even a forge server, I don't think you'll be able to get much help here.

Whenever you make changes and still have issues, always post a new log from after the changes were made. It could be some other issue rearing its ugly head, or you may have missed something someone else will see.

Please post the full debug.log there may be other information in there that was omitted that could point to what's wrong. Also maybe a screenshot of your mods folder

I saw someone suggest using a browser other than google chrome to download forge, might be worth a try.

1.16 is no longer supported, supported versions are 1.18 and 1.19. More information can be found here:

I've never used any launcher besides the official one, so I am unfamiliar with tlauncher. I would suggest using the official launcher, it supports multiple profiles/versions of minecraft, so you can have multiple versions/modpacks etc.

Then you just have to wait until they release an updated version for a newer version of forge.

Please post your debug.log to confirm the actual error being recieved

If the server crashed, it may have corrupted the world (I had this happen before) and you might have to restore from a backup. You should post the debug log from the server, it should contain information that will help track down the issue, without having to use too much guesswork.

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.