The reason for this (IMO) potentially dangerous behaviour is that when you modify a mech build and save it, the game save it into the internal DB or some save file that we don't currently have any idea where it is. That isn't bad, it's a good thing. It lets us save our favorite broke builds to repeatedly bring up to beat people over the head with.
The bad thing, and unknown to most of you, is that whenever Skirmish or Mechlab starts up, it does a basic verification check against ALL saved builds, and start generating warnings such as the above when they find mech builds that doesn't work. The worse part is that it doesn't ignore these, but goes into stunlock.
Since these builds are not in JSON and is actually likely in a DB somewhere, we can't manually remove these entries. The solution I went with (since it's my mods and I know what the heck I did), was to reinstate the missing entries that the system is complaining about, and try the Skirmish and Mechlab. Once those are working, I go through the entries and delete any that contains the bad material. And then I can remove the unwanted Manifest entries. If that sound like a lot of work, yes it is.. well actually not that bad since I have certain habits. But that's because I know the crap that I'm working on.
But imagine if you are a basic user who heard of this great mod and you download but found it not as great as you felt it to be. You remove the mod and then the whole game locks up on you. You reinstall and lose all progress in the main game. How'd that make you feel about the mod creator?
