-
Notifications
You must be signed in to change notification settings - Fork 25
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
[Mac OS] 1.12.2 modpacks wont start #1173
Comments
*ps. I think the both modpacks have same contents of crash-report, but I can't understands that report, (why the crash occured) |
*ps. I found out the cause through multiple searches. The reason is that it was recognized that there was no NaratorOSX Java classpath. However, the .jar file on the I think it's less likely that the file was damaged because I reinstalled it muliple times. I think Java doesn't seem to recognize that classpath. But I have a lot of difficulty solving that problem on my own because I don't know java very well. |
It looks like the recent update may have introduced this issue. So far I have not found a solution to this. |
This issue should be resolved now with the update that was released for the app today. |
This issue is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 3 days. |
This issue has been closed as there has been no recent activity after being marked as stale. |
What Operating System
MacOS (Latest)
Debug Code
FTB-DBGIPOPEHOPOK
Describe the bug
After Modloading It it has crash all modpack
Crash-Reports
FTB present Stoneblock2
crash-2024-07-23_11.54.31-client.txt
FTB presentDirewolf 20 1.12
crash-2024-07-23_12.06.19-client.txt
Steps to reproduce
Deleted App and all folder ex. .ftb
Re-Installed all (app, modpacks, Java)
But nothing has repaired
Expected behaviour
I just want start the game
Screenshots
Additional information
M2 MacbookAir / MacOs Sonoma 14.5
Before the bug I didn't modified any files and update Os, Java, App, Modpacks
It worked Last sunday
The text was updated successfully, but these errors were encountered: