Detections

Server Detections

This part of the Wiki details all Server-sided Detections in detail.

Magnitude Detection

Magnitude Detection compares previous position values from the HumanoidRootPart and checks if they are above a certian threshold within a specific amount of time, which can be set in Data, if this threshold is exceeded, the Player will be warned (Or kicked if Warnings is disabled).

Important

Make sure you have WhitelistedStates set up! As Magnitude Detection checks for abnormal Humanoid States before kicking a Player, this will be toggleable in the future

Humanoid Detection

Humanoid Detection checks if the new Humanoid State has changed to anything not Whitelisted or PlatformStanding, and then kicks the Player. You can configure the Whitelist in Data.

Important

The WhitelistedStates Table only accepts number values, please check out Roblox's Humanoid State Types

Note

PlatformStanding, aka State 14 is blocked by default, as PlatformStanding is used allot for flight exploits. You can disable it by setting CheckPlatformStanding to false in Data.

Client Detections

This part of the Wiki details all Client-sided Detections in detail.

Btools Detection

Btools Detection attempts to find F3x's Btools in the Player's Backpack and Character

Warning

Btools Detecion tends to be a unreliable, it may not Initialize first try.

Gui Detection

Gui Detection compares Gui's within the Player's PlayerGui with Gui's within StarterGui or checks for specific Gui Names, if a Gui is not in StarterGui or not named exactly the same as on the whitelist in Data, the Player will be warned (Or kicked if Warnings is disabled).

Caution

GuiDetection is NOT RECOMMENDED to be used UNDER ANY CIRCUMSTANCES. This can cause a lot of false positives, and a lot of innocent Players to be kicked or warned. Only use if your Game has strict Gui enforcements!

Noclip Detection

Noclip Detection is highly customizable, please check out Data for Noclip Settings, and always test properly so the Raycasting settings match your game!

Aggressive Mode

AggressiveMode as the name implies, is a lot more aggressive then regular Raycasting checks, it checks if the HumanoidRootPart has CanColide enabled. If it is disabled, the Player will be kicked. This feature can be enabled by setting AggressiveCharacterValidation to true within the Loader's Data ModuleScript.

Tip

Raycasting checks do not get disabled if AggressiveMode is enabled

Raycasting

Noclip Detection uses Raycasting by default, please check out the Data page for Noclip Detection on our Wiki to learn more!

Dex Detection

Dex Detection targets the basic Dex Explorer Script, and kicks a Player if they are caught. Special thanks to @devomebtnac for the Dex Detection methood, check out the Anticheat's Credits in its README file.

Note

This Detection won't work on any executors with a functioning cloneref (If they are running a version with cloneref)

Warning

This can cause false positives if you're Client Gets and Stores random objects in game.Chat OR Gets and Stores all of game:GetDescendants()

AWP Injection Detection

Caution

AWP Detection is deprecated, and will be removed in the future.

Targets the AWP Executor and tries to check if it was injected into the Client, by targeting getfenv timing flaws. If there is a timing flaw, it will be added to the violations counter. And yes, AWP can literally be detected by a localscript.

Detection Ratio

This was taken directly from @devomebtnac DevForum post, please check out the Anticheat's Credits in its README file, the Ratio will be shared in the Moderator Message

-- ratio stats:
-- avg 12.5, avg range 11.5-13.5, 98% ~17.5
-- awp averages about 31, so the difference is more than enough

-- we use a ratio so that slow pcs arent punished for being slow,
-- instead comparing execution time between a base test and getfenv

Note

AWP Injection Detection is disabled in the Studio environment