While you can’t make this exploiter proof, you could make it to the best of your ability. Roblox is in the process and has executed their own anticheat with byfron and even has gone out to work with a hacker groups to prevent the rise in exploits. While this doesn’t mean that everything you make now is 100% exploiter proof, these are changes roblox is making on there end to help.
Client side anticheats are impossible to enforce because simply, an exploiter has full control of their local enviroment. Meaning no solution anyone can give will work 100%. Your best bet as a creator is to prevent this, but also understanding that there will always be a way around client anticheat elements, as an exploiter has more direct access to adjust their enviroment.
→ While I’m not saying client side anticheats are not important, however as a creator the main focus should be the server related exploit issues as these changes are replicated to every client, meaning everyone can see it.
If you acknowledge the above and still wish to make one, the best you can do is
-
Ensure the blur is enabled when it should, and the blur Properties aren’t modified / make sure the blur also just exists
-
Ensure the client has recieved the remote event, and that it has fired when it should have. Making sure the remote event exists on the client and the client still has a connection to it.
-
Making sure this script that holds the anticheat information, isn’t destoryed, Enabled at all times, And the Parent doesn’t change
-
When detection of unwanted changes / exploits you should kick or punish the player if one of these events occur
You cannot protect the client in anyway, however setting a basic anticheat is something that can make it more annoying to remove / provide more chances of catching exploiters.