How To Use .Desendant Added for CoreGui

Help and Feedback Scripting Support
1

Hello, so I’m well aware of the “Dev’s can’t access core gui” Stuff, But Many people have done it using FindFirstChild but for some reason that won’t read core gui anymore.

game:FindFirstChild("ScreenGui", true) then --punishment

This used to work a couple days ago and I guess roblox patched it?

But how can I use game.DesendantAdded To look for new instances in core gui

game.DescendantAdded:Connect(function(descendant)
	pcall(descendant)
	if descendant:IsA("ScreenGui") then --Errors with the script lacking permission error
		print("ScreenGui")
	end
end)

Now for me this is sad because I developed an anti-cheat 100% capable of detecting core gui, and it took a lot of work, and it’s sad to see roblox “giving exploiters the leverage”. Please let me know if you know how to use this method.

3

game:FindFirstChild("", true) still works as far as I know, but the reason you can’t access anything is because of script permissions, and all properties and functions within CoreGui cannot be accessed using a script unless it’s from Command bar within studio, or a plugin. This is for good reason, as the LocalScripts should not be able to touch CoreGui, since they can easily make a scam game, such as hiding the purchase UI like what was discovered a couple months back. Exploiters can edit CoreGui, but LocalScripts cannot.

2 Likes
4

I Don’t want to edit it or anything, just want to be able to see when something new enters. I’ve searched for so long and found a solution only to get it patched again which really sucks, I don’t know why we can’t just see when something new gets put in… It’s honestly frustrating.

5

Well, I believe for safety reasons they just don’t want you to do anything since they can’t trust ya.

6

One of the reasons why CoreGui cannot be read from is because you may punish players for reporting your game.

1 Like