Bukkit

@hqt99

X times in X minutes is not possible, NoCheat only remembers most data for about 1 minute (to not put to much strain on memory).

But you can set NoCheat up to ban people automatically if they fail checks, yes. All you have to do is find the appropriate "actions:" entry in the config and add "cmd:byebye" to the already existing list.

Then go to the "strings:" section of the config and define "byebye: ban [player]" or "byebye: tempban [player] time" or maybe "byebye: ipban [player]" or whatever you want, as long as the command that you want to use (ban, ipban, tempban) actually exists for your server (either builtin or another plugin defines it). "byebye" is just a name for the action, you can call it whatever you want. It's only used inside the config file to link the "strings" definition to the action.

You can find that explaination in more detail here: https://github.com/Evenprime/NoCheat/blob/master/Instructions.txt

@cvxx7q

Yeah, technically I still should take a break from NoCheat. But then again, recently some people started to ask me for payed custom plugins. And once the IDE is opened, it can't simply be closed. :)

@cvxx7q

I'm checking if it is a proxy, therefore negative would be that it doesn't get identified as a proxy, despite being one.

@cvxx7q

Lookups seem very reliable so far. If at all, they produced false negatives instead of false positives.

@cvxx7q

I don't know. How many of your players have to use (uncontrolled) public proxies to connect to your server?

@kotpx3

http://forums.bukkit.org/threads/sec-nocheat-v3-3-0-detect-and-fight-the-exploitation-of-various-flaws-bugs-in-mc-cb-1-1-r3.4523/page-76#post-962023 I didn't get to actually write that info down in a more structured way yet. Maybe this weekend.

@cvxx7q

If they use a public proxy (proxies of their ISP or VPNs should be no problem), they'll be most likely on the list, even if they are legitimate players. But you'll be able to give players a permission node that exempts them from the check and "punishment". Therefore it should only hurt unknown people that connect for the first time to the server and (at least the way I'll set it up by default) only prevent them from using chat and commands as much as normal players do. I don't want to set it up to autoban people like other such solutions do.

First test runs went very well. Checking multiple dnsbl within a second, almost no traffic (it's just a DNS lookup after all), almost 100% hit rate so far (= identifying IP addresses as "public proxies") for the proxies that I could find.

I'm currently deciding on which of these http://www.dnsbl.info/dnsbl-list.php to include with NoCheat as default settings, because I (obviously) don't want to go through them all for each player. I'll have to test some more to find like the 5 best for the task at hand. bl.spamcop.net and cbl.abuseat.org are definitely part of the list, because they identified all proxies during tests.

I believe this is going to work extremely well without the server admin needing to do anything at all (especially not maintaining IP block lists etc. themselves).

@kotpx3

No client can disable NoCheat logging, unless the player has permissions or OP status and therefore can simply deactivate the plugin (but then it's the server admins fault anyway).

What some clients do is throttle all their hacks to such low values that NoCheat won't bother them. But that's the idea behind NoCheat anyway: to make people play legitimately without hacks, not necessarily find out who tried to use hacks.

I'll definitely not go as far as starting longterm data collecting and making statistics myself. That really would be enough material for a seperate plugin.

Lookups will be handled in a seperate thread, therefore they can take as long as needed. I thought about setting players without permission into an "almost muted" state on login that will severely limit chatting (maybe 1-2 messages per minute), and when the background check is done, they either get set into a normal state or stay the way they are until an admin explicitely "promotes" them to legit player status by giving them the permission node.

That way the lookup won't prevent legitimate new players (that maybe have to use proxies to play Minecraft) from exploring the server already, even if no admin is online, while still preventing spamming.

I've already finished the DNS-blacklist lookup code now, it was much simpler to do than I expected. Now I just need to integrate it into NoCheat and set up config stuff etc. that's needed.

I can add support for .txt blacklists and similar things later, although I'm pretty sure that most public proxies are on at least some of the DNS-blacklists because E-Mail spammers love to use these. For those that don't know what I mean with DNS-blacklists: http://www.dnsbl.info/dnsbl-list.php (you'll be able to chose freely which of these lists NoCheat is going to use, simply by writing the name in the config).