Why would i ever make this post back then bruh

Resources Community Resources
, , , ,
#26

Some things that are wrong with this:
You’re technically reposting a method from around 5 months ago, there are exploiters who will definitely check the forums and stumble upon this, and potentially find a way to bypass it (via hooking)
You’re preloading the entire CoreGui every frame, this is a bit impactful on performance.
Even if it might work, you’re also forgetting about the hotbar. If tools have icon, the preload will catch that, and trigger the “this person’s got Dex or Infinite Yield” flag.

Just resort to sanity checks, honestly.

2 Likes
#27

This method has a so much bypasses, more then 3 false positives; not recommend to use unless you can patch them.
EDIT: ScriptWare Gethui() Bypasses it automatically.

1 Like
#28

uhhh ur wrong, you technically can destroy a nil parented local script by utilizing getfenv or if they have synapse they can use getnilinstances… btw exploiters can bypass a client sided kick
kinda ironic you say that someone doesn’t know how exploiting works

#29

Fixed the code, You was missing 2 end statements

spawn(function()
	while true do
		game:GetService("ContentProvider"):PreloadAsync({game.CoreGui}, function(CoreGuiID, _nil)
			if string.find(CoreGuiID, "rbxassetid://") or string.find(CoreGuiID, "rbxasset://DexStorage.rbxm") then
				warn("Suspicious UI Detected")
			end
		end)
	end
end)
1 Like
#30

Straight up, it doesn’t work. This is probably a detection for V3, but V4 already exists.

1 Like
#31

As with all client sided “anti exploits”, they are meant to only stop skids and don’t provide a real protection against exploiters, obviously you should always use sanity checks and other server sided anti exploits.

4 Likes
#32

Wrapping it inside a coroutine would be faster then having a spawn(function()

Spawn(function() creates a wait upon creating a thread. Coroutine doesn’t. Though Spawn(function() is a lot easier to use.

#33

Quick reminder: Nothing is un-bypassable for exploiters. There’s always a way around your protections. Here’s an example of something that stops simple while true do crashes.

game:GetService("ScriptContext"):SetTimeout(1)
1 Like
#34

best anti cheat solution: dont give a shit about exploiting, i could even trust client and load every game script (using single script method ofc) on the client

What you should be doing is securing important network events, stuff like currency and if the game has competive side to it, damage remotes and other things related to that

This is literally pointless

6 Likes
#35

True, best fix is to make it pointless to exploit in the first place because everything is too secure to do much.

#36

And besides Luau and Roblox itself is sandboxed heavily, the only damage that can happen if you have anything that could let it happen (e.g unsecured remotes, loadstring, etc)

But even unsecured remote won’t do much damage unless it does something specific, e.g you let a client create objects and give them many ways to customize it, that would summon a lot of people making inapprioprate stuff, but if its just something like a deal damage remote or give cash remote and you improperly secured it, well you only be damaging your own game if its multiplayer.

1 Like
#37

Just so you know the synapse X version of Dark Dex is built different because it uses heavy encryption methods. Synapse X is different from other executors because it uses low level methods to implement these exploits. When I see low level I mean it can write hex values to the cpu and gpu.

1 Like
#38
#39