-
Notifications
You must be signed in to change notification settings - Fork 80
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
Error: java.lang.IllegalStateException: Mod 'architectury' is not available! #130
Comments
This has been an issue for a long time |
Given the age of the issue, unlikely to see a resolution. I will keep this one open to direct other duplicates to |
I found that OmegaConfig is built into mostructures-neoforge-1.5.0+1.21.jar. Disabling it will allow you to enter the game normally, and this person's method is also effective. |
@BeholdIsLost can you upload your latest.log too please |
ok so i've been fighting this all day, i was trying on 2.32 as well, but decided to downgrade to 2.29 and keep going until i found a version that worked (if any), but now i've decided to just add logs from each version i try (i was angry an 2.32 so i deleted the instance, and made a new one on 2.29, so there are the logs for 2.29, ill make a new instance on the new version to grab the logs from there, ill edit this comment with more versions, as to not spam the thread. so keep an eye out 2.29 logs 2.32 logs |
@9thyear2 Your issue seems to be a Linux configuration problem. See here: guard/rb-inotify#23 (comment) for a possible solution.
|
Latest.log https://gist.github.com/BeholdIsLost/36af020014fec6f3edb40bce9086c3dd |
running this in the terminal fixed it on 2.32
i don't know why this made an effect on a modpack but maybe an issue should be filed with prism launcher to detect if the value need to be modified before running a certain modpacks, cause i've never seen this till today EDIT: a warning would be alot better than just an outright crash |
Possible Fixes
Yes
Modpack Version
10-.017 latest
What happened?
The laste 3 updates, i have the same crash error
Crash Log
https://gist.github.com/Jocky69/de24213405501dbb2cc79506f1cab61b
Latest.Log
No response
The text was updated successfully, but these errors were encountered: