Devilswarchild

there isn't one due to the fact I'm using the curseforge app. only logs I'll get are latest.log and crash reports.txt

currently attempting to hunt down the culprit the old fashioned way... by enabling the mods one at a time until I find the one that isnt playing nice with the others.

there is no launcher_log.txt being generated for curseforge instances that I can see unless the file is being generated somewhere else

There were 2 seperate logs there

ok Ive tried it both with and without h9 pre 3 and im still getting the error. I will post both logs so you can see. with and without optifine preview h9 pre

the version I have is HD_U_H7 which on the optifine website is listed for 1.18.2 which is the version of MC im using... should I downgrade it to H6? nvm you said preview release... Ill try the h9 pre3 and see what happens.

not sure what the issue is but I'll link the log here for anyone who can tell me why Im getting an exit code 1 latest.log

i have talked to the author and he says its working just fine but ill ask him again

I know the rules say it has to be current version of MC but i do have to say not all mods have been updated to current version of MC which is why some people still use 1.7.x. so my question is i would like someone to look over the logs of my forge-1.7.10-10.13.3.1408 server and see what is going on and what is causing it to load and just as suddenly close the server? latest fml server log: http://pastebin.com/Ep2LF8Nb