Oh, sorry about that. There’s just so many unprofessional and unserious people on the DevForum that I’m used to questioning them and stuff
While it didn’t exactly contribute to any discussion, it doesn’t warrant your condescending tone. Flag the post and leave it at that, don’t use it as an excuse to berate them.
I am still helping/teaching people by explaining why it is wrong though.
That’s perfectly fine. You just came off as a little rude.
It was well deserved because they gave a misleading script that’s considered a trojan.
Yeah, I did! I didn’t join here for it to be treated like some gang where everyone follows rules and lines up like the military. I joined here to develop with others and learn, while having fun at the same time.
Please don’t swear here, you may know what it means but you didn’t get the point of it
I’m pretty sure with legit close to no scripting experience or just putting it into the script editor that you know it’s fake.
Well then this explains your rotten attitude towards everyone.
If you wanna continue go dms to avoid off topic, thanks.
It is indeed possible to detect dark dex without using stupid ways like gcinfo(), one of the ways would be using preloadasync (with which i am not going to go in detail).
Cry about it.
Humans are humans if he wants to add a lil humor I don’t see the issue. Don’t be “that guy”
But I will!
This is the current Dex (and GUI) detection:
game:GetService("ContentProvider"):preloadAsync({game.CoreGui}, function(assetid, status)
if assetid:find("rbxassetid://") then
while true do end --We can confirm that this is a unknown gui as no roblox gui in coregui uses rbxassetid://, so lets crash them
end
end)
How this works:
Basically, we request a preload from game.CoreGui, then we check if an assetid contains rbxassetid:// (as no roblox coregui object uses rbxassetid://), if there is, we crash the client.
you could send the clients guis to the server via remote and just check on the server
you can’t use game.CoreGui on your script.
They’re not misleading, I actually BOUGHT it myself.
Well, does it work? Have you actually tested it with multiple exploiters?
you can bypass this using metatables.
Ofcourse, your number 1 rule is never ever trust the client ever.
I will give you an true answer.
ya don’t.
why? The proof is simple. The owners of dark dex and other versions of it can easily patch it. Or even the exploiter himself can bypass it in many ways.
let’s just make a list.
metatables
disable localscript
destroy localscript
set localscript parent to nil
etc
you can never rely on localscripts as an anti exploit , it’s better to rely on serverscripts as anti exploits.
The exploiter can destroy the localscript and send malicious data to the remoteevent. So the server will think “oh it’s safe.”
Yes it does work, source is obfuscated can’t say more
the function preloadasync doesn’t security level check, so it won’t error, and will just return the assets in coregui
What’s to stop the cheat author from simply making the cheat executable install its image assets locally, in the Roblox content folder?