I did not know that lowercase properties were a thing. I realized this today when I was trying to make a proxy table for a plugin GUI and a table.
Right here it will error.
This isn’t an urgent problem since I can just not use these names, but I am still confused about why this is a thing.
I don’t quite understand your issue. Why would you want to remove lowercase properties? It doesn’t feel like it is in the way in any way, shape or form.
Im not really sure what youre asking. The Vector3 property of any BasePart has always been “Position”… with a capital P.
Roblox by default uses capitals at the beginning of properties (i think). So if you want to continue to use camel casing in your proxy table, you could just have a special “unwrapper” function that converts the property name from camel casing to roblox syntax. This could look something like this (string.sub(String, 1, 1)):upper()..string.sub(String, 2, -1) ← untested, but should work.
So thats one WORKAROUND, however you could eliminate the problem youre trying to work around by just not using camel casing in that table. Ik its like ocd but it would probably be the easiest way around this issue, if im understanding it properly.
I made this to mainly ask of why are they in the game
Yea, I will probably just use another name, but why are they in roblox then if you can’t set the property? Are they perhaps leftovers from older versions of roblox?
Yeah. It seems that can be read from, but not written to. I would definitely consider them deprecated.
