Modpack crashes on startup (solved)

[UwUsername]

I have been using the Twitch mod loader for a while and have been building off of the Tinkers modpack. I have added quite a few mods and been running them on a server with a friend just fine however last night I added some more mods and since then my minecraft crashes immediately but the server loads just fine I am using Forge version 14.23.5.2784 and I have about 8GB of ram set.

 

Crash log here

 

Any help would be awesome I normally can figure this out myself but today I am really struggling.

 

EDIT: I fixed the problem by manually checking each mod 1 by 1 to see where the problem was thank you to everyone who tried to help.

Edited June 27, 2019 by UwUsername

[DavidM]

Remove Optifine and try again.

[UwUsername]

  On 6/27/2019 at 1:50 AM, DavidM said:

Remove Optifine and try again.

Expand  

Removed it and it still crashed log here

[Ruchia]

Make sure the client mods match the servers and that the clients configs match the server's.
Also, post the debug.log, it can tell us more. ( > logs/debug.log)

[UwUsername]

  On 6/27/2019 at 1:59 AM, Ruchia said:

Make sure the client mods match the servers and that the clients configs match the server's.
Also, post the debug.log, it can tell us more. ( > logs/debug.log)

Expand  

I can't get the client to even open that's the problem and I don't see a debug.log in the logs folder.

[Ruchia]

It maybe inside that latest log.gz
I guess this is something the twitch launcher does sometimes. (edit: or maybe some mod. I honestly don't know, but I have seen it before.)
(if it contains DEBUG and TRACE entries, it's the debug log.)

edit: If they are not there, you could try adding the JVM arguments: -Ddeployment.trace=true -Ddeployment.log=true -Ddeployment.trace.level=all

Edited June 27, 2019 by Ruchia
tip?

[DaemonUmbra]

Twitch overrides Forge's logging configurations resulting in no debug.log being generated, try this:

 

[UwUsername]

  On 6/27/2019 at 2:07 AM, Ruchia said:

It maybe inside that latest log.gz
I guess this is something the twitch launcher does sometimes. (edit: or maybe some mod. I honestly don't know, but I have seen it before.)
(if it contains DEBUG and TRACE entries, it's the debug log.)

edit: If they are not there, you could try adding the JVM arguments: -Ddeployment.trace=true -Ddeployment.log=true -Ddeployment.trace.level=all

Expand  

Unfortunately neither are any different from the last log I linked even after updating the JVM argument.

[UwUsername]

  On 6/27/2019 at 2:21 AM, DaemonUmbra said:

Twitch overrides Forge's logging configurations resulting in no debug.log being generated, try this:

 

Expand  

I fixed it by going back and checking all of the mods I last installed one by one thanks for your help.

Edited June 27, 2019 by UwUsername

[UwUsername]

  On 6/27/2019 at 1:50 AM, DavidM said:

Remove Optifine and try again.

Expand  

I fixed it by going back and checking all of the mods I last installed one by one thanks for your help though.

  On 6/27/2019 at 2:07 AM, Ruchia said:

It maybe inside that latest log.gz
I guess this is something the twitch launcher does sometimes. (edit: or maybe some mod. I honestly don't know, but I have seen it before.)
(if it contains DEBUG and TRACE entries, it's the debug log.)

edit: If they are not there, you could try adding the JVM arguments: -Ddeployment.trace=true -Ddeployment.log=true -Ddeployment.trace.level=all

Expand  

I fixed it by going back and checking all of the mods I last installed one by one thanks for your help.

Edited June 27, 2019 by UwUsername

[UwUsername]

  On 6/27/2019 at 1:50 AM, DavidM said:

Remove Optifine and try again.

Expand  

I fixed it by going back and checking all of the mods I last installed one by one thanks for your help.