Anticheat Methods

Resources Community Resources
,
#87

This is not an example, this is just a description of what you are gonna do. Write an example so I can point out what can be detected or not.

#88

these are simple examples that liker gave you. there are many more ways to detect exploiters tampering with global tables. if you want to see an actually good anticheat then check my friend XoifailTheGod’s anticheat out (or you can take a look at my open source anticheat Valkyrie Anti Cheat). if you dont have an executor (i highly doubt you have one) you can just join the discord server and take a look at the “anti-cheat-info” and “anti-cheat-logs” channels

1 Like
#89

Not easy to give an example here. As I said, it really depends on the script I’m working with. One script might use the debug.info() function to return a specific value for their client-sided anti-cheat. Or maybe a method to prevent hooks, depends on the case here.

#90

Oh, I already saw it. Still doesn’t invalidate my points though.
(Took you long enough to reply btw)

#91

It really does not.

Let’s apply all of my methods in one imaginary anticheat script, which is hidden. Try to write a hook which spoofs debug.info to make it return “[C]” for one specific function.

#92

what
? the anticheat was never bypassed (same with valkyrie) and probably never will with these temu quality executors. Xoifail has working PoC for detecting every executor on injection except krampus and every executor’s hookmetamethod including krampus.

1 Like
#94

I didn’t really give an example of one definitive executor, I’m talking about the possibility of bypass, which is possible with the methods I’ve mentioned above.
Though you’re right, the current executors in this industry can’t even properly bypass Hyperion lol.

#95

there are various ways to detect these bypasses. after a point the exploiter will have to write their own bypasses to these detections instead of relying on hooks, setmetatable, getrenv and lets be real
 most exploiters wont get far as they still struggle with bypassing adonis lol


1 Like
#96

the best anticheat:

local plr = game.Players[game.Players.LocalPlayer.Name]

while task.wait() do
   task.spawn(function()
     while task.wait() do -- nested loop for double protection
        if plr.Speed > 100 or plr.IsExploiting or plr.HackInjected then 
           plr:Kick("hacker")
        end   
     end
   end)
end
6 Likes
#97

bro :skull::skull::skull::sob::sob: I’m dying

script.Disabled = true task.defer(script.Destroy, script)

do atleast this in the start of the script (op methods!!!)

2 Likes
#98

Lol. Well, you’re right. After all, once again I’m not really against client-sided anti-cheats like these. They can work pretty well against skids who cannot do anything without browsing v3rmillion lol

#99

Hello rapid please stop leaking top tier sacred anticheat methods given to us by the savior builder man. Thx.

Anyway, Liker, u made very nice topic . I like it.

6 Likes
#102

For certain functions you can do game.Clone and game.clone and they won’t be equivalent.
As for the “returned function” argument, the null byte can help protect against __index hook attacks, where they try to check if the property argument of self is “Clone” (and don’t check if there are null bytes and act accordingly).

A much better way of hooking game.Clone is simply doing hookfunction(game.Clone or game.clone, deter)

I didn’t really read that much of the argument that ensued, so I’m not really sure if this was stated already, but there you have it. :slight_smile:

1 Like
#104

Infinite Yield Reborn finna make their script web-based

#105

he’s speaking facts, so many facts. :fire:

#106

what about RbxStu the Studio Executor

#107

It is against the Terms of Service.

1 Like
#108

It is. However, i could argue it is fine as a roblox staff said you wont get banned, and you are not affecting anyone in a bad way. Idc if a hacker is on a private server and hacks (unless they are autofarming) but what i dont like is when hackers ruin the fun for others. So i think its fine to use rbxstu, even i use it

2 Likes
#109

didn’t it said

Disclaimer for ROBLOX:

  • This project was made for the purposes of testing things like Anti-Cheats and pen-testing your own games. It is made FOR Roblox Studio and ONLY for it. Methods applied on this tool are NOT applicable to the real client due to fundamental changes they have.

yeah they said that so is it still against the tos

#110

I already said its against tos, i just think its fine as confirmed by roblox staff as you wont get banned