And no, it cant access LoadStringEnabled, it’s not even a key of the userdata by the looks of it (or there’s some metatable blocking code idk?)
But yes, Roblox can easily just either add an interface method to those properties that aren’t seen by Lua, or just add them to Lua with RobloxScriptSecurity or LocalUserSecurity permission, so a Lua window could still happen
That is a very good point. I would bet this is likely a focus of the new properties widget as well, probably to make editing properties easier even with a lot of them. I am starting to become less concerned with property bloat personally as I prefer function over cleanness in that case, and I think perhaps that may be where Roblox is trying to head.
The biggest problem with that I think is that the solution to property bloat has always been inconsistent, and probably will remain that way unless a much more general solution is created, and I think if it is Roblox’s goal to allow for more properties on things without causing issues, they’ll probably start with that on the property widget.
Not sure what you mean by “doesn’t exist according to Lua” (Lua is a programming language), but TweenService generates error messages for properties not accessible from scripts.
