How to avoid MODULE without "name" in persistant.sfs?

[Gordon Dry]

Sometimes it happens that some bad mod and/or config or any incompatibility creates the weird issue that the persistent.sfs contains instances of this in several  part configs:

				MODULE
				{
					UPGRADESAPPLIED
					{
					}
				}

which means that there is a MODULE without a "name = "

And this is bad.
This creates many issues, NREs and such.

So my questions are

1. what could be the reason for this?
2. how to avoid it?

I know I can search for the blocks (using a proper text editor which can search for more than just a line of text) and delete them, save the persistent.sfs, create a MD5 of it and insert it into the persistent.loadmeta

[Gordon Dry]

So, after I deleted all the instances of the above and loaded the save again, I continued playing - now there are several instances of that bs again - without booting up KSP inbetween.

This means it's not the fault of a patch config, it must be a mod during runtime.

[Xd the great]

10 hours ago, Gordon Dry said:

So, after I deleted all the instances of the above and loaded the save again, I continued playing - now there are several instances of that bs again - without booting up KSP inbetween.

This means it's not the fault of a patch config, it must be a mod during runtime.

Where did you find the patches?

A good'ol delete-half-the-mod-and-run-the-game may help.

 

[Gordon Dry]

@Xd the great again? I did that last week and so I found KAC being the culprit for low-fps-in-Tracking-Station.

And btw the deep magic logic rituality of this half-the-mods-thing:

1. you just cannot remove whatcha want, dependencies have to be taken into account
2. I'm a good beta tester, because I play with mods - if a specific mod works without issues with only 5 other mods as companions - it doesn't mean that it works in a real play environment with all the mods needed to fulfill the need the core game cannot