Like im curious how it works compared to like how a RemoteEvent would work if you were to send the same information about a child that was added to a parent, like I feel like built in replication is faster than if you were to use a remote event but im not certain though because I don’t know how ChildAdded and ChildRemoved work in the backend if that makes sense
If my experience with replication is correct, every replication runs technically before any RemoteEvent. Things like Tool.Equipped run before recieving a called event after firing it on Tool.Equipped in client. I’m not 100% sure everything does work like that though.
2 Likes
Hm yeah I think that events like ChildAdded and ChildRemoved are handled by the roblox engine internally and are faster than RemoteEvents because Remotes add another lay of communcation which of course can lead too more noticable latency and stuff
You can mark my answer as a solution then.
We don’t have to guess what it does (but yes you are correct). The task scheduler priority order is as follows (taken from the docs at Task Scheduler | Documentation - Roblox Creator Hub):
2 Likes
Never seen that article, reading straight away, thank you!
1 Like
BRO THAYT IS EXACLTY WHAT I WAS NEEDING THANK YOU
charrrsdfvegc
1 Like
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.