Comment #1 originally posted by Nathaniel.Stalberg on 2009-12-06T01:29:53.000Z:

Actually, I just tested this and it doesn't usually immediately crash Ares or Antares. It does cause strange
behavior though. Apparently, if you don't control anything, the game tries to transfer control to the next
object created, including ones that you shouldn't be able to control: projectiles, warp flares, energy pods,
enemy ships, etc. When the object you currently "control" dies, you jump to another, or if no objects are being
created, just sit around controlling nothing. The camera centers on the object, but you can't control it and
mouse selection and almost all keys stop working. You can still control the computer menu by double clicking
on it, but that's about it. Certain options don't work, including "transfer control", while others, such as "go to
my position" can cause the game to crash. You can still win or lose the mission, so if you captured the planet
needed to win, you'll win as normal within a couple seconds. During my speedrun, I recorded a video showing
Ares crashing when this happens, but I haven't replicated that today.

Comment #2 originally posted by sfiera on 2009-12-06T07:46:07.000Z:

Alright, then we'll chalk it down to undefined behavior. There's no correct course
of action, so it takes some arbitrary, incorrect course of action.

Implementation note: I think all that needs to be done is prevent transfers to objects whose presenceState is "kLandingPresence". This is probably fairly easy.