ReplicatedFirst does not replicate first

Bug Reports Engine Bugs
,
1

Code in ReplicatedFirst is not guaranteed to run immediately, sometimes having delays upwards of 30-60 seconds before anything runs. This causes problems for the user (more or less, depending on what is placed under this service) because of seemingly long loading times.

In my case, I place a lot of client code in ReplicatedFirst, including interface. Users can see the effects of this problem by having UI not loading for a long period. Because of this problem, our game (Slap Battles) takes a hit to retention and engagement due to a high-friction onboarding.

I consider this to be a pressing issue and I’m hoping it gets fixed as soon as possible.

Expected behavior

I expect anything in ReplicatedFirst to run, well, first. This means it should be much faster than StarterPlayerScripts. This is also critical since I have code that attempts to run regardless of character loading.

5 Likes
2

Thanks for the report! We’ll follow up when we have an update for you.

1 Like
3

Cannot reproduce this. Putting a local script in ReplicatedFirst and into StarterPlayerScripts causes the scripts to fire on ReplicatedFirst and then StarterPlayerScripts at a later time.

If you can still reproduce this issue, please file a new ticket with a reproducing place file attached!