I am creating a anti-exploit for one of my games currently but I have this issue. I have a feeling it is because I have Filtering Enabled but I am not that sure.
Here is a part of my script that checks for a added forcefield
-- Checks for a added ForceField,
game.Players.LocalPlayer.Character.ChildAdded:connect(function(obj)
if (obj:IsA("ForceField")) then
if (obj.Parent == game.Players.LocalPlayer.Character) then
obj:Destroy()
end
end
end)
Also, I am doing a fire script as well!
game.Players.LocalPlayer.Character.ChildAdded:connect(function(obj)
if (obj:IsA("Fire")) then
if (obj.Parent == game.Players.LocalPlayer.Character) then
obj:Destroy()
end
end
end)
It would be appreciated for someone to help with this problem! Once I get the answer, I'll confirm it! Also, I would love some tips on how to avoid problems like these if you can give some!

2 comments
Could you give us the warning it gives? Also you can combine those two scripts.
I did combine both of them! Here is the output: Something unexpectedly tried to set the parent of ForceField to NULL while trying to set the parent of ForceField. Current parent is Player1.