-
Notifications
You must be signed in to change notification settings - Fork 43
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
Override compatibility check when adding mods #142
Labels
enhancement
Improvements to the project
Comments
For now, you can actually add all your regular mods (when selecting 1.18.2). Then when upgrading, all the mods that are compatible will still be downloaded even though there were incompatible mods. Edit: I misunderstood the issue, the above is a temporary workaround |
Added in 8fa2dc0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The problem
We're in between versions 1.18-1.19 of Minecraft and not all mods have been updated to 1.19 yet, so I have to write down all the mods that haven't been updated to 1.19 in a file somewhere to check on every now and then so I can add them to my 1.19 profile once they're updated. This is annoying af to keep track of.
My solutions
Have the ability to add version imcompatible mods into the profile (but give a message notifying this has happened) and check if they've been updated on
ferium upgrade
, then download if they're compatible. This would save a huge hassle of what I described above.Thank you to all the contributors <3
The text was updated successfully, but these errors were encountered: