-
Notifications
You must be signed in to change notification settings - Fork 24
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
incompatibility with lithium's latest neoforge version for 1.21.1 #174
Comments
See #173: This is fixed in the dev build from this GH action run: https://github.com/malte0811/FerriteCore/actions/runs/11371242578 (the previous run did not upload artifacts due to a build script bug). Given that Lithium on Neo is only available from GH action builds too, I do not consider it important enough to create a new release for it. 1.21.2 seems to be close to a release, the "fix" will be included in the FC build for that. |
Yeah but I won't use 1.21.2 for my modpack? It should be back ported tho :C |
If they actually release Lithium on Neo on 21.1 I'll look into making a new release. But the only statement I got from them so far was along the lines of "we don't know yet, maybe we'll do backports". Also, you can easily apply the "fix" yourself in a pack since it's just an option in the Lithium config. |
bro they just did 😭 |
uh, where? also i cant even launch minecraft, so how can i edit that, i think u mean from config folder? |
I was not aware that they had released one 4 days after telling me that they weren't sure yet whether they would. So I assumed that you were one of the people testing their GH builds. I will try to get a build out tomorrow after I get back from work. You can ask the lithium team about instructions for the config, but GH issues are not for "chat-style" one-message-per-5-seconds conversations. |
I did not get around to it the last two days (quite busy at work), but I've put the build on CF/MR now. CF still needs to be approved, MR should already be visible. |
alright |
https://mclo.gs/2MyYH4B
The text was updated successfully, but these errors were encountered: