Bukkit

@deleted_9426768

Well, it's a good thing I'm not a criminal who has you in a strangle hold threatening to snap your neck if you don't use it. Don't use it if you don't want to use it, I don't understand what's so hard about that concept. If you want me to actually do something to fix it, please file bugs like a sane human being. Thank you.

@HitmanPL47

Basically we listen for PlayerMoveEvent and check the distance between those to determine if a speed hack is occurring. The signature from something like that would be that the difference between those is huge. For instance, packet 1 might contain a location of X: 30 and packet 2 has a location with X: 53. That's a delta of 23 blocks in a solitary movement, which means they're either speedhacking or trying to teleport or yada yada.

The difference with timer is that EVERYTHING client-side is increased, including the rate at which packets are sent. Instead of making the client go super fast, it just sends normal movement packets but at an increased rate. This means it's not possible to compare the movement values or even really trust anything from player move events because the rate at which they're being sent is way too high, but the values will seem normal. This means I have to find another way to do this which entails counting how many times a player has actually said they're moving in the last X seconds; if that's higher than a rate I've measured and considered too high, we consider the check failed. The problem with this is the internet. The way packets work means they may not all arrive exactly when you expect them to because they'll take whatever route through the internet they all consider to be the fastest, which means the server could get 50 of a player's movement packets from the last minute or whatever because some router along the way was clogged. This happens a bit too often (albeit at a much less lower severity) for me to consider it functional.

@HitmanPL47

Haha right on. You need JUnit for that one, I'm wondering why you would need to bother though really, a bit strange that maven wouldn't automatically download those for you. I any case, if JUnit is the only thing causing you issues, I would just actually delete the "test" folder in src/main/net/h31ix/AntiCheat and just totally remove that dependency from the Pom.xml file in the base dir. You shouldn't need it; tests are really only to make sure I've not missed updating something when a new mc version comes out.

@HitmanPL47

All I can say is it has false-positives and I haven't had time to work them out. To compile it with the check, you'd pull the source from github (it's a Maven project, so the dependencies should handle themselves) and uncomment this code. (remove the /* and */)

EDIT: Just made a quick commit so people could use that specific revision to compile a build with timer. The commit is ea606c5dc8... - you should be able to pull it using

git clone git@github.com:h31ix/AntiCheat.git
git checkout ea606c5dc80ae0ec6af04aa31f65b34d78702e7b

(which creates an AntiCheat directory with the code) And then compile that revision. (assuming you've now changed directory to the one you just cloned)

mvn clean install

If this is a bit over your head, I'd just wait until I can build something with this change in it and be open to more testing of the check - still, good to know how to compile stuff on your own.

@HitmanPL47

There's built in code to protect for it, but it's not enabled by default; to turn it on you'd have to compile the program yourself with that check enabled (it's experimental). There's already a ticket open asking for this, and I'm dedicating some spare time soon to getting it in working order.

@Dippoakabob

Not if you use the API. Please don't advertise your server on my page.

@HitmanPL47

Are you talking timer?

@xICaerusIx

That's a vanilla minecraft spam disconnection, not from me.

@pcatack

Unfortunately my program hasn't had mind reading features built into it yet. Aside from water walking, all of that is entirely client sided and can't be blocked by any system implemented on the server.