20.09.2011, 13:42
Quote:
Methods of internal implementation (SQL etc) aren't really an issue, in this case that is the most obvious solution so I'm not that bothered about getting input on that (no offense). I was more interested in the usage side, for example your comment on human input - a link to an AC would be handy.
The comment on not requiring this and instead just blocking cheats is WAY beyond the scope of what we can do. It's been tried before and the sad fact is that there are too many people writing too many cheats to keep up - if one is blocked they just modify it slightly and re-release. |
Let's see then:
If you could have a new system like that, what would you want to see in it?
A webpage gathering the lists of ranges of abusers/hackers.
How would you see it working?
A trusted group of people (perhaps servers only appearing on hosted list - as it shows seriousness?) updating the lists of ranges. Then we could have an include(plugin?) which would automatically ban any of the IPs belonging to those ranges.
Basically it would be same as already mentioned SprunkBuster but instead of banning IPs it would be more efficient because it would blacklist ranges.