Cheat shield is an anti-cheat fully hosted on the server. I have been working on it for a bit now and decided to release it to the public..
The place is uncopylocked so you can check out the anti-cheat yourself.
Currently the anti-cheat contains:
Anti-Fly
Anti-NoClip
Anti-Speed
All detections were scripted by me and are unique (I think)
Here is the showcase of these detections:
Fly:
NoClip:
Speed:
You can check out the anti-cheat here yourself: Anti cheat place
Discord server : ENdgGeqDyq
(P.S I dont know if discord servers are allowed if they are not please tell me )
I would recommend not kicking players for server-sided anti-cheats, unless you are ABSOLUTELY SURE that it’s an exploiter and not some check triggered due to things out of your control.
(For example, lag can trigger walkspeed checks because it looks like you are teleporting.)
Instead, you should just revert the effect of the cheat, for example, setting players back to where they should be.
Noclip detection seems not horrible although I believe this would have false positives if you have parts that toggle between colliding and not as it doesn’t double check to my knowledge.
The fly detection is prime for false positives from lag/desync, and by the seems of it can be bypassed by just having an animation playing the whole time.
Also, you don’t even have the speed detection in the game anymore, what gives? Was it a common detection method that was begging for false positives or is easily bypassed?
From what I am reading in his code, the “Speed Check” kick was removed and changed to instead teleport the player back. Here is what I believe is his “speed check” and a commented version.
Heyo, just a friendly reminder to keep it constructive (e.g., not framing everything in the negative/only focusing on negative aspects).
@OP Nice contribution, anti-exploit culture only improves when people put their stuff out there, offer new ideas, and share what they know with others - so thanks for that. @2jammers suggested adding a GitHub, which I would second, more specifically for the reason that people can create Pull Requests and create Issues to draw your attention to specific parts of code/offer solutions at the same time. This helps capitalize on the resource of the programming community itself and will help make your resource better and stronger.
If you’re looking to continue maintaining this, I’d recommend a modular set-up, so that you can freely enable or disable anti-exploit checks. This would make it simpler to maintain, easier to segment different checks, and would make things more efficient when it comes to adding onto what already exists.
friend, what you just said does not make sense, you are only good for criticism and it is already in an incomplete version, read WELL, you need to learn no no no
Agreeing with what LambHubGoBrrrr said, Bedwars cannot have a server CPS detection since the server doesn’t have access to the LocalPlayer’s mouse clicking and so “BedWars” uses a Sanity check on the remote for hitting, a way this can be done is by adding a player to a table then adding a IntValue of + 1 to the player’s table and every second reset the players table’s to 0. If the player’s intvalue is above X then ignore any attempts until it resets. Another way you can do this is having a tool debounce on the server and checking for what the correct wait time should be before hitting again.
)
