This is really just a question, rather any “scripting support”, but this fits best in this category because I will want to make an anti-cheat, on a script, of course.
Are exploiters able to change theirAssemblyLinearVelocity, orAssemblyAngularVelocity?
I suppose how exploiters fling others is making their angular velocity set to an absurd number, or something.
They can change as long as you do nothing about it. But it will only replicate on the exploiter’s computer. It won’t reflect on the server. Also, whenever the exploiter changes the script of another player, it just changes on his screen; it doesn’t affect the other players or server (if the network ownership of the script or other player’s character isn’t given to the exploiter). If NetworkOwnership of the object is not on the exploiter, then he can just change its properties by himself. If NetworkOwnership of the object is on the exploiter, then it will affect the other players too, but it won’t be seen by the server.
Yeah but don’t try to pass information to the server with remote event otherwise exploiters can use that remote event in their purpose. you can’t prevent exploiters from your game completely as you know but you can make advanced anti-hack system to be more protective.
If you can calculate maximum rotation speed of player can reach with built-in forces or scripts, you can check RootPart.Orientation and if Rotation speed more than desired value then you can kick or ban exploiter.
EDIT: every way is correct to do if exploiter cannot access the anti-hack and deceive the anti-hack system
local old = nil
game.Players.PlayerAdded:Connect(function(player)
player.CharacterAdded:Connect(function(character)
character.HumanoidRootPart:GetPropertyChangedSignal("Orientation"):Connect(function()
if old == nil then old = character.HumanoidRootPart.Orientation return end
print((character.HumanoidRootPart.Orientation-old).Magnitude)
end)
end)
end)
Yeah it is, but careful that exploiters can’t change properties. You can think various methods of making an anti-cheat. It is related what you trying to do.
EDIT: If this script is created within a server script, it will not work as intended. This is due to the fact that exploiters are unable to pass information to the server unless there is a remote event. If you use a remote event from the local script to send orientation data to the server, exploiter can change the data. The challenging section begins at this point. You need to pay attention to the parameters being sent from the local script and check whether an exploiter is sending them or not.