-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Crash]: Updated and immediately got an error #1787
Comments
I downloaded crash assistant separately and moved it to mods folder - same result...when I go back a version everything is fine |
The issue is wired... From where came 1.2.4? |
Hmm... The wired issue - the wired idea. But this shitty caching algorithm not only replaced jar in jar mod to prev version, as it won't cause this, but also corrupted something so here we go. Can you try to download mod directly from CurseForge web. Also please upload mod jar here. |
Also did the crash assistant GUI started? |
Can I have local/crash_assistant/logs/ latest.log |
updated ATM to 10-2.23, downloaded crash assistant 1.2.6 from curseforge, copied into mod folder - replacing 1.2.6 that was there from the update. Same error message - not valid jar file - yes crash assistant gui started - tried to add mod jar file to this message but got message "we don't support that file type" - however, when I went to grab the 1.2.6 file, i noticed that I had 1.2.4 in the mod folder, two different versions of crash assistant. I deleted the 1.2.4 file and reran mod pack - and was successful, no crash I hadn't realized 1.2.4 was in there but also I thought there was a process where if the two versions were present, only the more current version would be recognized. Lesson learned: check mod folder for differing mod versions Thank you for your time and help! |
Possible Fixes
Yes
Modpack Version
10-2.22
What happened?
Updated newest verision with crash assist and got an error when loading the game
Tried reinstalling - same result
Crash Log
https://gist.github.com/darrenh2/9729274e4256fc980e4b1d3e0566e8ac#file-latest10-2-22_crashlog
Latest.Log
No response
The text was updated successfully, but these errors were encountered: