I have twp suggestions for preventing team killings. This is not a problem during every match, but the amount of damage one abusive player can cause to their team is serious....
1) Code into MWO that any mech killing a friendly within the first two minutes of the game will self-destruct and the player disconnected. This prevents the multiple kill scenario where one idiot wipes 2-3 friendly players at the start of the match. Allied players will not have to then turn their guns on their teamate in order to prevent them from killing even more allies.
2) A second system that will automatically shutdown any mech that fires and damages a friendly mech within the first minute of a match. A new one minute period starts, and if the same mech fires and hits a second friendly mech within that new period they will be disconnected from MWO as with the team killer scenario in 1). This will keep Team-Killers from switching to crippling friendly mechs rather then killing them and also gives teammates a chance to get away from the team-killer rather then be killed.
- Silent Screamer


Code For Preventing Team Killing
Started by SilentScreamer, Oct 08 2014 06:14 AM
5 replies to this topic
#1
Posted 08 October 2014 - 06:14 AM
#2
Posted 08 October 2014 - 06:27 AM
How about the Code be tied to the Cadet bonus?
#3
Posted 08 October 2014 - 06:51 AM
Stoneblade, on 08 October 2014 - 06:27 AM, said:
How about the Code be tied to the Cadet bonus?
You can further penalize the offending party, but my goal is to make it more difficult to actually kill teamates rather then just slap the offender on the wrist after the fact.
Edited by SilentScreamer, 08 October 2014 - 06:52 AM.
#4
Posted 08 October 2014 - 06:57 AM
Or if someone wanted to leave a match they would blow up a mech.
Better solution is a TK tracker put in place so PGI can see consistent offenders and the time they did it and deal with appropriately. Then allow a random player to "rejoin" in that guys place.
Better solution is a TK tracker put in place so PGI can see consistent offenders and the time they did it and deal with appropriately. Then allow a random player to "rejoin" in that guys place.
#5
Posted 08 October 2014 - 07:03 AM
SilentScreamer, on 08 October 2014 - 06:14 AM, said:
1) Code into MWO that any mech killing a friendly within the first two minutes of the game will self-destruct and the player disconnected.
2) A second system that will automatically shutdown any mech that fires and damages a friendly mech within the first minute of a match.
2) A second system that will automatically shutdown any mech that fires and damages a friendly mech within the first minute of a match.
If you are trying to avoid the TK player, both rules will not work. If he is dedicated, he can start the TK after two minutes. (TK-ing in a brawl is even more effective so a smart TK-er would already do this but I digress). Second, a lot of FF happens and I'd hate to see to have a forceful DC because I hit a team player for any reason (walks into line of fire, miss with arty, spray with the MG, etcetera).
TK idiots are comparatively rare, accidental FF is not (all light pilots can relate). I've only met a handful of TK idiots and only one player who tried to TK me for receiving FF (JJ'd into line of fire). Many TKs either given or received are e.g., from arty, failure of the friendly ID on the HUD, sheer stupidity. That is, part of the game.
Tracking TK stats as shad0w4life suggested should work much better.
Edited by The Great Unwashed, 08 October 2014 - 07:09 AM.
#6
Posted 08 October 2014 - 07:33 AM
I'm closing this thread as it is discussing active violations of the griefing rules.
As The great Unwashed pointed out, such a system would not prevent intentional teamkilling. If you want to do something about players who do it intentionally report them to support instead, so they can be taken care of permanently.
As The great Unwashed pointed out, such a system would not prevent intentional teamkilling. If you want to do something about players who do it intentionally report them to support instead, so they can be taken care of permanently.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users