2 replies to this topic

[Therorin]

Ok, I know many others have had a negative experience at mission start. It goes like this, your mech hits the ground and you are not even up to speed then bam, you hear weapons fire and you are taking damage. How can this be you ask?! How could the enemy get that close so fast? The answer is, they didn't, some trigger happy mech jock on your team just hit you with not so friendly fire. I have even seen this taken to the extreme of destroying one or even two friendly mechs. Now, my suggestion will not stop team killing, but.. what I propose is simply a device to reduce the unintentional friendly fire instances at the beginning of a match. It goes much like in the real world. From mission start there is a predefined time, say 30 seconds, where all weapons are locked and cannot be fired. Then when the predetermined time period has elapsed the pilot receives a radio message informing them that they have been granted weapons free status and at that point their weapon systems are now armed and live fire is possible.

Edited by Therorin, 10 March 2013 - 05:02 PM.

[Neolisk]

Never noticed such behavior (i.e. friendly hits at the beginning of a match), although I did myself hit friendly targets, because I could not see the enemy target well, but that happened during the fight. Anyway, 30 seconds is too much, enough for enemy encounter on small maps, especially on lighter mechs. You don't want to have your weapons locked when it happens.

[RLBell]

A problem I have noticed and experienced is the client will hang. Waking up the client requires clicking the mouse in the client window, so the first thing the roused client is fire the group associated with that mouse button. Accidental friendly fire can be avoided by not leaving your crosshairs and pipper on a friendly mech.