Client Anti Cheats: Aren't as bad as you think!

Resources Community Tutorials
, ,
#207

Ok nice one bro, happy? You won an argument on the devforum

I didn’t even knew it existed because I didn’t see it in synapse’s docs.

You can’t check EVERYTHING from the server, atleast admit that

1 Like
#209

we can actually prevent everything if we put our minds into it

just like getconnections

#210

Pretty sure, It’s possible to check if instances are inside smth without events

#211

Also, Is it possible to detect wait() or task.wait() hooks? (Yes they are possible to hook apparently)

#212

yep u just have to be creative

#213

omg!11 he used the echo command and opened the dev console!11 crazy hacker :scream:

#214

idk man LOL

he says hes maling an exec soon so idk

krnl devs wants to buy it

#215

Why would you wanna detect a hook for those, if they hook that: their fault and their crash.

#216

I think they want to prevent bypassing cooldowns or stuff like that

#217 
local Variable = os.clock()
task.wait(1)
if os.clock() - Variable1 < 1 then
   --> detected
end

Heres an example
This will detect if they hook it to be lower then the value inputted

#218

Simple: Don’t make cooldowns on client. Literally the basics

1 Like
#219

No like for simple things such as a notification popup

1 Like
#220

What’s property spoofing? How do you prevent namecall tampering?

1 Like
#223 
while true do
 Instance.new("Humanoid", workspace)
end

Spikes memory to 100 and even uses a bit of if GPU

#224

This is actually halarious lmao
Is he gonna make a hack where you can dance next and name it /e dance?

#225

You could hook that

local OldInst; OldInst = hookfunction(Instance.new, newcclosure(function(class, parent)
    if rawequal(class, "Humanoid") and rawequal(parent, workspace)
        return OldInst("Humanoid") --> An exploiter could just return that and your crash is bypassed
    end

    OldInst(class, parent)
end))
2 Likes
#226

Cool. I just gave a crash method. Everything can be hooked.

#227

It was a really bad way (imo) to crash because afaik after creating those 100 humanoids if you wait a few seconds it’ll actually unfreeze

#228

Nope. Won’t unfreeze. I have tested it on a good pc. (But with a for i = 1, math.huge but that shouldn’t be a big difference)
It will even bring the Roblox had to quit error.

#229

Oh my bad I thought you did i = 0, 100

Yep won’t actually unfreeze

But when I use the funny :SetTimeout your loop will time out since you are using while true do
Instead use while task.wait() do as SetTimeout can be used to get around it

2 Likes