You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there are non upgradeable mods found, the only way to upgrade to a newer version is either deleting the mod or having allowVersionFallback set to true, which is not always desirable (especially as long as it's a global setting)
What?
I think it would be great if there was a way to just --force a version change (with an additional confirmation "Yes, I know what I'm doing"?), so I can just easily bypass this without having to take mods out of the modlist and later re-adding them..
Any alternatives?
This would probably become obsolete by allowVersionFallback being per mod and/or test respecting the allowVersionFallback setting.
It would still be cool to have for other unexpected edge cases, I guess.
Anything else?
No response
The text was updated successfully, but these errors were encountered:
With the fix that went in the other day, this might also have been ... made better? ... the main source of the issues was the buggy/outright bad handling of the versionFallback mechanism. If you have time to test it with the new release, could you?
I'm fully on board with a --force, just trying to think of what it would do. If it doesn't do the verification of the versions, it would basically be a "remove all mods locally, change the version in the modlist.config and then attempt to install and see what happens"
I might still do it regardless but I'm curious if the fallback fix has helped with this situation
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I have checked for similar
Not a bug
Why?
If there are non upgradeable mods found, the only way to upgrade to a newer version is either deleting the mod or having allowVersionFallback set to true, which is not always desirable (especially as long as it's a global setting)
What?
I think it would be great if there was a way to just --force a version change (with an additional confirmation "Yes, I know what I'm doing"?), so I can just easily bypass this without having to take mods out of the modlist and later re-adding them..
Any alternatives?
This would probably become obsolete by allowVersionFallback being per mod and/or test respecting the allowVersionFallback setting.
It would still be cool to have for other unexpected edge cases, I guess.
Anything else?
No response
The text was updated successfully, but these errors were encountered: