After reading around the net, this forum, and examining a few of the anti-cheating scripts I am left wondering something I hope you guys can clear up. I am referencing private trackers (the .bz family to be exact)
To me, the most logical cheat detection would be if a client was reporting upload on a torrent where no other clients are reporting downloading or your client reporting uploading beyond a threshold above or below the combined activity of your peers.... but from my experience this doesn't seem to be the case. Unless I missed something (which I may have) the anti cheat scripts I have looked at don't even examine the activity of other peers on a torrent in that way. They just look for you to make blatantly stupid mistakes.
For instance, I can get on a torrent with many seeds and leechers (who are inactive because they only wanted some of the files of the torrent). So, I know there is pretty much no activity on the torrent unless someone connects for real. I set ratio master to leech with at a relatively low download speed. I would think since none of the other peers are reporting upload that I would be red flagged.
Once I appear to have downloaded all or most of the torrent I start to appear to upload at an even slower speed that I had been downloading. I would think this would again red flag me as none of the other peers are reporting download or as much download as I am reporting upload.
But, it would appear that this is not how most detection methods work? Is this because it would be too CPU intensive on the server to cross reference reported activity on the same torrent?
Bookmarks