With the fairly extensive changes coming to 1.22.0, I've ran into a problem where I have an old modlist (1.18 or so, don't remember) and a lot of my mods are now outdated and don't work on 1.22.0-rc.2. I feel like a very useful feature would be to have the mod manager list mods that are not explicitly marked as compatible with the version I'm trying to use.
To make this simpler, I'd propose two changes:
- An addition to the table that the
list verb returns, displaying the "For Game version" column as on the ModDB downloads page
- A flag for the
list verb, ie. list -v 1.22.0-rc.2 that somehow marks, perhaps by coloring the "for game version" field, mods where the selected version does not match the mod's requested versions.
This would allow the user to quickly scan their mod list and disable any mods that might be not working.
With the fairly extensive changes coming to 1.22.0, I've ran into a problem where I have an old modlist (1.18 or so, don't remember) and a lot of my mods are now outdated and don't work on 1.22.0-rc.2. I feel like a very useful feature would be to have the mod manager list mods that are not explicitly marked as compatible with the version I'm trying to use.
To make this simpler, I'd propose two changes:
listverb returns, displaying the "For Game version" column as on the ModDB downloads pagelistverb, ie.list -v 1.22.0-rc.2that somehow marks, perhaps by coloring the "for game version" field, mods where the selected version does not match the mod's requested versions.This would allow the user to quickly scan their mod list and disable any mods that might be not working.