Proper Filtering Enabled workflow

Hello,
I’ve recently been getting back into development on ROBLOX and as times and methods have changed I am asking the community for any tips or tricks regarding filtering enabled. For example, I have been debating between using two different workflows, but i’m not sure which would run most efficiently. i.e. would it be better to have a remote event/function for each individual call or rather have a single remote event and function?

any info about FE and how remote events and functions interact between the client and server is appreciated

• It is always better to have different remote events/functions over cramming all of your requests through a single remote function (There is a hard 50 kbps limit when sending data from the client to the server, and referencing a different Instance in game is a lot cheaper than passing extra arguments to tell the server what you’re doing).
• You should never call RemoteFunction:InvokeClient() as an exploiter could cause the function call to yield indefinitely.
• The client can delete any Instance parented to their character and the server will happily replicate this (do not store anything critical in the character).
• Unanchored parts can be controlled by a nearby player (if the player has network ownership of the part), allowing an exploiter to fling the part or pretty much delete it.

4 Likes