Hazard, there has been a recent change in the way of counting kills and deaths, and there hasen't been the problem you are describing: this change I mean is when db counting was changed. Before it was -1 for the killer and a death for the victim, whereas now it doesn't count at all, so it's possible to make something similar to the gang-kills.
Just because it is/has been done before does not mean it is RIGHT to do so. Yes, the stats are already screwed up due to the horrible idea of "removing a death/adding no kill" (what the fuck? if someone dies they die, you can't undo the fact they died), adding more ideas to screw with the truth of the stats is not the way to go.
/stats is useless to me. Since my k/d radio is somewhere far in the negatives. Implementation of a /stats that also shows race wins, would make my self-esteem go up alot. But would it count 2nd and 3rd place as a win? Or a loss? Or neutral?
Example of why tampering is bad. How is it even possible to have negative kills? Because there is stupid code that tampers with the stats. The stats should be truthful, that is why you can classify but not "rig" them.
Think about it this way, how about if someone is being voted president/prime minister, "everyone" can vote, but I decide to put in a system that removes the votes of the poor. I now don't have the poor peoples votes for use later on and I also have a biased vote. Same principles apply here. The kill/death stats are for raw kill/deaths, you are biasing those stats and removing accuracy when you stop counting for certain conditions... not only that but the bias would be inconsistent; there's no way to clearly define how it's biased and make statistical measurements.
The command is "/stats", that is short for STATISTICS, which is what it's meant to show. It's supposed to show REAL DATA
