The client decides what it replicates, therefore exploiters can just… make something not if they really wanted to.
1 Like
Wouldn’t you need another client script to detect if that’s deleted?
1 Like
No, you can use AncestryChanged, however exploiters can now hook this.
1 Like
I Found Way Detect How Many Instances Added In Core Gui But Exploiter Now Put There Exploit In Nil Which Is Undetectable
1 Like
tldr: pointless
long answer:
doubt its possible, but even if there’s a method to detect dark dex, that would have no point in doing so.
there is a synapse code saveinstance() which basically saves (almost) everything without creating a single gui, part or anything else (that means it will save workspace, replicatedstorage, etc). exploiters can even take stuff further and enable decompiling for localscripts to see what script does a localscript run.
edit: if you dont get it how saveinstance() works, it creates a place file with all stuff in it
1 Like
kinda sad though, as all of my effects + hitboxes are handled through client
2 Likes
False and false there are some chads like me who have done it in a secure way with out indexing anything in the game as well as anti connection breaking checks 
, but yes a rlly good exploiter could probably figure it out.
1 Like
In the game subdirectory there is an index of nil, and when a C++ Interpreter/injector parents an instance to nil, it becomes unmodifiable, because the LUAU game environment initializes after the injection is complete. Roblox has to step up their security, but after an entire decade of the same problem, it seems unlikely to happen soon.
1 Like
You will never be use able to Dex or any other UI, Roblox has disabled this entirely for developers. So there is no way. Sadly in CoreGui without us knowing.
3 Likes
very legit sir good job with your pro antiexploit that “does not index anything in the game” u are a real chad
1 Like
the only way you could possibly detect something being added to coregui (aside from the million other reasons why this is stupid to even attempt) is by exploiting an undocumented feature
developers aren’t meant to touch coregui at all, not sure why you would even bother checking for dark dex, they can do nothing but modify things on the client which, unless your game is built like a potato, should not be an issue
moral of the story: utilize proper sanity checks on the server and don’t rely on client antiexploits, attempts at trying to patch things like dark dex on the client are futile and will be worked around at one point or another if you even manage to in the first place
1 Like
There actually is a way to not index a single thing in your game but it’s going to give you a stroke because it’s too weird to make but essentially you make a function that reads properties and then pass everything through that function and everything you now “index” would look like this.
Instance(Instance[Instance]);
So yes it is “very legit”!
3 Likes
please elaborate on how this method resolves the original issue of not being able to type check, or otherwise read useful properties of objects in coregui for the purpose of detecting dark dex?
2 Likes
not exactly, some obfuscators will throw in random if else and other stuff to make it “harder” to deobfuscate, and it will also increase the file size and decrease performance significantly
2 Likes
you can’t detect dark dex
also checking for memory spikes won’t help you detect dark dex
2 Likes
Thats crazy, i must have detected some other exploit thats called dex!
4 Likes
there’s have way to detect dark dex by detecting whenever a instance was added in coregui
2 Likes
there is no way to detect instance being added in core gui. roblox devs fixed all of methods.
also if exploiter will protect gui with protect_gui() / gethui(), you can’t detect it for sure
2 Likes
I’m not going to give you our actual detection or tell you how it works but essentially you take the regular detection and re make it so it indexes nothing.
2 Likes