How would i prevent remote hooking so exploiters don’t make my remote events/remote functions infinitely yield.
They can’t yield remote events even if they tried to and in order for exploiters to yield remote functions you will have to invoke their client by using :InvokeClient() which normally shouldn’t be used in the first place.
If what you’re talking about is hijacking the remotes to exploit, then you should just do sanity checks on server.
That was literally a script from v3rmillion you saw it which would have meant you saw the yielding part
As I said, unless you’re using :InvokeClient(), they can’t yield the code, they can return something else but that’s what sanity checks are for.
Also I saw that code with __namecall metamethod in it, whatever that code was, don’t use that metamethod
Exploiters can intercept pretty much anything that happens on the client.
If you saw the code then that means you would have seen the part which yielded it for 9e11 seconds
Not really, you removed the code before I was able to read it all
Okay but now you know that it does yield it for 9e11 seconds
They can but that doesn’t mean they can yield serverside with remote events because that would make no sense. They can possibly yield serverside if server used :InvokeClient() function but that’s pretty much the only way to yield it.
But they can yield it your underestimating the client and trusting it not to hook the remotes
If they can yield your code by using remotes then there is definitely something wrong with your code in the way you written it.
Also it can’t be yielded for 9e11 seconds because that equals to about 28538 calendar years, are you sure you got the number right?
yes im sure i got that number right because it was literally on v3rmillion and yes they can yield it for that long you can yield a script for aslong as you want they may not wait out 28538 years but they will definately stay in the game with that remote yielded forever
Exploiters can only yield the server if the server invokes the client via RemoteFunction Instance
Otherwise what the exploiter is yielding is probably the client its self through a BindableFunction or anything that runs on the main thread (non-os thread) in the client
Or the game being affected by the exploit is poorly coded and vulnerable and the code specified may not behave the same way on your game.
Really doubt that if they can get the remote calls then they could probably yield it without any poorly coded things inside your game
I assume you’re referring to exploiters hooking FireServer to turn certain remote calls (ex. ban ones) into wait(9e9).
In short, you can’t prevent that.
What you can do is have proper sanity checks on the server, so that they can’t spoil the gameplay for other players. Blocking a remote usually doesn’t affect the others, unless its purpose is to reset a state like safe zone god mode, in which case you should be handling it on the server.
1 Like
Alright thanks famous v3rmillion hackerman but if thats the case then how did that strucid patch that one anticheat bypass script that i saw on v3rm that used remote hooking.
I recommend you to use an anti-exploit script I’ll paste one here soon
I already patched almost all the stuff in that script that you posted that isn’t rc7 or random stuff that an exploiter could just use rconsole for the print checks.
anyone can use the console though
Im talking about rconsole the function that synapse has which has a custom console