Good evening, everyone, and congratulations on the New Year holiday!
It’s very funny that Volt (AWP rebrand) hasn’t solved its long-standing problem.
Anyway, this post is about how we can detect Volt with this simple detection:
local Players = game:GetService("Players")
local violations = 0
while task.wait(0.2) do
local t1 = tick()
for _ = 1, 1000 do
debug.info(1000, "s")
end
local t2 = tick()
for _ = 1, 1000 do end
local t3 = tick()
if (t2 - t1) / (t3 - t2) > 22.5 then
violations += 1
if violations >= 8 then
Players.LocalPlayer:Kick()
break
end
else
violations = 0
end
end
Many thanks for this post Related Timing Detections.
PS: No false positives are expected. Even on low-end devices, the static response will be around 13-15, and on ordinary devices, it will be 7-10.
15 Likes
Timing detection, you’re hella detected, there’s better methods, lock in!
6 Likes
xpcall tracing still works, Volt sethiddenstack 
Volt Injector which creates many RWX sections, omg, VirtualQuery, where are you???
One way or another, this applies to getfenv as well as debug.traceback, and it is truly shameful…
1 Like
Cheat has to allocate memory for it’s dll??? surely this is detected!
6 Likes
I have been informed that your paste has been detected by bitdancer and will be promptly garbage collected next update.
4 Likes
cool now use this in a production game
It’s cool that you didn’t write something like that in another post about AWP detection 
they are both braindead and should never be used in any production games
sometimes its better to not post than post garbage that will inevitably false positive users trying to play on their nokia 3310’s
Yes, it’s best not to let users of prehistoric devices from the dinosaur era play games with such detections at all…
1 Like
Oh, right! Since you yourself know what type these detections belong to, please do not bring up this topic for meaningless replies that make no sense in any way.
Thank you!
If you don’t be quite, I’ll repeat the great reckoning of detection leaks like Liker before me.
1 Like
I advise you to do it! Don’t just say it, words are worth less.
To be clear, I’m not trying to be rude to anyone, so…
how to be corny tutorial 2026 unpatched:
2 Likes
there is an easy fix for this…
- You can’t just detect hackers by just detect how fast the game run, what if Roblox scheduler think it just a dummy script that slow the whole game down so it slow the script?, then bang, you kicked a innocent
- debug.info() slows down the game, you making it easier to kick local player, false positive, basically DoSS yourself
- You don’t have proof
- Hacks is obviously faster, you run in a VM and you expect assembly (a.k.a machine code, direct CPU instruction) level speed
TL; DR: scam, waste of client performance
ROBLOX has long been built brick by brick, and such a case will clearly not happen.
Yes, of course, debug.info is definitely not an easy operation, and we perform it constantly every 1e4 times!!! But anyway, to make the call as empty as possible for the result, we call debug.info with non-existent arguments, that is, 1000 is the stack level where there will never be anything.
Based on what you said, Task Scheduler is divided into priorities, where each task is processed by category.
The claim that this is a scam is an exaggeration.
In many cases, the value is higher because debug.info is hooked and goes through additional overhead operations, i.e., through newcclosure and other garbage.
For Volt, as I understand it, this function is hooked like the rest for setstackhidden, where without a hook you cannot simply hide the influence for any stack walks. It’s a trivial return old that will increase the function’s response many times over without any compromise.
PS: Based on the conversation about Task Scheduler, I refer to a source from 2016, where everything could have changed long ago.
1 Like
You probably don’t even know what is a RSP and you are here to talk about stack with me. Exploit use a different stack, you both are not even in the same OS thread…
Gives these before you talk
- Proof of it doesn’t kick innocent and it actually work on hackers
- Stack is on used on function calling, passing argument. You both are not even in stack, each OS task has its own stack. Show proof that exploit actually somewhat run inside ROBLOX and
RSP is pointed to a ROBLOX managed stack, not an OS thread that inject and you don’t even know
- If hack can do something you make up, like
setstackhidden, they will also hook on tick() and os.time
Friendly tip: just delete your post to not scam beginners
citadel hasnt been updated in 6 momths
deobfuscate ib1 instead
