New Killshooter Mode for scenarios

[Dinger]

Killshooter=2 hitting ANY plane causes shooter to receive the damage.

Now, why would you want such a mode?
Here's an age-old scenario problem:

If all planes in flight at frame end are scored as having landed, experience shows that some people will stay in their ditched aircraft, or keep their hopelessly damaged craft aloft behind the end of the frame.  Moreover, in multi-sortie scenarios, one could for example plan a last minute bombing sortie without worrying about fuel for the return leg -- and last-minute fighter intercepts would have to destroy the bomber, not just kill all the engines.

But if all planes are required to land at the end of the frame, the CM has to call an end to the hostilities before that time, and that rarely occurs without incident.

 That's where such a killshooter setting comes in.  Making any shot that landed hurt the shooter would certainly discourage folks from dogfighting after the buzzer.  Then everyone could try to RTB.  YOu could even use this to encourage reasonable scenario behaviour by turning it on for the last ten minutes, then counting everyone not exited as lost.

Anyway, it's just a simple suggestion for something easy to implement that would give the CMs greater flexibility in designing and executing scenarios.

[Duckwing6]

Easier sollution:

"ALL A/C still in the air at frame end are count as lost... The frame will run for a max of xx hours.."
i put that in every scenario i design...

There is a give time frame for the frame so no need to call an end to hostilities.. it's the pilots own judgment call if he wants to be a loss or not  

(one needs to give folks something to make them think about RTB)

[This message has been edited by Duckwing6 (edited 11-27-2000).]

[Dinger]

The point of my post was that there is a problem with such a "At frame end, you're lost" solution.  In an ideal scenario, everybody's read the writeup and everybody's flying as if their life depended on it.  And everybody would heed their CO's order to disengage towards the end of the frame.
But they don't.  And the problem isn't the poor fools who lose their planes because they can't RTB.  The problem is that they prevent others from RTBing;  I've seen this countless times: somebody will sacrifice an airframe trying to vulch enemy fields.  An interceptor will chase the bomber formation, making a pass when they descend below his altitude.  A dogfight will continue because were one side to run for home, the other would score the kills.
Many of these cases are candidates for the .eject command. I've never served as CM, perhaps it is easier in AH to boot all these people.  Yes Killshooter=2 is not an intuitively obvious idea, but given the inherent artificiality of event endgames, it is one that I think you'd find come in handy.

[SKurj]

Making pilots land at scenario end is ridiculous....

The 2 hrs we have to run the scenario does not come close to a day in game time from what I've seen.
I can understand that the logs likely do not indicate when a pilot has ditched his AC and is sittin in the cockpit waiting for frame end, but there is little can be done about it.
In real life pilots would sometimes not make it home until long after his wingmates landed, sometimes hours... I see no reason why this should not apply to scenarios.
Maybe more detailed Logs would help...


AKSKurj