Removing old mod element from persistent.sfs

[marsfan]

I am in the process of reworking what mods I have installed, and I realized that a good number of mods tend to store data about themselves in the persistent.sfs save file.

How would I go about removing this stuff from the save file, as I have noticed that sometimes the game hiccups and throws errors in the log if it tries to use a plugin to parse something it does not have installed anymore.

On a related note, is there any sort of documentation on the structure of the save file? I have wanted to learn more about the internals of ksp, and so far this has proven to be a bit of a wall.

[DMagic]

The general way that mods save information that is not specific to a certain vessel or a certain part is through scenario modules, which get added to the top section of the save file. If you delete a mod then all of its data from the persistent file will also be deleted, as the game has no way of knowing what needs to be saved and loaded without the mod present.

The only thing left over will be an empty SCENARIO config in the persistent file. Like this:

	SCENARIO
	{
		name = SomeModsScenarioModule
	}

KSP will complain about it when it is loading, something like: "Can't find Scenario Module with name...", but it isn't harmful and there is no need to remove the old scenario module stub from the save file. Editing the save file is a good way to break it.

If, on the other hand, you still have the mod installed and you delete the scenario module from the save file, then at best you might basically reset the mod, and at worst break the mod. So that's probably not a good idea, either.