If Obj.Name:lower():find("dex") or Obj.Name:lower():find("hub") thenįor _,Obj in ipairs(Gui:GetDescendants()) do - checks gui's descendant's name for odd thingsĬoroutine.resume(coroutine.create(function() If Gui.Name:lower():find("dex") or Gui.Name:lower():find("hub") then - checks gui's name for odd thingsįor _,Obj in ipairs(Gui:GetChildren()) do - checks gui's children's name for odd things :Connect(function(Gui) - runs callback function if a gui is added to playergui Local function ReportToServer(Type : string, Args) - creates a function to report odd behaviour to the server using the FireServer function we got earlierĪntiTamperRemote.Parent = ReplicatedStorage - parents the remote to ReplicatedStorage so the messages can be sent to the serverįireServer(AntiTamperRemote, Type, Args) - calls the FireServer functionĪntiTamperRemote.Parent = Instance.new("FunctionalTest") - reparents the remote to somewhere dex and getnilinstances() can't see Local LastHistoryLength - creates a variable for the last length of the log history tableĭo Not Edit This Script Unless You Know What You're Doing.įor _,Instance in ipairs(BlacklistedInstances:GetChildren()) do - loops through all the instances in the blacklisted folderīlacklist = true - inserts the instance's classname into the blacklist tableĪntiTamperFolder:Destroy() - destroys the AntiTamper folder so the exploiter doesn't know it's in the game and also to stop false flags from the instances in the blacklisted folder Local Blacklist = - creates a table for blacklisted instances Local FireServer = AntiTamperRemote.FireServer - gets the funciton to fire to the server to avoid _namecall hook detection used to spy on remotes _index hooks are less common for remote spies Local AntiTamperRemote = ReplicatedStorage:WaitForChild("AntiTamperRemote") - grabs the AntiTamperRemote from ReplicatedStorageĪntiTamperRemote.Parent = Instance.new("FunctionalTest") - parents the RemoteEvent to somewhere dex and getnilinstances() can't see or call it from Local LogService = game:GetService("LogService") - gets log server for detected if an exploiter calls the error() function Local ReplicatedStorage = game:GetService("ReplicatedStorage") - gets ReplicatedStorage for the remote Local BlacklistedInstances = AntiTamperFolder.BlacklistedInstances - gets the blacklisted folder so it's ready to be deleted Local Player = game:GetService("Players").LocalPlayer Local AntiTamperFolder = game:GetService("ReplicatedFirst").AntiTamperClient - gets the AntiTamperFolder so it's ready to be deleted when everything is set up TamperingDetecter script.Parent = Instance.new("FunctionalTest") - parents the localscript to somewhere dex and getnilinstances() can't see Here’s the code for those who are curious. I only skimmed the code as reading any further made my head hurt, so forgive me if I misread a thing or two. Parenting it to the “untouchable” FunctionalTest is redundant. The TamperingDetecter script could be obtained by using getscripts (or whatever it’s called) and calling Destroy on it would halt it.Error message generated by developers would trigger this anti cheat.Wouldn’t it be a better idea to limit the detection to the character instead of the whole game? A lot of games use these specific Instances:.How does FunctionalTest bypass getnilinstances?.(sorry about the outdated method that I used to use to hide scripts from getnilinstances() and dex executor devs found out)ītw please read the README script to avoid the system breakingĮnjoy! (also working on some other cool things and sorry if it’s a bit unoptimized) You can easily change what Instances are blacklisted by simply remove or adding the instance to the BlacklistedInstance folder on the client, yes I do know that this can be bypassed but it does make your game harder to exploit also I do know that most exploits put their gui in CoreGui but the playergui detection is to purely detect free executors and people who simply forgot to parent their gui to CoreGui If any executor other than synapse calls the error() function for some reasonĪ list of blacklisted instances which you can changeĮxploiters putting exploit guis into PlayerGui (kinda)Īnd a few other things that I won’t list for the purpose of detecting more noobs Hello this is a funny little system that I made which makes exploiting games that one more bit a teeny bit harder.Įxploit scripts possibly infinite yielding
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |