How could I prevent a remote from being not fired or getting deleted.
If you can’t answer this topic refrain from posting on it, please!
I have seen this interesting concept of sending a GUID over to the client every second and making the client send it back, this works because the client could not predict the GUID before it gets sent over from the server ( i forgot were this post was if someone could link it ).
Could you give some context in what your asking this in regards to? For example do you mean server side or client side, why would it get deleted in the first place and things such as that.
What’s this for? Is it a part of another system or is it standalone? Because if it is, it’s just wasting bandwidth and not exactly achieving anything…
If you can’t answer this topic refrain from posting on it, please!
Ok so first,
Don’t be rude. We are here to help you, if you rather someone not asking questions to assist you then I don’t think the DevForum is what you are looking for. If you don’t clearly write your post then of course people are going to ask questions about the post.
The way you have written up the method makes it seem like this is an example method that you have seen (not you asking how to do this method).
Your method does not even make any sense? How would what you are saying stop a remote event from being deleted? You could explain how the method your looking at works a bit more before claiming you have said everything in that one message.
This method is very popular, sending GUID to the client and the client sends it back, if not received or the GUID is incorrect kick the player from the server.
( i’ve seen someone use this before but can’t locate the source )
Would you not then just generate a random number (or letters or what ever you want your ID to contain) then just send that to the client and create some type of code client side to send it back. I am not to sure why you would need an opensource thing to do that. There is even a function called :GenerateGUID() in the https service you could use.
I personally don’t see much point towards doing this because someone could just remove code (for example a client side anti exploit) but just keep the code that returns back the GUID so what would the point of checking if the remote event is deleted or not.
Yes the :GenerateGUID() function is what I have been talking about.
This just a waste of bandwidth. You shouldn’t be trying to secure your events, but instead try to prevent them from being exploited.
no,
problem solved.
9-()(*HNDN
It doesn’t guarantee anything though, there’s a plethora of ways that a client can send a valid return message even if they delete the event or disable your script.
I hope this is just for practice or something, because if you guys spent as much time on proper server security as you did trying to find theoretical ways to handle client security, you wouldn’t need the client security to begin with.
they could easily set up their own .OnClientEvent event and send it back 
then the remote is still there lmao if there sending it back then the remote still exists.
and i want is the remote to still exist
they could hook your localscript’s :FireServer() to do nothing and then set up their own to always send it back
NEVER trust the client.
They have access to do anything with your local-scripts and modules required by one, it would be very easy to bypass your security.
won’t be easy to bypass if the dev knows what they’re doing.
It is inevitable; exploiters have full control over their client.
I believe you will understand when you dive deeper into this.
they can just disable the onclientevent set up by the developer then set up their own, now they have full control over the remote
I literally said that lol [char limit]
nope not possible
lol
dwdad[d
]DW}AD{