-
Notifications
You must be signed in to change notification settings - Fork 49
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
Allow downloading "incompatible" versions of mods #407
Comments
This comment has been minimized.
This comment has been minimized.
Sorry, but whats the solution then? And this issue is not just github mods, it happens with modrinth and curse too. Why is the program deciding for the user whats best for them? Note that im not talking about the "add" function but the "upgrade" one, it will not upgrade when for example the minor release version is not exactly the same even when using --dont-check-game-version |
I'm sorry I misunderstood what you had originally written. Ferium right now pretty much expects that the mod author properly specifies what Minecraft versions and mod loaders the file works with. The ignore game versions flag currently just uses the latest file that's compatible with the mod loader, which doesn't provide much flexibility. A more robust solution for your problem is provided in #155.
Assuming I understood what you meant, that is exactly what the flag does. You specify the flag when adding the mod and it will store it in the config and remember that configuration when upgrading. |
The Problem
The program does not seem to allow you do download mods it deems to be incompatible despite the available versions working perfectly fine even if theyre 1 or 2 versions behind
Your Solution(s)
Please give us a bypass option that simply downloads the most recent release anyway and let us manually assess whether it crashes or not. I have a small mod list and can handle this myself
The text was updated successfully, but these errors were encountered: