There are a few xpcall detections you can perform:
got nil
Dex does not trip any of these though. Some remote spies might.
It’s impossible to detect the GUI itself in any way, so just stop trying. It doesn’t work. You can only detect behavior caused by Dex’s presence. So focus on the side effects rather than the main course.
I mean if you found a way you could probably patch Dex Explorer / Synapse X because it creates a new dialog in the game called “Dialog”, which apparently was caught by the (now patched) game/coregui access method.
Any exploit worth the price doesn’t use dex that adds to coregui, it adds to a special clone of coregui that can’t be detected by DescendentAdded/ItemChanged attacks
Synapse X Dex Explorer is actually located inside coregui, no special clone. It just doesn’t show itself when you’re using it. If you wanna see for yourself and you have Synapse X, run it and then run a beta version of dex and it will show up.
There is no “Synapse X Dex Explorer”. Synapse has no official distribution of scripts and therefore any dex someone may be using is a script they downloaded from somewhere else.
syn.protect_gui does not have anything to do with CoreGui. If someone is using a Dex that parents to game.CoreGui instead, then they are a very sad and unskilled exploiter.
The xpcall detection methods catch most exploits on inject, unfortunately not including Synapse as far as I’m aware. But they do it by hooking debug.info in such a bad way that its behavior changes, so that’s detectable. (debug.info(0, 'ff') will not throw an error on Synapse)
Please don’t condone exploiting on the DevForum.
Newer versions of Dex Explorer locate themselves in coregui still, but they use syn.protect_gui which I’m unfamiliar with what it actually does.
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…