So recently I’ve noticed that there have been made some changes to the RobloxLocked property.
Firstly, trying to set it has no effect - it will always be false:
Secondly, it’s now by default false for everything, including stuff such as CoreGui:
Although despite that fact, normal scripts still error as usually when trying to index those objects:
So I’m curious, is roblox removing the property and replacing the trigger for the “Class security check” system (which used to be the RobloxLocked property) with something else? Is it an anti exploit measure?
(and no I don’t really have any use for this, I’m simply curious, as I asked around but nobody knows anything)
This has been the case for a few years now. The setter for the RobloxLocked property intentionally doesn’t do anything. This was done so that RobloxLocked can’t be modified through Lua exploits, and it wasn’t given a [ReadOnly] tag just in case any CoreScripts were still referencing it.
Setting the value of RobloxLocked and it not doing anything in response? No I’m pretty sure I looked into this a year ago and it was the case. Maybe they’ve been messing with it recently? I’ll look into it.
