From what I’ve looked for, there doesn’t seem to be any documentation regarding the replication order of different types. For example, if I fire a remote and then set an attribute on an instance, can I reliably assume that one will replicate before the other? Can I guarantee an attribute will exist before a tag on the client after setting them in that order on the server? This type of information is very much needed.
Affected URL: https://create.roblox.com/docs/scripting/attributes
Hey sporb, the short answer is no, you can’t assume the order, which is what we’re trying to convey with “The Roblox Engine doesn’t guarantee the order in which objects are replicated from the server to the client, which makes the Instance:WaitForChild() method essential for accessing objects in client scripts.”
In your view, should we extend this to “in which objects (and changes to objects)” for clarity? On the client in particular, we recommend programming somewhat defensively and making extensive use of the events and signals for listening for changes.
When you say “The Roblox Engine doesn’t guarantee the order in which objects are replicated from the server to the client”, this reads like it’s related to Streamed objects, which makes sense. However, it doesn’t imply anything about the order of other information, such as the remote queue, attributes, etc. It would be more useful to explicitly state that these things are unreliable if that is the case.
Definitely. I added a paragraph to that section with what I hope is some extra clarification. Thanks a bunch!