Spider Spawning Generates Phantom MissionTriggers entries in sandbox.sbc, cripples servers
Current version: 1.196.016
Start an empty scenario with spiders enabled.
Spawn an Alien planet.
Stand on the Alien planet.
Save the game.
Look at sandbox.sbc. Find <MissionTriggers>
Under this you'll probably see two <item> listings, one for some random <stm> that I can't identify, and one for <stm> of zero.
Wait for a spider to spawn.
Look at sandbox.sbc again. Same location.
Under <MissionTriggers> you'll now find new <item> entries, each with an <stm> associated with your ClientID.
For *every* spider that spawns, a new <item> entry is generated.
So far as I can tell, no current method in the game clears these entries. Killing the spiders certainly doesn't. Saving and quitting doesn't.
What brought this to my attention was a modded server utilizing a couple dozen ish mods or so was starting to have 5 second freezes for everyone connected each time a player connected.
Examination of the 16MB (!!) sandbox.sbc discovered ~26,000+ <item>s under <MissionTriggers>, all structured the same way as you'll see in the above test. That's 318,000+ lines worth of data being tracked for all the spiders that had spawned during the life of the server.
Which had only been up for a day or three.
It's no wonder that auto-save was locking up the server a bit, or that players connecting to it were locking the entire server up for a short while.