[BUG] Bug with my large modpack since "NotEnoughItems-2.3.48-GTNH"
quentin452 opened this issue · 30 comments
Can be fixed by downgrading NEI to NotEnoughItems-2.3.47-GTNH
Crash when try to join second time a world(ON SERVER) :
crash-2023-05-10_19.27.30-client.txt
the modpack :
https://legacy.curseforge.com/minecraft/modpacks/biggess-pack-cat-edition/files/4521827
Thank you, that was very helpful. I think I have a fix. Can you please try the following jar (within the zip file) and let me know if it fixes the crash?
i maked alot of test(like 4 or 5 hours) , and every time i make a new test , it seem that not same mods are suspects , so i think its a bug in NEI
This is a hardpass to support, that pile up of mods has some invasive mods, mods which purposefully don't work with gtnh codebase and a lot of conflicting and poorly written mods.
Do some diligence and find which mod causes conflict at least. Better if you can point at which change between NEI 47 and 48 caused that to conflict.
Use that special given version, it was modified to provide more debug information on the crash form nei side. Its not the same as normal . 51
I've tested the changes from 2.3.48 with GTNH and didn't hit that. Your modpack has 800 mods, which sounds crazy to me.
I need a bit of cooperation from your side to be able to narrow this down. Can please try out the following build of NEI 2.3.51, which includes a couple of additional log statement?
NotEnoughItems-2.3.51-GTNH.bigpack.crash.debug.zip
Please try to replicate the crash and upload the full client log.
This will not be helpful. Again, the jar I've linked to above has a couple of additional log messages, that might help me narrow this down.
Also, I need the full client log not just the crash log. The crash log does not have all the information I need.
You have to manually replace the jar file locally in your instance's mods folder. (no changes necessary on the server)
Here is the crash report + logs with the debug
wait , its seem that fixed it , i crashed and i tried to rejoin the server and seem to be work. so idk
edit : i think it save in memory the last config reload from the previous crash with the 2.3.51-debug, i tried to remaking a server world and it seem that don't crash anymore.thx
Hmm, that doesn't give me a lot of confidence. Can you maybe try booting the server and client fresh again? Make sure you have the latest jar that I've posted above installed in your client instance (....bigpack.fix-1.jar
). Then connect to the server once and then a second time.
If it crashes on the first connect, please post the crash log here anyway, It may not be related to this bug report, but I still want to make sure that it isn't related to some other issue in NEI... With 800 mods, you can expect things to be weird.
i have the .bigpack.fix-1.jar in both
1 : i relanched both
2 : first time joining server world , all is okay
3 : second time joining server world , all is okay
4 : some time joining server world , all is okay
to make sure that isn't chance , i will relaunch again server and client
Test 2 :
i have the .bigpack.fix-1.jar in both
1 : i relanched both
2 : first time joining server world , all is okay
3 : second time joining server world , crash :
crash-2023-05-10_22.13.26-client.txt
fml-client-latest.log
4 : some time joining server world , all is okay
So its better than before , like just one crash , not all time crash when try to join server world , it's really less anoying
Thanks. OK, so it's still the same issue. Can you please upload the full client log?
EDIT: Thank you.
OK, here is my second attempt at a fix. Please try!
So i relaunched three times client and server and maked test , and it seem that crash is fixed.Thx.