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
Scenario:
I am using CKAN on KSP, and there are mods for a prior version of KSP, but I know that they work with the current version. I am also willing to accept any negative impact and issues introduced to the client that those mods may have.
I would like to install older mods via CKAN, regardless of the version of KSP they are for.
A concrete examples include the various 1.0.x mods that are all compatible with 1.0.5, but not installable because CKAN detects they are not for 1.0.5, most notably Kerbal Engineer Redux.
Suggestion:
Give me an option in the CKAN Settings on the GUI, or a command line switch for the command line version, that will allow me to install any mod in the incompatible list.
A side effect from installing incompatible mods is that the GUI for the installed mod's entry should have it's background turn red while the text turns white to make the incompatible mod pop, so the user is very much aware that the mod is not compatible with the current version of KSP.
The entire point of this suggestion is to remove the headache introduced to the user when we get incremental updates that don't actually cause mods to become outdated, yet outdate wide swaths of mods. It's also to prevent the user from manually installing the mod, then having to deal with the headache that arises from CKAN wanting to install a newer version of the mod on top of an existing manual installation.
The text was updated successfully, but these errors were encountered:
While I'm tempted to generate a pull request that does this, I'm not sure if this functionality is in line with what the CKAN project is intended to do, as it does let the user bypass version restrictions.
On the other hand, by making incompatible mods stick out (especially if they are installed but not updated) it makes it easier for the user to find mods that are present when KSP updates (like a Steam KSP install that will update when a new version is pushed), and get the mod author to update their mod for the newer KSP version.
Scenario:
I am using CKAN on KSP, and there are mods for a prior version of KSP, but I know that they work with the current version. I am also willing to accept any negative impact and issues introduced to the client that those mods may have.
I would like to install older mods via CKAN, regardless of the version of KSP they are for.
A concrete examples include the various 1.0.x mods that are all compatible with 1.0.5, but not installable because CKAN detects they are not for 1.0.5, most notably Kerbal Engineer Redux.
Suggestion:
Give me an option in the CKAN Settings on the GUI, or a command line switch for the command line version, that will allow me to install any mod in the incompatible list.
A side effect from installing incompatible mods is that the GUI for the installed mod's entry should have it's background turn red while the text turns white to make the incompatible mod pop, so the user is very much aware that the mod is not compatible with the current version of KSP.
The entire point of this suggestion is to remove the headache introduced to the user when we get incremental updates that don't actually cause mods to become outdated, yet outdate wide swaths of mods. It's also to prevent the user from manually installing the mod, then having to deal with the headache that arises from CKAN wanting to install a newer version of the mod on top of an existing manual installation.
The text was updated successfully, but these errors were encountered: