Skip to content
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

Closed
darrenh2 opened this issue Jan 11, 2025 · 7 comments
Closed

[Crash]: Updated and immediately got an error #1787

darrenh2 opened this issue Jan 11, 2025 · 7 comments
Labels
Crash Game crash

Comments

@darrenh2
Copy link

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
Screenshot 2025-01-10 194810

Crash Log

https://gist.github.com/darrenh2/9729274e4256fc980e4b1d3e0566e8ac#file-latest10-2-22_crashlog

Latest.Log

No response

@darrenh2 darrenh2 added the Crash Game crash label Jan 11, 2025
@PiggyWhiskey
Copy link

PiggyWhiskey commented Jan 11, 2025

Seems like Crash Assistant hasn't downloaded properly
image

Check the file, and make sure it's the correct size, perhaps delete the mods folder and re-install the modpack to ensure you get the right files

@darrenh2
Copy link
Author

I downloaded crash assistant separately and moved it to mods folder - same result...when I go back a version everything is fine

@KostromDan
Copy link

KostromDan commented Jan 12, 2025

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...
Modlist printed by neoforge prints: Crash Assistant 1.2.4 (crash_assistant) while your install and modpack has 1.2.6.

From where came 1.2.4?
Since mods doesn't contain 1.2.4 jar...
Mystic.

@KostromDan
Copy link

KostromDan commented Jan 12, 2025

Hmm... The wired issue - the wired idea.
The jar in jar mod which is loaded from coremod haven't got version in name.
So maybe some service cached from prev version jar in jar file and now distributes mod called 1.2.6 but containing in jar in jar 1.2.4 cached version...

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.

@KostromDan
Copy link

KostromDan commented Jan 12, 2025

Also did the crash assistant GUI started?

@KostromDan
Copy link

Can I have local/crash_assistant/logs/ latest.log

@darrenh2
Copy link
Author

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Crash Game crash
Projects
None yet
Development

No branches or pull requests

4 participants