Can a RemoteEvent get overloaded?

Join Date: 2014-04-19
Post Count: 2571

#182952622Wednesday, February 03, 2016 11:07 PM GMT

I'm sending data (a small int value, 1-100) to every client every .2 seconds, the maximum amount of clients in the server is 30. Would this be too much for a RemoteEvent? Is there a limit?

Roblok1

Join Date: 2011-07-27
Post Count: 2019

#182953512Wednesday, February 03, 2016 11:23 PM GMT

yes, events can be overloaded. but the number of times you can fire an event is usually pretty high. so unless the event is being called in a loop, it should be fine.

morashsPeasant

Join Date: 2011-01-06
Post Count: 4944

#182953884Wednesday, February 03, 2016 11:28 PM GMT

You should create an IntValue object in Replicated Storage dedicated to the player and on the player's side, use the .Changed event to detect changes on the int value. Remember to delete a players value when they leave :D

sayhisam1

Join Date: 2009-11-25
Post Count: 2092

#182954839Wednesday, February 03, 2016 11:43 PM GMT

@morash that opens up a veryyy large number of security holes. For one, I can simply change the value of the IntValue if I wanted to. RemoteEvents are much more secure. And instead of using IntValues, just store it in a local _G key if the value isn't very important. IntValues are laggier than using a _G value, since you have to actually create a new instance, set its parent to replicated storage, etc. Whereas _G is simply table manipulation.

morashsPeasant

Join Date: 2011-01-06
Post Count: 4944

#182960511Thursday, February 04, 2016 1:04 AM GMT

lol Filtering Enabled ...

FrostOver

Join Date: 2013-06-20
Post Count: 299

#182960782Thursday, February 04, 2016 1:09 AM GMT

you can still edit the client with filtering enabled

morashsPeasant

Join Date: 2011-01-06
Post Count: 4944

#182960921Thursday, February 04, 2016 1:11 AM GMT

sigh.. He is SENDING the data from the SERVER to the client, not the other way around (which wouldn't work). Forget what I said about creating a value for every player, I thought you were sending individual values every .2 seconds. When there is 1 value, being sent to all the players, making ONE IntValue object in the server is better.. instead of firing all clients every .2 seconds.. (im pretty sure)