Search the Community
Showing results for tags 'manual install'.
Found 1 result
-
.thumb.png.fa27a7f26ffbce41d23f5282560c243f.png)
I'm manually installing some mods after doing a fresh install of KSP and deleting every mod I had. My game was crashing a lot and I want this to be cleaner and I want to get more efficient with modding. So, right now, I am manually installing a mod and I am seeing that some files from that mod's GameData file already exist in my KSP GameData folder. For example, I was manually installing Ven's texture revamp and saw that it included Module Manager 2.7.2 while I already previously had MM 2.8 installed. I was told to not add the 2.7 because Ven's will work with 2.8 but KSP 1.3 won't like 2.7. Good advice. Now, I am installing USI MKS and am seeing that a lot files in the Mod GameData folder that I either already have or in some cases have a more complete set of. For example, USI MKS comes with the Firespitter plugins, but I already have the Firespitter file and it has a lot more than plugins, in it. Question is, is there a streamlined way of doing this or is that exactly the work that CKAN was made to alleviate? Is this a part of manually modding; going through these files individually? Because I'm not sure blindly moving over GameData folders and duplicating files are a stable way to play a game, not to mention, it leads to clutter which leads to the urge to clean install, sometimes. A more serious question would be, if i'm dealing with these duplicate files, how do you decide which to keep? My logic would say that if it's already been installed through CKAN, it's probably the newest version.... maybe.
.thumb.png.fa27a7f26ffbce41d23f5282560c243f.png)