You just said two different things. Dex cannot be in both CoreGui and syn.protect_gui
. If it is in syn.protect_gui
, that is the reason you cannot detect it anymore.
So… is syn.protect_gui some kind of coregui clone??
Yes, exactly. It is a subclass of CoreGui that is created by the exploit. This is also the reason that doing certain things with it crashes the game, especially on certain other exploits (which do the same thing).
The only exploit which is completely undetectable also happens to be the same exploit that doesn’t use a subclass of CoreGui.
So this is not just regular coregui? (Dex clearly shown inside.)
That is regular CoreGui, you’re just running a version of Dex which parents itself to the regular CoreGui. Like I said, there is no one version of Dex.
(This is the script hub)
Synapse doesn’t have a script hub. What are you talking about?
Huh, I stand corrected then. They must’ve added that recently then(?).
In that case, the version of Dex on the script hub is insecure and you shouldn’t use it. You shouldn’t even be exploiting in the first place. Exploiters who care about detection will use a modified copy that uses syn.protect_gui
.
Synapse X has had a script hub for years, this gui does use syn.protect_gui. Every version of Dex Explorer before this version doesn’t have syn.protect_gui as far as I’m aware.
Oh the Synapse script hub has been around for years. Their dex is simply the same as any other dex, it just uses syn.protect to protect itself from recursive findfirstchild. The other things are kinda useless except the ESP. It basically just has a few utilities that are considered essentials but even the unnamed ESP is opensourced in github.
I must be really out of date on Synapse then (better than being an exploiter, anyway). Looks like syn.protect_gui
doesn’t work quite the way that I expected. Apologies.
But here’s the real question, is there even a good way of accessing coregui / game? If there is thats basically dex detection in a nutshell.
From LocalScripts’ weak default identity of 2? No. CoreGui is intentionally protected.
Roblox really needs to add a official method of accessing coregui…
No they don’t. There’s a reason it is this way. I’m pretty sure the CoreGui shows some sensitive info that developers shouldn’t have access to.
I want to tell you and coolswagger that there actually is a game that detects Dex! So it IS Possible: Crystal Anticheat - Roblox
Coregui access with limits, such as not having access to default roblox guis and sensitive info.
We’ll see about that. Let me check it out.
In your case, Roblox needs to at least let us be able to count the instances in CoreGui, but not access it…like we can get a # of screenguis ordinarily 6 or so…and if another descendent is added we can count 7 and then that’s a cheat. That way we dont interfere with coregui but we only get the count to know if something additional is there.
It seems to detect dex but its either using a unsupported method or memory usage detection.