![]() Things like Module Manager and Community Resource Pack were things that I used to miss before CKAN.Are you quitting the game just because you end up living? Well, you don't need to leave your favorite game for unwanted reasons. Putting a folder into another folder certainly isn't hard, nor is clicking on a check box in a list The main benefit of CKAN I see is that it finds required mods and installs them too. I only mentioned CKAN because nobody else did. It is up to other community members to provide better info to newcomers to avoid any type of flame wars in future. Without enough info, they can't figure out where they have made a mistake with manual install, neither they are capable to supervise automatic tools like CKAN. Point is that ordinary, especialy new users are not informed enough how mods works in KSP. I will let that to anyone to choose method that suits their needs. I'm neither promote manual or CKAN install method. Have to be fair and say that CKAN staff members do their best, and bad metadata that cause faulty install is solved almost soon as discovered. Other 5% falls into that mentioned faulty install. That will solve 95% of faulty install issues. Then install everything again trough previously exported *. Uninstall everything end check out gamedata folder by yourself to wipe out any other files except SQUAD folder. Whenever you encounter frequent (de)install of various mods, it is good to export your installed mods in *. Uninstall issue with CKAN can be solved more/less easy. You end up again with faulty mod install. To make things slightly worse, CKAN can also create faulty uninstall, due to policy that it should not wipe out any file created inside mod folder that was not existed at the moment of install.ĭue to fact how MM works, that it consider some mod as installed by only checking if some folder exist inside gamedata, without checking actual content inside that mod folder, it apply some MM paches on parts that should not be aplied. Automatic metadata creator or CKAN boot crawler can make a mistake and create bad metadata, as well as humans who do that manualy. ![]() Probably will be repeated in various random threads too.Īs tool for automatic install, CKAN can make mistakes too. Here is full thread page of example of faulty manual install, following this post. And you end up again with faulty install. Most of the times they pack last version of it. Other moders pack his own stuff and any dependency mod that they have used together in one archive. If you miss that info and only unpack his stuff you end up with broken mod install. Some pack only his own stuff and inform you somewhere that you also need some dependency. You need to understand first how various moder pack his stuff in archive. It is also true that you first need to understand what is ziped archive and what ordinary folder. Anyone is welcome to counter-point, but I'm done, so please lets not turn this into a CKAN shouting match or flame war.Īs any tool, you need to learn how to properly use it. THIS has been MY biggest issue with CKAN.Īnd, PLEASE, I stated my opinion on CKAN vs a simple manual install AS FAR AS BEGINNING USERS go. If you understand basic folder structure, and how to extract archive files (.zips/.rars), its like a 15 min learning curve and you are done. Its SOOOO simple and easy to learn how to do a manual install. CKAN may be a great tool, HOWEVER, as illustrated in the latest CKAN situation, its not really good advice to suggest CKAN as an alternative to understanding basic manual mod installation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |