If any BodyForce is inside or added to the character, it sends a message to the server using a RemoteFunction to check whether or not the force exists on the server. What I did as a solution was to locally check the character for any descendants added, and also scan the character every small amount of time to check for BodyForces. The assistance of body forces is what actually ends up being the problem. As I have tested, the fast rotation of the body alone does not usually cause flinging. What I found was that using orientation of the character is extremely unreliable as a normal user can rotate themselves at very high speeds with relative ease. Problems while creating the anti-exploit.Īlmost all “spin fling” exploits I have seen use Body objects.
Sorry I know this is an old topic, but I feel that I need to clarify how I finally ended up solving it.
0 kommentar(er)
