Closed GoogleCodeExporter closed 9 years ago
Any comment on this? :)
Original comment by DDor...@gmail.com
on 1 May 2013 at 6:06
Yes. I fully understand this request. Scale could also be global not local. So
players have some kind of bullshit\tk\push\abc global XVM rating. If rating
exceeds some value attach to player some "bullshit" label.
Dont expect this to be implemented right away.
Changed title.
"Hitlist" or "blacklist" of players
->
"Teamkill\grief\rude rating global XVM label"
Ideas:
Icon depicting shit for griefer.
Icon depicting cyan shit for TK.
Show only top 1000 TKs, griefers.
Original comment by ilitvinov87@gmail.com
on 1 Jun 2013 at 12:08
Original comment by ilitvinov87@gmail.com
on 1 Jun 2013 at 12:08
Thanks, the global aspect of it sounds great!
But this should be in addition to the local aspect. Since It's nice to see
someone is a "cyan shit" but if he didn't team kill me personally I might
consider this less important.
So we should be able to distinguish between global griefers and personal
griefers.
Since if someone is a great player but happen to team kill me several times, I
want to see that as well.
Original comment by DDor...@gmail.com
on 5 Jun 2013 at 11:31
Just be warned a feature like this might be open for abuse. I would only
register a global complaint for a player if it was similarly backed up by 2
other players on the same team (and not in the same platoon).
Original comment by inna.bry...@gmail.com
on 6 Jul 2013 at 12:55
Original comment by ilitvinov87@gmail.com
on 19 Aug 2013 at 4:28
Why did you close this?
Original comment by DDor...@gmail.com
on 19 Aug 2013 at 7:52
1) This board is for bugs primarily.
We have plenty of people proposing enchancements at forums.
2) In case any Enchancement remains posted on this issue board means some
developer is interested in this. Developers tend to code what they want\accept.
I was interested in this kind enchacement, but now i am not. Not playing, not
coding much.
Idea is great anyway.
Original comment by ilitvinov87@gmail.com
on 20 Aug 2013 at 8:40
Original issue reported on code.google.com by
DDor...@gmail.com
on 11 Mar 2013 at 1:00