A fellow KSP player posted an interesting bug report on the KSP forums this weekend (September 24). The bug report was titled “KSP2 is Spamming the Windows Registry Over Weeks/Months Until the Game Will Stop Working Permanently”. According to the report, something is misconfigured and KSP2 is flooding the Windows registry every time the player changes SOI (sphere of influence) or when a save file is loaded. As noted by the user, this problem didn’t occur until after the v0.1.3.0 release.

The problem seems to be related to Unity’s PlayerPrefs class, used to “store Player preferences between game sessions”– I don’t know who thought this was a good idea or why it’s the norm to store these kinds of preferences on the Registry, but in every other OS supported by Unity and even Windows UWP itself, these preferences are stored in a file and not inside the registry.

On another side, it looks like the game is saving information related to in-game objects to the registry, but surprisingly the dev team at Intercept Games is competent enough to forget that object instance IDs change every time you start the game. And the old information stored on the registry is not deleted, meaning your registry will get flooded with game object information up to a point that the game can no longer start because the registry is “full”.

The developers considered this as a “critical issue” and were aiming to release a hotfix, which should be released in the “coming days”, according to community manager Dakota. One can hope that Nate and his minions deploy a hotfix for this issue faster than before. Or it will take the usual 1-week timeframe to deploy hotfixes that fix a single bug.

In any case, bugs like these and the delay in deploy fixes for critical problems like the one above show how “serious” the KSP2 dev team is, and how “competent” they are. It’s not like they have almost infinite budget and a billionaire publisher behind them. After all, they are indie developers, right?