I was told to not create a new bug report, so I have edited this one with the contents of the duplicate one.
All messages above, excluding the initial message, may be ignored.
This is a practice many people do, as PlayerGui is the only way to replicate an instance to specific players. Because instances parented to nil cannot be sent through remotes, while PersistentPerPlayer could be used that only covers Models and also relys on Streaming.
You can put instances in ServerStorage and instantiate them per player from there.
We are moving towards streaming more and more, which conflict with the idea of a big datablob that gets streamed on load to every player.
I want to make clear that my bug report is not about the previous conversation.
My bug report is about PlayerGui not being cloned/replicated into PlayerGui under certain conditions, with StarterGui/PlayerGui only having 3 descendants.
@catinpsyop Thanks for the report. Could you please re-iterate the issue that you’re encountering one more time? The context may have gotten mixed up in this thread’s history.
The latest edit of the main post is up to date, but I’ll reiterate it shortly here:
If ReplicatedFirst has a lot of (script?) data, contents of StarterGui will never be replicated to PlayerGui on first character load.
The StarterGui contents appears to have been cloned to PlayerGui in server view.
