Scripting HelpersARCHIVE
A little piece of Roblox history. Preserved for everyone, one question at a time.Read about the archive →
✓ ANSWER ACCEPTED

Does this AntiExploitScript work?

How do you add and AntiSpeed hack or AntiExploit?

Exploit:

workspace.FilteringEnabled = true

workspace.Changed:connect(function ()
	workspace.FilteringEnabled = true
end)

SpeedHack:

local Player = game.Players.LocalPlayer
while wait(0.5) do
	if Workspace:GetRealPhysicsFPS() > 61 then
		Player:Kick()
	end
end

My question is, are they working? Are they in correct format? Is it Valid? Is normal FPS REALLY 60? Am I missing something? Also, I don't have a hacking thing so... I wouldn't know. So basically i'm asking, does this look good and it works. No bugs will happen or anything? Nothing is wrong?

3 answers

✓ Accepted answer

I've found an article related to your exploit question, which uses FilteringEnabled (from what I know, it basically prevents clients from allowing changes to the server)

FilteringEnabled in ROBLOX

As for GetRealPhysicsFPS, that should work under most circumstances when players attempt to speedhack. It should be done in a local script to get the client's FPS time. As an anti-speed hack, it should be set to ~60, as some computers allow ROBLOX to run at 60 FPS rather than the common 30 FPS.

My answer to you is yes, those should be able to stop exploits/speedhacks to a certain extent. However, when your place uses FilteringEnabled, there will need to be a lot of changes if you require the client to send instructions to the server.

3 comments

0

Please fix your link. You didn't put the link in the ()'s.

0

@CreativeEnergy thanks.

0

Thanks Dummiez. Also, I like your flappy bird game.

I've found good anti-hack scripts have things that have loops and look for things with keywords like "bug" "virus" and "duplicate" in the Lighting and Workspace folders. I hope I helped

1 comment

0

Roblox already fixed that bug in 2009. I'm talking about speed hacks and exploits.

This discussion is preserved as it was. New answers, comments, and votes are closed.