Do you copy the 'GameData' folder of mods to the root of KSP, or do you copy the contents of the GameData folder to KSP's GameData?

[The Dressian Exploder]

I wasn't even aware people did it differently, but apparently some of you guys copy a mod's GameData folder to Kerbal Space Program.

 

I copy the contents of the mod's GameData to KSP's GameData folder

 

So, which one do you do?

may or may not have made the longest title on a thread on this forum...

[Superfluous J]

Folder into gamedata.

Mostly because some mods don't have a gamedata folder in their zip.

[RealKerbal3x]

I just copy everything in the mod's GameData folder to the main GameData.

[goldenpsp]

1 hour ago, The Dressian Exploder said:

I wasn't even aware people did it differently, but apparently some of you guys copy a mod's GameData folder to Kerbal Space Program.

If they are, they are doing it wrong.

while DLL's are not location specific, parts and such rely on the proper path to function properly.  So having a situation of nested gamedata folders such as gamedata\gamedata will break stuff.

Also renaming mod folder names will break stuff.

[Stone Blue]

I drag/drop contents, inside /GameData. i dont even unzip

That way I dont get the annoying Windows "merge" warning and I can also *see* exactly what I'm installing, cuz I dont usually install pacaged dependecies...I grab and install those seperately

Edited December 31, 2020 by Stone Blue

[jimmymcgoochie]

If I was installing a mod manually, I’d take the contents of the mod’s GameData folder and bung it into KSP’s GameData folder, or if there wasn’t a GameData folder inside the mod then I’d grab the folder with the parts etc. folders inside it and put that into KSP’s GameData.

But really I’d use CKAN and let that do the folder faffery instead.

[CobaltWolf]

What's the difference?