I have seen many developers use object remote events, as well as instanced remote events for organization.
I have been very curious on what everybody uses or recommends. Remote events in replicated storage stack up a lot even with folders.
Do you use objects? or do you instance them the more skilled you become at scripting and organizing
I have them inside a folder in Replicated Storage so both the server and client can access it.
It has nothing to do with organization.
It’s an instance used for cross client-server communication.
It’s a very essential part for communication, but be very careful using it and read all safety cautions regarding it.
does it get messy if you need a significant amount of remote events?
If you keep them in one place and name them in a way that let’s you find them again easily then you’re good to go
What do you mean by object and instanced remote events? Remote events that are defined in the explorer vs ones created at runtime..?
I watched a video on someone who used a module script remote event to only have a few for his whole game just wondering if that’s actually a good way
I did a basic benchmark (“ping-ponging” RemoteEvents with no data back and forth) of 100 RemoteEvents firing vs 1 RemoteEvent firing 100 times (with an ID number) and the 100 RemoteEvents used far less bandwidth, even when compressing the ID to a single-char string.
So, there’s the important answer. Multiple RemoteEvents win in terms of per-message overhead.
Edit: To avoid bias in messaging speed, I also tested sending 100 empty messages every resumption cycle (i.e., task.wait()) from client-to-server-to-client. The same results were experienced, with 100 remotes having less overhead.
Yes, it can, in the project im working on rn its hard to fi d specifics. I guess the solution is to make another folder. I’ve never tried instancing them, it may be more organised.