Separate Remote Event for Each Client?

[inoobe_xi]

I remember someone said that giving each player their own remote event would cause less latency. I want to use this in my new game, but before I do, I just want to know if it will really make a difference.

[ScottyMcPiper]

This will not make a difference. Having your remote events in ReplicatedStorage is fine, as all clients will see the event the same way, just as if the event were in the starter pack. Plus, it’s easier for organization to have them in ReplicatedStorage.

[Operatik]

I don’t see any problem with separate remotes. This could work and does not make any difference.

The only difference is organization as previously mentioned by @ScottyMcPiper. I usually favor the practice of placing remotes inside the ReplicatedStorage. Follow up by writing the scripts with game:GetService("ReplicatedStorage"), and from there, get the remote(s) you want to use to fire and receive signals from.

[gullet]

Doesn’t seem like that’s what he was asking. As for having separate events per player I doubt you’d see any measurable difference. Unless the exhaust queue is not global there will be no difference. If it is, it would be extremely slight at best, unless you’re actually over the limit. Unless having separate events makes the structure more clear in your game, I don’t think it would help, if anything it would make it messier.

[colbert2677 (ThisMangaOnHiatus)]

A thread was made about this issue before, have you taken a look at it?

Is there any difference in performance between one single RemoteEvent for all players or a RemoteEvent for each player?

Generally if I have a particular event that every player will generate, I create one remote event and one script to handle all the remote events being received from every player. It seems more straightforward and more elegant. But then I got thinking, and this may be a stupid question, but could players see a quicker response on the server to the event they created if they each had their own separate remote event? Can a remote event get “bogged down” if receiving multiple requests from multiple …

Separate remotes does have a performance difference, however you should be careful if you decide to take that approach. It can lead to spaghetti code and bad habits. Having remotes set up in ReplicatedStorage is maintainable and if you handle your code right, you can also prevent various issues such as performance hits and request throttling.