Scripting HelpersARCHIVE
A little piece of Roblox history. Preserved for everyone, one question at a time.Read about the archive →
All questions/Question #93534
✓ ANSWER ACCEPTED

How do I prevent exploiters from using CoreGui to parent their Guis?

Asked 700 views1 answers

The problem with CoreGui is that any indexing of it with a roblox script will error with a permission error. However, I found out that exploiters can parent the Gui under game:GetService'CoreGui' and operate it fine.

This is a problem because now we have a blind spot that exploiters can use, and even if we had a way to find and delete their guis, how would we test it out with Roblox scripts?

Currently erroring code

local a=game:GetService'CoreGui';
a.DescendantAdded:Connect(function(b) --> error

end);
Anonymous

1 comment

0

I don't think you can do anything to that area. I think it's locked.

Anonymous#

1 answer

✓ Accepted answer

The short answer is, you can't.

Regular LocalScripts lack the permission required to add/remove things from CoreGui, while script injectors don't have this restriction.

There used to be a method of calling tostring on objects added into CoreGui, but Roblox removed this for some reason, apparently because you shouldn't be allowed to tostring restricted instances.

The best thing you can do in this case is secure your code. If you cant stop it at it's source just make sure your game is exploit proof where you can make it exploit proof.

AnonymousPermalink

1 comment

0

One way is to try to use RemoteEvents when firing infomation

Anonymous#

This discussion is preserved as it was. New answers, comments, and votes are closed.