Please give developers an option to toggle this replication I'd rather deal with handling latency and creating a smooth experience myself than have to worry about things I cannot control. From my experience and testing, clients have control over HumanoidStateTypes ( Humanoid:SetStateEnabled() and such) as well as the Humanoid.Sit and Humanoid.Jump properties. Keep in mind, this is all with FilteringEnabled. It's easy for developers to overcome this by creating their own jumping, but they shouldn't have to do this to avoid something that's not in their control. The only alternative now is to create characters without Humanoids because of how exploitable Humanoids (or the Player.Character property, again, haven't tested) are.Īnother exploit that comes to mind is the flying exploit where a player seats themselves and spams jump to hover. I understand that this is so that clients have smoother control, but I think this is something that developers should at least be able to toggle. Unfortunately, most (not sure if all, haven't tested) HumanoidStateTypes are fully controlled by the client which I think is giving too much power to the clients. I'm not trying to promote exploiting, so I won't state which Enum it is, but if you know a good deal about scripting (or know how to google) you'll know which HumanoidState I'm talking about. Though I don't know what program they use and what script they execute, assuming faith in ROBLOX's security (that is, assuming that this is something they overlooked and not something that they failed to protect) I believe no clipping is done by manipulating a certain HumanoidStateType. I'm sure there are other exploits I'm not aware of but an exploit that I've recently experienced myself was no clipping.

Easy noclip roblox