For security I want to make fake remote events that would instantly ban exploiters, but I don’t know how much I should put without causing performance issues, will 300 be too much for server to handle?
Why would you need 300? Just make like 10 fake remotes and have 1 real one imo.
I’m talking about all the remote events in the game, I want fake ones to be more common, the game will have more than 1 real remote event, I’ll try to minimize amount of remotes but my problem rn is performance
What I do is have 1 remote event and use a string to tell the server what function I want. More than 10 fake events is fine but I think 300 is overkill.
There are multiple different remote listeners in the game and if they all listen for same remote it might cost a lot of performance as most of these listeners will ignore the functions, making their listen useless
AFAIK, exploiters don’t just ‘see’ the RemoteEvents. It would be pretty simple to see which ones were actually in use, which would defeat the purpose.
2 Likes
My goal is to rename the remotes in similar names, like E1034, E1035, etc… and then if the exploiter runs the wrong remote he will be perm banned, and then I would switch the real and fake remotes eventually so they would have to search for the real remotes again, having more remotes banning their accounts could make it difficult for them
Making hundreds of fake remote events is not an ideal way of dealing with exploiters. Just make your server more secure on the remote even that you actually use.
There is no point in making 300 remote events. A dedicated exploiter can figure out which remote event to fire.
The reason you would consider doing something like this is to counter script kiddies however this is a terrible way of dealing with them. A secure server doesn’t need hundreds of false remote events.
Don’t make hundreds of remote events and create a system that manages them. Just use sanity checks on the server.
7 Likes
hackers can see what remote is the real its called “Remote Spy”
you could do a function which asks the server to return a temporary code, code which will be generated and sent only if the server detects that the parameters correspond to what you want, then the client can call the event with the code, if the code is valid the event is running. You can also check directly in the event
I believe listening for 300 remotes will cause tons of performance issues. Try to keep it between 10-20. I think this is a really good idea, but you don’t need so many remotes.
That’s what I thought, sending a code as a confirmation method and check if data is valid on server, if data invalid the client will be kicked for giving invalid data