It says that it doesn’t seem to be used there, but a lot of No-Clip exploits that I see are always setting the players state to 11, so I’ve set my game to autoban anyone who reaches this apparently unreachable state.
Anybody know if this state type can actually occur through normal means? Some players claim to have it happen via flinging but I’m pretty sure they’re just lying about it to get unbanned.
Which is probably due to the fact that the state isn’t calculating anything.
it’s supposed to just switch back to normal on the next physics step, but obviously something is going wrong as your example demonstrates.
I’m not 100% sure if this state is actually triggered by legitimate means in practice. We’d have to ask someone like @anon59103962 who works on the Humanoid.
I checked your profile to see what game you were talking about, and apparently you have a game with 1,871 people playing it (and counting), 230 visits (this isn’t increasing), and no servers.
Did you do this, or has Roblox messed up?
Anyway, if your game is already popular, instead of banning for being in state 11 you create a log.
Every time a player enters state 11, you record for how long for that session they have been in state 11.
Every time a player disconnects from the server, you add 1 to a particular value in a datastore, that value determined by how long they have been in state 11.
When you analyse the data, you should be able to determine whether to ban people for being in state 11.
If the state can occur naturally, there should be plenty of people who have been in state 11 for less than 5 seconds.
I’ll consider the idea of a counter activating whilst players are in state 11, this should fix random flukes with humanoids accidentally getting set to this state by whatever glitch.
That’ll only help with exploiters who don’t know how to script.
By the time the server registers the state change, the player has already had about 100ms of noclip time, and they can resume noclipping instantly with a script.