Open tapple opened 6 months ago
I found what might be sources for these fields:
in the code they are
I'm not sure if Apollo is a roblox project or not, and I don't understand what Roblox-Client-Tracker is. Is that files extracted from the roblox game player app?
Those are the names I gave them while reverse-engineering how UniqueIds worked. There's nothing official about them.
None of the structure/field names throughout the spec are required, and you can use whatever names you want. I've chosen names based on what is sensible and useful. For example, Color3.R/G/B are named so because this makes it obvious which fields of the Color3 type they correspond to. There's nothing stopping me from changing them to Color3.Foo/Bar/Baz except a visceral aversion to making things more confusing.
In the case of UniqueId fields, they have no public facing representation; UniqueId is visible only as a blob within rbxl. So in the spec, the only significance in their names is to identify their purpose, which I think the current names do just fine.
I'm not sure if Apollo is a roblox project or not, and I don't understand what Roblox-Client-Tracker is. Is that files extracted from the roblox game player app?
Apollo is a project related to GraphQL that is independent of Roblox. Roblox likely uses their libraries internally, but also has converted them to Luau.
While Roblox-Client-Tracker is also unaffiliated with Roblox, most of the files it hosts are authored by Roblox.
I'm not sure where to ask this
UniqueId is documented as having 3 fields:
Are these names official, or inferred? If official, is there a source? if unofficial, how were they inferred? Just by examining their contents in a bunch of rxbm files, and trying to make sense of them?
I understand UniqueId name comes from the xml tag name. But the id is just a binary blob, with no field names
I'm just curious. If there's good answers, maybe the doc should mention them