18 replies to this topic

[Abledime]

I am fed up with team mates testing weapons at base just after start up.

three matches in a row I've had armor stripped from my meck.

one was a twin gause ML combo to RCT on my light Meck instant RED and damage to FCT armor


I therefore propose any Friendly Fire at base in the first 30 secs should mean forfeit of any Cbills for that match.

then maybe people would learn to set up weapon groups in Training grounds or hold fire until they see the enemy.

Edited by Abledime, 09 April 2013 - 09:40 AM.

[blinkin]

sometimes it is bugged input at the beginning of the match, but overall i agree there should be something. your response is pretty obviously emotional and a bit extreme.

i say we fine players 2x whatever would be awarded (cbills AND xp) if the friendly they hit were an enemy. this should be throughout the match. also weapon damage should be set to 0.00 for the first few seconds of a match.

[Mechteric]

maybe the dropzone locations for mechs on all maps should just never be put in front of one another, rather they should be line abreast or something

[Donas]

one would hope that there will be internal Teamkill/damage monitoring in the code that punishes players. This damage could be set to only the first 30 seconds of a match, or weighted heavily towards the early part of a match. Combine this with the option to forgive penalties to the person receiving the team damage (since it might have been his fault later on, stepping in front of an lrm volley for example) and you've got a winner.

WoT goes even further by flagging the player a teamkiller, and allowing anyone on the field to kill him without penalty. And it I recall correctly, it even flags them in the forums.

[Neolisk]

Donas, on 09 April 2013 - 10:03 AM, said:

WoT goes even further by flagging the player a teamkiller, and allowing anyone on the field to kill him without penalty. And it I recall correctly, it even flags them in the forums.

Without forgiveness period? That sounds like a soft ban.

[Makenzie71]

I vote no on the damage. You might think it's stupid for people to test their guns at base, but more often than not friendly fire gets the people who think it's smart to walk in front of a live-firing buddy like they have right of way. It'll be pretty hard to separate the two.

[Markis Steiner]

The easiest way would probably be to make the first 10-20 seconds of each match a time when FF does not cause damage. This will not stop moronic testing and accidental discharge through cats jumping on the keyboard, but it might help.
In the heat of the battle it would be hard to tell the difference between someone trying to shoot an ally and someone diving in front of an ally and getting shot because he jumped in the lane of fire.

I am a big fan of the forgive button on TKs, I hate the idea of TK forum spam like on WoT because accidents happen. I also hate the fall damage from spawning in Tourma....the Carbon Gigatube map.

[blinkin]

Markis Steiner, on 09 April 2013 - 08:41 PM, said:

The easiest way would probably be to make the first 10-20 seconds of each match a time when FF does not cause damage. This will not stop moronic testing and accidental discharge through cats jumping on the keyboard, but it might help.
In the heat of the battle it would be hard to tell the difference between someone trying to shoot an ally and someone diving in front of an ally and getting shot because he jumped in the lane of fire.

I am a big fan of the forgive button on TKs, I hate the idea of TK forum spam like on WoT because accidents happen. I also hate the fall damage from spawning in Tourma....the Carbon Gigatube map.

i am also a big fan of the forgive button, because we all have moments of profound stupidity when we wander between the friendly atlas and his target. i should have the option to forgive friendly fire incedents caused by my own ignorance.

[Abledime]

this was more aimed at people who on start up immediately fire off a alpha strike into the meck in front.

[blinkin]

Abledime, on 09 April 2013 - 10:49 PM, said:

this was more aimed at people who on start up immediately fire off a alpha strike into the meck in front.

i don't know for sure about it anymore, but i do know for a long time there was a bug where occasionally on start up your mech would just fire on it's own. i had it happen a few times in the past, but luckily no one was ever in front of me when it went off.

[buttmonkey]

the worst ones are teamkillers, i wont tollerate them anymore, have had a couple of fights with people on my own team. its their own damn faults they think its funny to keep tagging you with a m laser, not so funny when you turn and hit them with double ac20 or something

[MentalPatient]

I propose an honour system to deal with friendly fire, tied in with the future ranking system. If you shoot a friendly accidentally or intentionally it takes demerit points from your honour. As your honour increases, through assisted kills, saviour kills, capping points, taking objectives (in CW), or any kind or meritous behaviour, you become eligible for promotion. In order to receive a promotion you must be nominated by at least 2 other players. Higher ranks will allow access to more equipment, more say in taking objectives, and eventually calling the shots of the battles for planets.

On the battlefield, accidental friendly fire should still not be tolerated and there should be consequences.

[Bobzilla]

Sometimes when your typing in chat the key inputs act like your not. The best solution is not having mechs facing each other at drop, other wise people who do not deserve getting punished will. Any system that cannot discriminate between errors and intentional action will be ignored as people will think, 'who cares, i get penalties either way'.

The penalty for FF is your team is weaker and your chances of winning and getting rewarded are less. The more FF the less chances of sucess. Its a pretty good system. It's flaw is one person can ruin it for the team, but each team has equal chance of having that kind of player. I'd rather have a teamate that does 700 dmg and 50 FF dmg than a player that does 100 dmg and no FF dmg.

[MasterErrant]

blinkin, on 09 April 2013 - 09:55 AM, said:

sometimes it is bugged input at the beginning of the match, but overall i agree there should be something. your response is pretty obviously emotional and a bit extreme.

i say we fine players 2x whatever would be awarded (cbills AND xp) if the friendly they hit were an enemy. this should be throughout the match. also weapon damage should be set to 0.00 for the first few seconds of a match.

the problem is that in fast combat it's usually the hit mechs fault. not the firers.

there is a bug that make weapon groups not show correctly...sometimes you have to test you setup. i'v been hit a few times actually killed once in my commando. and I've also have others walk right into my fire even though I aim high...had a spidey jump into dual ERPPCs,,,lol,,,he was suprised.

[blinkin]

MasterErrant, on 11 April 2013 - 04:17 PM, said:

the problem is that in fast combat it's usually the hit mechs fault. not the firers.

there is a bug that make weapon groups not show correctly...sometimes you have to test you setup. i'v been hit a few times actually killed once in my commando. and I've also have others walk right into my fire even though I aim high...had a spidey jump into dual ERPPCs,,,lol,,,he was suprised.

i have played assault mechs before. in general it is far easier for a mech pilot to release the trigger than it is for a pilot to change the trajectory of his mech significantly (even with a light mech).

so it isn't always the fault of the person firing but most of the time it is. far more often than when it is the fault of the victim. the slowest ballistic weapon we have is the AC20 at 900m/s. this means that out at 900m (very long range) mech pilots have less than 1.00 seconds to respond.

some friendly fire incedents are inevitable, but the one firing has far more control over whether it happens or not than anyone else. so any suggestion i make is going to favor punishing the one who pulled the trigger.

i will say in general that LRM fire should be forgiven though since those shots are often in the air for several seconds before they come back down to hit either friendlies or enemies.

[Mechanix460xvr]

I have had extreme cases of weapon lag. I'll repeatedly pull the trigger and nothing happens. Seeing my fireing window had closed i'll turn to find a new position only to end up shooting a friendly in the back with my twin guass. So there are too many variables to have the authority to say what is intentional or not.

[MasterErrant]

blinkin, on 11 April 2013 - 07:04 PM, said:

i have played assault mechs before. in general it is far easier for a mech pilot to release the trigger than it is for a pilot to change the trajectory of his mech significantly (even with a light mech).

so it isn't always the fault of the person firing but most of the time it is. far more often than when it is the fault of the victim. the slowest ballistic weapon we have is the AC20 at 900m/s. this means that out at 900m (very long range) mech pilots have less than 1.00 seconds to respond.

some friendly fire incedents are inevitable, but the one firing has far more control over whether it happens or not than anyone else. so any suggestion i make is going to favor punishing the one who pulled the trigger.

i will say in general that LRM fire should be forgiven though since those shots are often in the air for several seconds before they come back down to hit either friendlies or enemies.

un at close range under a hundred meters where about half of combat ends. it's a done deal. once the trigger is pulled it's done releasing the trigger doesn't affect a shot already fired. it's a fact of real life combat as well **** happens.
My uncle has had a us >50 caliber bullet in his back since 1967 for that very reason

My point is that this is giong to happen and if they put heavy penalties for "Every" incident as suggested the it'll just happen. I'm pretty sure they are tracking and investigating these things.

[Rushin Roulette]

blinkin, on 09 April 2013 - 11:04 PM, said:

i don't know for sure about it anymore, but i do know for a long time there was a bug where occasionally on start up your mech would just fire on it's own. i had it happen a few times in the past, but luckily no one was ever in front of me when it went off.

There never was such a bug. This was caused by smegheads ALT-Tabbing out of MWO for the loading sequence but using the mouse to change MWO to the primary window once it was loaded.... combine that with the fact that the Left mouse button is the primary firing trigger for most players. Those werent friendly fire situations... they were m0r0nfire situations. That is one reason why PGI added the mech startup sequence to give these guys more time to safely think... derp maybe I should click on the MWO window now as the match is starting.

MasterErrant, on 11 April 2013 - 10:39 PM, said:

My uncle has had a us >50 caliber bullet in his back since 1967 for that very reason

Whaaa? Your uncle must either have a gigantic (and extremely hard) back to be able to fit a light artillery shell, or you are talking about a small bit of shrapnell from an artillery round. If he was really hit squarely in the back by a >50 cal bullet/shell, then there would be nothing left of said back... (or any wall he was close to either for that fact)

[Bobzilla]

Rushin Roulette, on 11 April 2013 - 11:19 PM, said:

There never was such a bug. This was caused by smegheads ALT-Tabbing out of MWO for the loading sequence but using the mouse to change MWO to the primary window once it was loaded.... combine that with the fact that the Left mouse button is the primary firing trigger for most players. Those werent friendly fire situations... they were m0r0nfire situations. That is one reason why PGI added the mech startup sequence to give these guys more time to safely think... derp maybe I should click on the MWO window now as the match is starting.



Whaaa? Your uncle must either have a gigantic (and extremely hard) back to be able to fit a light artillery shell, or you are talking about a small bit of shrapnell from an artillery round. If he was really hit squarely in the back by a >50 cal bullet/shell, then there would be nothing left of said back... (or any wall he was close to either for that fact)

He ment .50. Could have gone threw a few other peole first.