You’re explanation makes a lot more since. But my main goal is to at least disable the free executors. But also I didn’t know of getnilinstances()
until now.
It’s always easy to disable free executors; when you’re dealing with individuals looking through every feature Synapse X or other executors has though, that’s when everything becomes a pain.
Agreed, that’s why I wanted to mix both this module and overall good remote practices cause it makes more since to disable most, and then mitigate.
Server sanity checks will always be the best deterrent for exploits. Bypass methods will be made by exploiters for every other method. Obfuscation/hiding objects won’t make a difference.
Most of us can’t wait for Roblox to make a move on exploiters with anti exploit detection on the actual client. They’re taking their time.
how exactly do you send messages to the server using this module?
I would say its a temporary solution. While it can stop starter exploiters, someone else will just hook __namecall metamethod and get the remote instance or simply filter nil instances using ClassName if you only got 1 remote.
-- Get Unsigned Module
local Unsigned = require(path.to.Unsigned)
-- Get Event
local Event_Object = game.ReplicatedStorage:WaitForChild("Event")
-- Create UnsignedEvent object
local Event = Unsigned:AddEvent(Event_Object)
-- Initialize Unsigned
Unsigned:Init()
-- Fire Away!
Event:FireServer() -- You can also put any arguments inside.
For more information, please check the docs.
You should extend this to ModuleScripts
KRNL, A free roblox exploit executor, has getnilinstances. its not as uncommon as you think. Parenting it to nil wont do a thing.
Just about every executor out there has support for that. Most implementations of Remote Spy override the namecall function which we use to fire remote events. Unsigned’s backup solution is randomising object names (and possibly modifying the contents of getfenv()
) to make it difficult to discern which remotes are being called to achieve which means. This is quite similar to what Pls Donate does by the way.
Also, I believe Synapse X has an auto-run feature where it runs a script as soon as it can (joining in). I believe this “anti-cheat” changes it just a bit after the local scripts can create a variable for the events, so I’m not sure how this would work…
Please don’t use this. It won’t help.
There is an error with the module, i dont recommend this at all.
what’s the point? the reparenting can be bypassed using getnilinstances()
, hookmetamethod()
, the best way to protect your remotes is by adding sanity checks in the server, GUI Detection is impossible as you can draw the GUI to the screen, which makes it impossible to detect, It’s coded a bit unefficiently
im not an exploiter, I just get the information from the replies, please private message me if i’m spreading misinformation