Every now and then I browse v3rmillion.net for any major things, like FE bypass or explorer scripts and try to patch them in my games.
Recently, I found an FE bypass script that literally just disabled FE, as if someone just unchecked it with a RemoteEvent. I wont post the script here for hopefully obvious reasons, but is there a way to fight against this type of FE bypass?
I tried it with this script inside of the Workspace:
while true do
wait()
if script.Parent.FilteringEnabled == false then
script.Parent.FilteringEnabled = true
end
end
and I was going to add more than that, like a backup in case someone with an explorer exploit deleted the script, it would just paste it back in. (In case they do disable FE)
But when I tried this method, I got the error "Unable to assign property FilteringEnabled. Script write access is restricted"
Anyway to bypass this?
6 comments
I am scared of hackers now if this is true... but anyways I think that if they game is checking for that 30 times a second it will lag out bad.
You cannot. It is LocalUserSecurity, which means it can ONLY be changed in studio or the command bar in studio. Otherwise, if you saw this in YOUR game, see https://devforum.roblox.com/t/recent-roblox-security-incident/53277
Thanks for the help, hiimgoodpack. and @goldstorm950, it would not lag the game like that :P
@goldstorm950 That's like a breeze for your computer.
The thing that you recently saw was a joke. There is no such thing as a remote that disables FE. I would recommend avoiding those types of threads as they are often false.
Even if it was a joke, there are still FE bypass scripts that people should look out for. So I'd rather not avoid those threads