I helped? I quite literally just said
be careful while dealing with numbers, you should also check nans which can equal to something it isnât suppose to.
Basically if number ~= number then return end prevents nans
might as well have none because this will do nothing againt exploiters
if Equipped is for a tool being equipped, you could replace the remote event with a bindable event and have a server script fire it.
âI actually have commercial games and a master degree in computer scienceâ
if you use these poor methods of protection if you can even call it that on your games then i highly doubt you even know how to open roblox studio without having to use chatgpt to tell you how
the entire security suggested here is like having a door with no walls
This is childs play to get past. It doesnât take any knowledge of any specific exploit system to know this is super easy to get through.
Here is the equivalent of what this is:
Please enter the password: ______
The password is giqohgioqhgiqhgv;bqa btw
The client sends a password the client already has. They already need to view the remote event logs to get the remote events they need to make the exploit, so they already see the password.
Even if it was changing or something it would become harder, but the client would still have the password or the code to generate the password.
OMG you guys just donât give up ⌠I would never add just one anti cheat. Youâll be facing a wall of them. Giving you a few easy ones is just bait. A script like this one may not be perfect but it will lead to mistakes. Then youâre gone. Just give it a rest. Starting to think youâre all hackers and taken serious offence to getting stopped. I encourage any attempt at this stopping this. Hackers are just scum.
Many other developers have said well on this.
After reading the posts, I think I should add something in another approach so that you could learn why or how your event isnât safe.
Before we start, hereâs the thing: Your script is safe in terms of being hidden from exploiters, but your event and the leaderstats value isnât protected.
First, before even knowing the script you posted, exploiters would go browsing the local script where it has the TruthVal âgiqohgioqhgiqhgvâ. Then theyâll see that youâre passing that truth val to game.ReplicatedStorage.ChangeVal
. Next, theyâll just change V
to what they want.
For example, if you had this somewhere in your local scripts.
--LocalScript
local ChangeVal = game.ReplicatedStorage.ChangeVal
local TruthVal = "giqohgioqhgiqhgv;bqa"
<someEvent>:Connect(function()
ChangeVal:FireServer(true, TruthVal)
end)
<someEvent>:Connect(function()
ChangeVal:FireServer(false, TruthVal)
end)
then exploiters could go about something like this:
ChangeVal:FireServer(true, TruthVal) --Now plr.leaderstats.Equipped.Value = true
ChangeVal:FireServer(false, TruthVal) --Now plr.leaderstats.Equipped.Value = false