Jav TKers getting out of hand, got zero help from staff over an eight hour period.

[Dealt]

hire staff, have staff use alias's to monitor as people are getting wise as to the staffies..

Log IP's of TKers as players like *scratches head* that amazon.com newblet is obviously just an alias of some old newblet passing his time being annoying. Repeat offenses get banned from Jav for w/e time if this is possible.

Staff wont like it because they want their e-fame but f'em useless tarts.

[Ilya]

snitches get stitches, yo

[leonardo91681]

dude

stop snitchin

Why should he? This thread has helped me to watch out for these bad players whenever they log on.

Team killers should be treated like sex offenders, their names and ship prefference should be in a nice little section of the website so you as a player can be informed of who these idiots are. Atleast this way you as a player can avoid the grief and move on to a happier place.

[Ilya]

dude

stop snitchin

[blackrazor]

Today I reported Dr. Block for excessive (way way excessive .. as in "art form" excessive) TKing. It got looked into by an ER who tells him to change ship. Which he does ... to a shark. I explain how that won't work, and the player leaves, returning as Doctor Block. He continues to TK, so I ?cheater again. When he is watched, his TKing smooths out to only the occasional accident. Still, we lost our match on account of this dude, and worse still, excessive Jav TKs demoralize the team. Many players then teamswitch, or log-out, or go in Javs themselves, to join in the mayhem or seek revenge.

Later this same evening, innovate and Zr, both Javs on our team, got into a Jav TK pissing match with each other, taking out our flagroom defenses with them. If you need to kill someone that badly, what ever happened to the good old fashioned teamswitch and kill them properly?

Anyways, I know staff tries. But, the TKing players have evolved to make it hard to really punish them before the damage is already done, if at all. I hope TKWatcher (or Dexter's Money System), when it arrives, will curb these game-ruining antics.

[PH]

how u fuks leave me? im only 1 on butterfrees chat now

i retire and ride off into sunset like a true champion

sry 4 this

[the_paul]

gr8 idea here

shut the fuck up cheese

[blackrazor]

The counter-strike TK system:

It's a good idea, although nothing stops the TKer from carefully counting his TKs, and logging out before the one that would give him reprisals. If he has a bunch of alts, he could cycle through them, basically allowing him to grief indefinately.

I'm all for KISS .. but it has to be fault-tolerant, also. Much of the so called complication you sited is moot, because the code runs automatically and you never see it. If you saw the code that makes TW or pubbot work, it would look complicated as all heck, but that's fine, since we don't have to see it when we play. But we do have to see some details during any meaningful discussion of design.

Anyways, it's still a good idea. Basically if one player's TKs accumulate, the player that was TKed to overflow the TKer's counter, i.e. the TK "that breaks the camel's back", gets to choose ignore / ship-lock. You still need a redemption method, such as time or enemy kills, that removes TKs from his counter over time. You need persistence of data, so relogging doesn't erase his misdeeds. You need some basic AI filtering, such as: "If enemies died too, then it's not a TK".

Still this might be a more player-controlled implementation than "auto-lock", and I like that. I would still want to keep "redemption voting" though, in case the team as a whole feels they need the player in that ship more than the TKs are costing them.

You can't do a tracking of TKs per individual player persistently though, imagine how huge every player's file would be, if it had to track every TK against every other player in the database. That's why it has to be an aggregate number (counter), but still allowing the player that he goes over with to have a big choice in his ship-lock fate.

There is little point in auto-reporting to staff, either. Staff is stretched too thin, and smart TKers just log off when they see a staffer looking their way. Don't get me wrong, I like staff. I know they try. Sometimes they catch the guy. But it's a big drain on their time and energy, for small effectiveness and reward, relatively speaking.

As for the negative buffs about which kthx was writing, EMP comes to mind.

[Malladrin]

Please people, think KISS - keep it simple stupid. Some of the posts and systems suggested here are so complicated I didn't even finish reading them.

IMHO, the only pragmatic (simple) and "fair" system for and against teamkillers has been the one Doc Flabby suggested. Minus the warning thingy, warnings ought to be left for staff to handle. To get the option to have someone locked out of jav is a really good idea (say after a handful of tks). The shiplock does not have to be that long, say 30-60 min, to have a deterrent effect.

[kthx]

Really, I don't remember any of that from Distension. Hilarious.

[roxxkatt]

Oh man doc, that opens up a whole new range of ideas, because that is badass. I love the idea and where you got it from but you are forgetting some of the more fun functions when you get TK'd.

you can Poison someone, Beacon someone, Kill someone, Blind someone.. :P I wish we could do some of that.

this is commonplace in distension, the event you have never played and hate so much

[kthx]

Oh man doc, that opens up a whole new range of ideas, because that is badass. I love the idea and where you got it from but you are forgetting some of the more fun functions when you get TK'd.

you can Poison someone, Beacon someone, Kill someone, Blind someone.. :P I wish we could do some of that.

[Doc Flabby]

What do people think of a counter-strike style teamkilling system?

Where the player who is teamkilled gets to punish the teamkiller.

The person whos go teamkilled (serveral times in a row) can choose the punishment for the teamkiller.

Instead of just !report they get these 4 options.

1. do nothing/default
2. Warn player
3. Call staff (availble on 2rd teamkill)
4. force ship change (availble on 3rd teamkill)

[Jason]

both you, pd, and blackrazor seem to be on the same brainwave with me. and i like your ideas. i would rather see more player interaction than have the system be fully automated. and i also would insist that staff still get involved as much as possible.

i'll keep batting around ideas within staff and keep everyone posted as far as where this is going to go. just be forewarned, dev has a lot on their plates right now so this might take some time.

[Pressure Drop]

we don't have the manpower to properly police pubs every hour of every day, and we never will. we'll never get a perfectly logical idea such as pub helpers to go through. staff is just too exclusive (admittedly for absolutely no good reason) for that to happen.
.

thats the thing though in an ideal world we would have a good staffer watching pub all the time and banning proper tkers but that is always unfeasible and if we are going to spend man power coding, rather than code a pretty system attempting to change something that isn't broken, implement a workable anti-tk system which incorperates a little player regulation. It's something that would actually be a big improvement for alot of ppl in pub that are frustrated at getting tked and ?cheater isn't a help. I've seen games ruined entirely by tkers and ?cheater didn't bring anyone and the whole freq is doing them ... frustrating.

i'd think about it more if one was going to be designed for pub but a quick guide for key features would be
- player getting tked has the opportunity to interact with tkbot
- bot would have preset quota's different for jav shark if possible and quota is over a set time and decays
-player logged -i.e. if repeat offenders need to be banned /ship locked for progressively longer etc

there would be alot of room for manoeuvre in the best way to implement it i've some ideas if it is going to be tried.

also this should be an assist to ?cheater not replace it entirely and staff should be told if they witness purposeful tk's to still ban and not go use the bot dummy