Detect whether KSP was installed with Steam

[Majiir]

I'm not sure how to reliably detect this.

[blizzy78]

We could simply check if there is a SteamApps\common\ folder above the KSP folder. For example, my KSP Steam install (which I never use) lives at D:\Programme\Steam\SteamApps\common\Kerbal Space Program\

[Majiir]

This works for a lot of cases, but what if the user's installed Steam in a different library? (Steam allows for multiple game libraries so you can install on multiple HDDs.)

[blizzy78]

Does anyone ever use this?

[NeoXant]

Look to registry for key HKEY_CURRENT_USER\Software\Valve\Steam\Apps\220200 and check if Installed is 1

[blizzy78]

That doesn't prove KSP was started from Steam. I have a Steam and a store install on my computer - using this check it would always be Steam=true, but I never use the Steam install.

[NeoXant]

You can grab location of running KSP.exe process and check whether full path have SteamApps\common. Even if user installed KSP in custom library, then will always have SteamApps\common in path to process

[Majiir]

A running instance of KSP has the IsSteam flag, which indicates whether it was started from Steam. The question here is whether KSP was installed with Steam. If someone copies their KSP installation out of the Steam folder and launches it elsewhere, I consider that self-installation. If they run KSP directly but use Steam for updating the game, that's useful information for understanding how people tend to update.

[Majiir]

You can grab location of running KSP.exe process and check whether full path have SteamApps\common. Even if user installed KSP in custom library, then will always have SteamApps\common in path to process

This seems like a good solution. I'll add this in the next version.