🎥 Client Side Checks
And here we are, ready to delve into some hardcore client-side detections.
note
Client-Side Detections: These detections are excellent for gathering information about potential cheaters, but they can also result in more false bans than server-side connections. Additionally, they are more susceptible to bypassing by advanced cheaters.
Here are some detections that you should understand, and they may be a bit complex to set up.
PegasusAC | Explanation | Important To Know |
---|---|---|
Anti Spawn Cars/objects/Peds/Pickups | This detection works as follows: it monitors all the spawns that a user initiates and detects if they are originating from an unknown resource (e.g., an executor). | Attention: Please be aware that this is a client-side configuration. It is not a secure substitute for server-side spawn protection. |
Anti AntiCheat stop | To achieve comprehensive protection, you should take two steps. First, set this variable to 'true.' However, the most critical step is to enable AC Protection in the server console using the command 'pegasus -help.' | Attention: Please note that the resource in which you install the anti-cheat protection should be added to the 'ResourcesToCheck' variable. |
ProtectPlayers | I recommend enabling that feature. | Attention: It's highly recommended to set explosion damage to 'true' as it's crucial for protecting your players from explosion damage. |
AntiInvisible | Invisibility will be triggered after 10 seconds of being invisible. This delay is in place to accommodate certain scripts that use invisibility for spawning or changing clothes effects, such as vMenu. | Attention: - |
AntiVision | This detection will remain off for emergency vehicles that use vision cameras and similar features. | Attention: Exercise caution when using scripts that involve vision effects. |
DUITextures | If you know what you're doing, you can make additions to that table. If not, it's fine to leave it as it is. | Attention: It's unlikely that this detection will result in a false ban. |
ClientHoneypotPunishment | Here, you can list events that you are NOT using. You can identify potential cheat usage by monitoring this list. | Attention: Ensure that you are not actively using the events you add to this table, as using them could lead to false bans. |
BlackListDictionary | Hey, this will detect whether a dictionary is active. | Attention: Keep in mind that some menus you are using might utilize items from these dictionaries, potentially causing false bans. If you encounter any issues, consider removing the conflicting items. |
AntiWeaponSpawn | To install that, you should set it to 'true' and then execute the 'install_weaponprotection' command from the Pegasus console. | Attention: If you have a script that is not written in Lua or is obfuscated and provides weapons to players, be cautious as it may trigger false bans. |
ScreenChecker | This detection will utilize 'transeract' to scan the client's screen for any words. If it detects any blacklisted words, it will take punitive action against the player. For example, if the word 'fuck' appears on the screen and it originates from a Lua menu, the player will be penalized. | Attention: Exercise caution when including short words in the blacklist table, as they may lead to occasional false bans. Additionally, enabling this detection can potentially cause lag in your server. It's advisable to test it thoroughly before implementing it. |