Comment 10 for bug 895972

Yes, SW.AutoTargetFire= is a fine feature, and I thought implementing it already. It needs a reasonably small amount of work and serves a valid purpose: finding enemy subs using a sonar auto-targeting stealth stuff, or creating an auto-forceshield you could activate in case a nuke is launched, or to have costly paradrops send to your base only if you want to spend the money, or a psychic reveal that finds enemy bases. It is more complicated to do it right, like not using up the SW if there is no valid target, though.

ShowCameo=no has to be ignored if the SW is launched manually. Otherwise you couldn't fire it at all.

AutoFire=yes will fire the SW using AI targeting. ManualFire=no on the other hand is not to be confused with something like UseAITargetingIfPlayerClicksCameo=yes. It's purpose is not to select a target automatically. It exists to disallow players getting the SW cursor if an autofiring Lightning Storm can't be fired because there already is a LS active, or the AI hasn't elected a favourite enemy player to attack yet. I'm no fan of those "In weird case of X, the ManualFire will behave like this, otherwise it will do that. Does not apply if Z. Defaults to A for blah, to B otherwise. Don't use in combination with H unless stated otherwise. See Appendix D for more information". Nobody would get that.

So there has to be a new flag. Of course it is possible to use ShowCameo=yes, ManualFire=no and AutoFire=no to mean something special like "Show cameo, and when the user clicks, select target automatically and fire", but this is completely counter-intuitive.