It is not a total solution but how about a 5 second weapon lock after friendly fire?

If the shot was inadvertent the hit player would have time to reposition and the shooting player could reposition or re-aim.

If the shot was malicious the hit player / team would have a chance to identify and trash the shooting player and the shooting player would have some added risk.

This scheme tries to strike a balance between limiting the damage a malicious player can do (which we DON'T want to nerf too much) and keeping friendly fire from simple mistakes minimized.

Of course it could be combined with the more traditional limits like ISK / Kick / BAN for situations when a longer lasting penalty is appropriate.

Hmm, what about...

Maybe make it so if you TK 7 or so people in one match, you are flagged as a traitor, and for the rest of the match, both teams see you as red, (and you see both teams as red) and maybe make it so they can only spawn in default/static spawn points? maybe even make it so they can't hack stuff? (preventing them from taking spawn points/emplacements, but still allowing them to blow them up.) They could still earn points from killing, they wouldn't lose any isk, but they would just be marked as traitors, and maybe even have a "times marked as traitor" kind of stat on their player cards.

Treachery is punishable by death. I think in high-sec, the "punishment" for TKing should be minimal. I personally like the flagged as red thing. That way you'll be getting shot at by both sides, and you'll be able to be spawn camped. but if you're good, you could still get away with it, and if there are multiple traitors, it'd almost be like three sides to the fight :D

I believe there must be an aditional mechanism, reporting.

Many people will play this game as random matches, so if a player is deliberated tk'ing someone in these matches there should be a report tool.

If enough reports are given this is escalated toa gm that can then take action against the player.

I know WoT has this feature built in. Its a interesting option to protect the random people that may gain a enemy within its own npc corp lines and help to keep the game clean and fair play on.

i really like the idea of flagging the tker as red for both parties but this brings up other questions like how many times to kill before this happens. should the player get any isk rewards after the battle?

The biggest issue I have with the paying isk is what if they have no isk left. what if someone just creates a acount to do nothing but tk.

However since DUST is an FPS, we have to take into account strafing accidents, unlucky grenades (Don't hit the doorframe smartass, or the classice grenade hit a guy in the face 2 feet away from you), poor aim and frantic tank combat, aka the suprice roadkill.

Well, with my idea, the TKers would still get ISK after the battle. Everyone deserves the ability to come out ISK efficient. But since they would be red to everyone, and possibly not be able to hack (but still able to blow up assets manually), and , to cap it all off, be limited to static spawns, it would greatly reduce their effectiveness on the battle field, and the odds of them coming out ahead in efficiency would be dismal.

My idea of flagging the person isn't to penalize saboteurs, it's to discourage idiot kids who don't know what they ard doing from griefing, as well as discouraging careless trigger-pulling.

Unless you are confident you can take on 31 other people yourself, when you are limited to where you can spawn... then I would suppose you'd be a bit more careful :P