Commander Detonates on Game load when "No Land Units" is on.

[RiggsEclipse]

Subject says it all, every single time I load a game, with other people or just AI's with no mods and all default settings save for that one build restriction my commander detonates along with everyone else's immediately after the game starts. I've been trying to do a game of nothing but Naval and Air but kinda cant do that when your commander explodes on contact with the ground. Both logs are attached. Hope you guys can help cause I'm at a loss.

[DeadMG]

Seems to me like this is the intended behaviour... you said no land units. Your Commander *is* a land unit. Furthermore, so are engineers, so I can't fathom how you intend to get any kind of gameplay out of that situation.

[Ionic]

lol, yep that is how it works.

[ZLO_RD]

What?
I am pretty sure that "no land" should exclude commander...
Unless you assume that prebuild option is on, as well as no assasination victory condition.

[ckitching]

Something in 3641 made the enforcement of unit restrictions a little more aggressive.

UI mods used to be able to circumvent unit restrictions and build banned units anyway. They still can, but now any unit that's not supposed to exist just blows up as soon as it's finished, so it's not much help any more.
Unfortunately it seems there were a few weird edgecases like this and Cybran buildbots (which counted as air units so would keep blowing up). Will tweak it