There are various errors when attempting to use a nil value such as “Attempt to index nil value” or “x is not a member of y”. This has caused confusion among new developers when it happens for an object that does exist, but hasn’t replicated to the client yet. When throwing these clientside, we should add an addendum to the error that says “Has the object replicated yet?” or “Did you mean to use WaitForChild?” (maybe not a good idea because slapping WaitForChild everywhere you get a nil error is bad).
In any case, we’re not providing enough information in these errors to communicate that there’s potentially a replication race condition, as opposed to the object not existing (ever).