Configuration

1. How do I configure the anticheat??

The resource comes pre-configured with our recommended settings, so in most cases you won't need to change anything. At first, you only need to update the following fields: Config.DiscordServer, Webhooks, Config.AccessMenuIds, Config.SendPlayerLogWithVideo (we recommend this to be set on true, but only if you want to) and Config.FrameworkAntiWeaponsCheck

2. Do I have to pay for anticheat configuration to Reason Anticheat team or to other people?

No. You never need to pay anyone to configure the anticheat.
In almost all cases, the default configuration is the best configuration (only change values when you have a valid reason). If you need help, check the documentation for each field below or open a ticket on our discord server

Config

The configuration file can be found in config folder of anticheat resource named config.lua. Inside the config file you can set values or actions for every feature of anticheat. Down spredbelow, each feature will be detailed with more details about each feature even though there entiare instructions in the config file. Copy and find in the config file the feature you need to adjustse

Anti stop resource

The anti stop resource will prevent player to stop the anticheat resource. This feature does NOT exist in config to be set to true or false, as if it was possible to set to false, your server would have been exposed to a very high risk and anticheat will not monitor some cheating actions and we would have been exposed as bad advertisment. Resource stopped means that client lost the tranmission with server and there are only five cases when the client loses the transmission with the server which are:

1. Resource stopped from executor (most common)
2. Host low performance: unstable network (freezings, drops, packet loss, DDOS attacks), lost internet, poor specifications
3. Server low performance: high server resource consumption
4. Player's low pc performance: poor specifications
5. Player's bad internet connection: unstable internet connection, low internet speed

Stopping resource from executor is the most common reason (1). In case all players got kicked for stop resource it means that the server or host has low performance (2) (3). In case only one player got kicked for stop resource it means he stopped the resource from cheat (1) or he has low pc performance or bad internet connection (4) (5), where stop resource is the most common reason. The penalty can be KICK (if the player stops the resource while he is on the server) or BAN (if the player stops the reasource before joining the server)

Commands names

Config.Help, Config.ClearAllCommand, Config.ClearVehiclesCommand, Config.ClearPedsCommand, Config.ClearObjectsCommand, Config.BanListCommand, Config.UnbanCommand, Config.UnbanAllCommand - variables that sets your commands names that you can call from server console in order to perform the right action. For more guidance visit Commands section

Config.SafeGameEnvironment

true: Add extra security to your server environment (more safe then if it is set to false). You need to also add in your server.cfg the following permission: 
add_ace resource.rac command allow

false: Don't allow the anticheat to add extra security to your server

Recommended: true

Config.ScreenshotAPI

Config.ScreenshotAPI - is the API responsible for hosting images captured by the anticheat. If no API is configured, the resource will be unable to upload, store, or retrieve screenshot evidence

In order to create an API on Fivemanage follow the next steps:
1. Visit https://fivemanage.com/
2. Log in / Create an account
3. Go to tokens page
4. Press 'Create new token' button

5. Set a name and type media for the token

6. Copy token

7. Set in config the Config.ScreenshotAPI with "https://api.fivemanage.com/api/v3/file?apiKey=YOUR_TOKEN";

-- Example of token: ABCDEFGHIJKLM123456789
Config.ScreenshotAPI = "https://api.fivemanage.com/api/v3/file?apiKey=ABCDEFGHIJKLM123456789";

Config.SendPlayerLogWithImage

true: The log will include both the player details and the screenshot (available only for some logs)
false: The log will contain text-only information

Recommended: false -> set to false will be faster logs and bans. set to true will just create a screenshot (possible to be irrelevant as the reason of the ban is sufficient) and will take a while to ban until screenshot is being created

Config.SendPlayerLogWithVideo

true: The log will send video of the player when a player gets banned
false: The log will contain text-only information when a player gets banned

Recommended: true -> set to false by default as it will be faster logs and bans, but set to true will send you an evidence on room Config.WebhookBanVideo of the player with latest 60 seconds of his session to see the exact reason of ban in order to not fool you with his excuses in case the player is cheating

Config.SendKillAndDeathsReplay

true: Send video replay of player who killed or died from using command Config.SendKillAndDeathsReplayCommand (default: /racreplay)
false: Do not send video replay of player who killed or died from

Recommended: true -> set to true you can see as killer or victim how you killed or how you have been killed. This feature will help players to catch players they suspect they are cheating by watching a replay of Config.SendKillAndDeathsReplayTime seconds of killer's POV

Config.SendKillAndDeathsReplayAPI

Config.SendKillAndDeathsReplayAPI - is the API responsible for hosting videos captured by the anticheat for replay system. If no API is configured, the resource will be unable to upload, store, or retrieve replay evidence

Config.DiscordServer

Config.DiscordServer - is the discord link invite for your server. This link will appear as hyperlink when someone gets banned and tries to connect to your server. Ban window will tell them to join your discord server and they can create a ticket to get unbanned. Also, it will be shown the Reason Anticheat discord server in case they are interested in our work, but if they join to our discord we cannot handle their ban, because the ban is a local ban (only for your server)

Config.AccessMenuIds

Config.AccessMenuIds - is a table where you can add all player's identifier who will have access to the menu. Is it enough to add only one identifier (license, discord, fivem, xbl, live, steam) in order to grant access to the in game menu. You can find player's identifiers in your database or anticheat logs. Adding your user licenses to access menu table will also make you a whitelisted user. For more guidance visit Menu section

Config.HasUserAccessMenuId

Config.HasUserAccessMenuId - is a function which you can make however you want that will determine if the player has access to the anticheat menu using functions from your server (framework)

Config.TeleportToPlacesMenu

Config.TeleportToPlacesMenu - is a table that contains the names and coordinates of places that can be used in the anticheat menu for teleportation

Config.WhitelistedIds

Config.WhitelistedIds - is a table where you can add all players' identifier who will be protected from almost all anticheat detections (if you use cheat as whitelisted user you can get banned for several reasons. we do not allow cheating at all). Is it enough to add only one identifier (license, discord, fivem, xbl, live, steam) in order to whitelist a player in order to be protected from almost all anticheat detections. You can find player's identifiers in your database or anticheat logs. For more guidance visit Menu section

Config.WhitelistedIds

Config.HasUserWhitelistedId - is a function which you can make however you want that will determine if the player is whitelisted from almost all anticheat detections using functions from your server (framework)

Config.ShowPrints

true: Show prints on server console on different anticheat actions
false: Don't show prints on server console on any anticheat actions

Recommended: true

Config.RockstarId

Config.RockstarId - will force player to have a rockstar (social club) account when he tries to connect to the server if it is set to true. It is recommended to set it to true to force player to own a rockstar (social club) account.
true: Force rockstar (social club) account when player connects to the server
false: Don't force rockstar account when player connects to the server

Recommended: true

Config.SteamId

Config.SteamId - will force player to link his steam account to his fivem account when he tries to connect to the server if it is set to true. It is recommended to set it on false to not force the player to use his steam.
true: Force link steam account to his fivem account when player connects to the server
false: Don't force link steam account to his fivem account when player connects to the server

Recommended: false -> set to false, as players may not understand what or how to do it if it is set to true

Config.SteamIdAge

Config.SteamIdAge - is the minimum age of linked steam account in days if Config.SteamId is set to true 

Config.DiscordId

true: Force link discord account to his fivem account when player connects to the server
false: Don't force link discord account to his fivem account when player connects to the server

Recommended: false -> set to false, as players may not understand what or how to do it if it is set to true

Config.DiscordIdAge

Config.DiscordIdAge - is the minimum age of linked discord account in days if Config.DiscordId is set to true 

Config.MinNameLength

Config.MinNameLength - is a value of the minimum length of player name on player connect. If the player name does not reach this length value, the player cannot connect to the server.

Config.MaxNameLength

Config.MaxNameLength - is a value of the maximum length of player name on player connect. If the player name exceed this length value, the player cannot connect to the server.

Config.AntiBlacklistedNames

true: Don't allow players using blacklisted words from Config.BlacklistedNames table in their name on connecting
false: Allow players also using blacklisted words from Config.BlacklistedNames table in their name on connecting

Recommended: true -> set to true, will not allow players to join with blacklisted words from Config.BlacklistedNames table in names, but by default it is set to false as you may allow all players names on your server

Config.AntiRandomNames

true: Don't allow players using random names from FiveM on connecting
false: Allow players also using random names from FiveM on connecting

Recommended: true -> set to true, will not allow players to join with random names from FiveM (Example: IcyLizard1672, LazyGoose8593), but by default it is set to false as you may allow all players names on your server

Config.AntiSpecialCharactersConnect

true: Don't allow player names with characters different from letters, numbers and normal symbols (keyboard symbols)
false: Allow any name

Recommended: true -> set to true, as players may have names that cannot be found (invisible characters) or impossible to search (non-keyboard symbols)

Config.XSSConnect

true: Don't allow player names that contains special characters, links, harmful expressions
false: Allow any name

Recommended: true -> set to true, as players may have names that can be code execution

Config.AntiEmojiConnect

true: Don't allow player names that contains emoji
false: Allow player names that contains emoji

Recommended: true -> set to true, as they will be impossible to be searched (non-keyboard symbol)

Config.AntiVPN

true: Don't allow players who connect with VPN
false: Allow players who connect with VPN

Recommended: false -> set to false, as maybe is it safer for players to use VPN in online

Config.AntiMultipleSessions

true: Don't allow players to connect/playing with multiple session on the same rockstar account
false: Allow players to connect/playing with multiple session on the same rockstar account

Recommended: true -> set to true, will prevent players to join your server with multiple session and can cause missing player information, so you cannot find the player (example: missing player id) or crash the server

Config.AntiBanEvade

true: Don't allow players to connect if they are already banned from anticheat and try to ban evade by bypassing through some spoofing methods. The check is made based on banId, identifiers, tokens and memory (IP is excluded)
false: Allow players to connect if they are already banned from anticheat and they have used spoofing methods

Recommended: true -> set to true to don't allow banned players to rejoin

Config.AntiBanEvadeIP

true: Don't allow players to connect if they are already banned from anticheat and try to ban evade having the same IP
false: Allow players to connect if they are already banned from anticheat and they have used spoofing methods, but they have the same IP

Recommended: true -> set to true to don't allow banned players to rejoin

Config.AntiSpoofer

true: Don't allow players that used spoofer on their computers before
false: Allow players that used spoofer on their computers before

Recommended: false -> set to false, as many players may have used spoofer on their computers in the past to unlink tokens (unknown reason -> you can ask them, but they can also tell you they don't know because maybe they don't have any ideea what they install) and could be also on other games

Config.AntiReleaseMode

true: Don't allow players to join your server on release mode and use canary or beta mode
false: Allow players to join your server on release mode

Recommended: true -> this is a very important setting for your server to set to true (even though in the config file is set to false) if you know that every player that joins your server is able to understand what they have to do (a tutorial will be displayed on drop player message and they can follow the mentioned steps). Most cheats/executors can be injected only on release mode channel, so switching to Beta or Latest (Unstable) mode will eliminate maybe all cheaters from your server

Config.TrustFactorCheck

true: Don't allow players to connect to the server if their trust factor is below the thresholds Config.MinTrustFactorTotal or Config.MinTrustFactorChecker
false: Allow players to connect to the server if their trust factor is below the thresholds Config.MinTrustFactorTotal or Config.MinTrustFactorChecker

Recommended: true -> set to false, as you may not desire this feature, but it is an easy way to directly block suspect players to connect to your server if their trust factor is too low (under Config.MinTrustFactorTotal or Config.MinTrustFactorChecker values)

Config.MinTrustFactorTotal = 20 -- any value under 20 is blocked
Config.MinTrustFactorTotal = 0 -- only 0 value is blocked
Config.MinTrustFactorTotal = -1 -- disable

Config.MinTrustFactorChecker = 40 -- any value under 40 is blocked
Config.MinTrustFactorChecker= 0 -- only 0 value is blocked
Config.MinTrustFactorChecker= -1 -- disable

Config.AntiMenus

true: Don't allow players to use lua menus
false: Allow players to use lua menus

Recommended: true -> for sure injected from cheats/executors

Config.AntiMenusPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiExecutor

true: Don't allow players to use or navigate through executors in case they have injected it
false: Allow players to use or navigate through executors in case they have injected it

Recommended: true -> set to true to monitor players if they are using or navigating through cheat menus

Config.AntiExecutorPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiResourceInject

true: Don't allow players to inject resources to your server
false: Allow players to inject resources to your server

Recommended: true -> set to true, cheaters can be caught if they inject resources to your server.

Config.AntiResourceInjectPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiLuaInject

true: Don't allow players to inject and execute lua code from your scripts
false: Allow players to inject and execute lua code from your scripts

Recommended: true + installation -> set to true, cheaters can be caught if they execute code that does not exist in your resources (in the specific resource the cheater injected that code).

Config.AntiLuaInjectPenalty can be WARNING, KICK or BAN.
Recommended: BAN

lua54 "yes"
client_script "@rac/source/client/inject.lua"
shared_scripts {"@ox_lib/init.lua"}
dependencies {"ox_lib"}

Config.DeathPrint

true: Prints the player who killed you in F8 console
false: Does not print if anyone killed you

Recommended: true -> set to true, this is helpful in case a cheater finds a way to kill you, so you can find him

Config.DamagePrint

true: Prints the method you got damaged in F8 console
false: Does not print when you get damaged

Recommended: true -> set to true, this is helpful in case a player or cheater finds a way to damage you, so you can find him

Config.ComaHealth

Config.ComaHealth - is the value of health when the player is in coma (dead). If you are in coma (dead) the health is 120 HP (FiveM default), so the value in config should be 121

Config.AntiAllExplosions

true: Cancel all explosions (creation and damage)
false: Allow explosions

Recommended: true -> set to true, all explosions will be cancelled on the server, but it is set to false by default as you may want to see or use some explosions on the server

Config.AntiExplosions

true: Cancel explosions (creation and damage)
false: Allow explosions

Recommended: true -> set to true, any explosion created will not deal damage and will be cancelled on the server

Config.AntiExplosionsPenalty can be WARNING, KICK or BAN.
Recommended: BAN (never use WARNING)

Config.BlockedExplosions

Config.BlockedExplosions - is a table where is the name of the explosion along with its id that is allowed or not. In case a player will execute any of this not allowed explosion will get penalty Config.AntiExplosionsPenalty on first explosion usage. If the name of the explosion along with its id is commented (-- before explosion) means that it is allowed, else if the name of the explosion along its id is not commented (it has not -- before explosion) means that it is not allowed and the player will get penalty Config.AntiExplosionsPenalty if he is execute such explosion. In case you have scripts that uses explosions you have to allow them carefuly in Config.BlockedExplosions (Even though you have scripts with explosions it is not recommended to allow any explosion and leave the table as it is by default. A cheater can have in his executor / menu an explosion that is allowed and harm your server)

Config.AntiInvisibleExplosions

true: Cancel invisible explosions
false: Allow invisible explosions

Recommended: true -> set to true, will not allow players to spawn invisible explosions

Config.AntiInvisibleExplosionsPenalty can be WARNING, KICK or BAN.
Recommended: BAN (never use WARNING)

Config.AntiSilentExplosions

true: Cancel silent explosions
false: Allow silent explosions

Recommended: true -> set to true, will not allow players to spawn silent explosions

Config.AntiSilentExplosionsPenalty can be WARNING, KICK or BAN.
Recommended: BAN (never use WARNING)

Config.AntiSpamExplosions

true: Start counting each player explosions used in a certain period of time
false: Does not counter each player explosions used in a certain period of time

Recommended: true -> set to true, if player causes a specific number number of explosions (Config.ExplosionsCounter) in a specific period of time (Config.ExplosionsTimer seconds), even though the explosion is allowed (beside the explosions from gas, vehicles or other explosions that can be produced on the server by players), he will get penalty Config.AntiSpamExplosionsPenalty. Even though the explosions from vehicles are not blacklisted they will count in different situations such as the explosion has been produced with no vehicle nearby the player (if there is no vehicle nearby and he is the owner of a vehicle explosion he must be cheating) and try to prevent this type of explosions by deleting the vehicle which is going to explode. This is one example of a situation that is analyzed and deliver full information about the explosion. Also, explosions which are not produced on the server and only on client will be punished.

Config.AntiSpamExplosionsPenalty can be WARNING, KICK or BAN.
Recommended: BAN (never use WARNING)

Config.AntiProjectiles

true: Cancel projectiles (creation)
false: Allow projectiles

Recommended: true -> set to true, any projectiles (Ball, Snowball, RPG, Grenade Launcher, Homing Launcher, Railgun and others can be launched and they are considered projectiles) created will be cancelled and cleared on the server in order to not damage players

Config.AntiProjectilesPenalty can be WARNING, KICK or BAN.
Recommended: BAN (never use WARNING)

Config.AntiSpamProjectiles

true: Start counting each player projectiles used in a certain period of time
false: Does not counter each player projectiles used in a certain period of time

Recommended: true -> set to true, if player causes a specific number number of projectiles (Config.ProjectilesCounter) in a specific period of time (Config.ProjectilesTimer seconds), even though the projectile is allowed, he will get penalty Config.AntiSpamProjectilesPenalty.

Config.AntiSpamProjectilesPenalty can be WARNING, KICK or BAN.
Recommended: BAN (never use WARNING)

Config.WhitelistedProjectiles

Config.WhitelistedProjectiles - is a table which contains all projectiles that are allowed on the server. Whitelisted projectiles will not be cleared from the server

Config.AntiParticles

true: Don't allow particle spawn beside the whitelisted ones on the server
false: Allow particle spawn on the server

Recommended: true -> set to true, will cancel all harmful particles that can be spawned on all players by cheaters

Config.AntiParticlesPenalty can be WARNING, KICK or BAN.
Recommended: BAN (never use WARNING)

Config.WhitelistedParticles

Config.WhitelistedParticles - is a table which contains all particles ids that are allowed on the server. In case the particle is not added as whitelisted particle, the player who execute any particle which is not whitelisted will get penalty on first particle usage. In case you use any particle on the server it will print the particle id on anticheat logs so you can whitelist it.

Config.AntiCollision

true: Remove collision for specific props
false: Do not remove collision for any prop

Recommended: true -> there are props which can be harmful to the server, such as gas pumps, that can cause explosions which are mostly produced by cheaters or trolls, so setting to true will prevent players to create a harmful impact with the specific prop

Config.RemoveCollisionProps

Config.RemoveCollisionProps - is a table that contains all props you can get through them without causing any impact (such as explosions). By default, all gas pumps are set without collision in order to avoid explosions on the server

Config.FrameworkAntiWeapons

true: Don't allow players use weapons from outside the server (outside of function Config.FrameworkWeaponCheck)
false: Allow players use weapons from outside the server

Recommended: true -> set to true, this feature can be used if you can place some conditions to check player weapons inside function Config.FrameworkWeaponCheck

Config.FrameworkAntiWeaponsPenalty can be WARNING, KICK or BAN.
Recommended: BAN (never use WARNING)

Config.FrameworkAntiWeaponsCheck

Config.FrameworkAntiWeaponsCheck - is a function that your can make on your own to check if the player owns the weapon (inventory item) or other checks (examples: hours played, level, gun license item) to avoid weapons given from cheats. In case you use the weapon wheel for your weapons, this resource will not be that useful for you. You can customize your functions for checking the weapon on players in order to get penalty if they use weapons from cheats

-- Example

Config.FrameworkAntiWeaponsCheck = function(source, weaponname)
    if source then
        local user_id = vRP.getUserId{(source)} or nil
        if user_id then
            if vRP.getInventoryItemAmount({user_id, weaponname}) > 0 or vRP.getInventoryItemAmount({user_id, string.lower(weaponname)}) > 0 then
                return true
            else
                if GetVehiclePedIsIn(GetPlayerPed(source), false) ~= 0 then
                    return GetVehicleType(GetVehiclePedIsIn(GetPlayerPed(source))) == "heli"
                else
                    return false
                end
            end
        end
    end
end

Config.AntiBlacklistedWeapons

true: Don't allow players with specific not allowed weapons (set in Config.BlacklistedWeapons) in any way (have it in loadout, pull out it in his hands, shoots, aiming or damage with it)
false: Allow players all weapons

Recommended: true -> set to true, will clear, cancel, remove and penalty players that are using specific not allowed weapons (weapons that are set in Config.BlacklistedWeapons)

Config.AntiBlacklistedWeaponsPenalty can be WARNING, KICK or BAN.
Recommended: BAN (never use WARNING)

Config.BlacklistedWeapons

Config.BlacklistedWeapons - is a table which contains weapons that are not allowed

Config.AntiExplosiveWeapons

true: Don't allow players to use explosive weapons/bullets
false: Allow players to use explosive weapons/bullets

Recommended: true -> set to true, will remove explosive weapons/bullets from player if he owns one

Config.AntiLoadout

true: Don't allow players spawn with weapons from citizen loadout file
false: Allow players spawn with weapons from citizen loadout file

Recommended: false -> set to true can produce false bans due to inventory system in case you are using weapons as items (in this case, keep Config.AntiLoadout set to false and Config.FrameworkAntiWeapons set to true and configure the function Config.FrameworkAntiWeaponsCheck is the best solution). If you are using weapon wheel, you can set it to true

Config.AntiLoadoutPenalty can be WARNING, KICK or BAN.
Recommended: BAN

sv_pureLevel 1

Config.AntiGiveWeapon

true: Don't allow players to give/send weapons (one or all) to other players
false: Allow players to give weapons to other players

Recommended: true -> cheaters can give weapons through cheating methods (benefit or troll), so set to true will cancel this type of function

Config.AntiGiveWeaponPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiRemoveWeapon

true: Don't allow players to remove weapons (one or all) from other players
false: Allow players to remove weapons from other players

Recommended: true -> cheaters can remove weapons through cheating functions (troll), so set to true will cancel this type of function

Config.AntiRemoveWeaponPenalty can be WARNING, KICK or BAN.
Recommended: WARNING -> this can cause false calls because of FiveM infrastructure. Set on WARNING will just cancel the function

Config.AntiInfiniteAmmo

true: Don't allow player using infinite ammo on weapon
false: Allow player using infinite ammo on weapon

Recommended: true -> set to true, will prevent player to use infinite ammo (exceed maximum bullet amount loaded in weapon, which is 250 or Config.MaxAmmo (it is set by default 250) or having maximum bullet amount without decreasing the amount)

Config.AntiInfiniteAmmoPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiInfiniteBullets

true: Don't allow players to have infinite bullets (also some infinite ammo or no reload functions) on weapons
false: Allow players to have infinite bullets on weapons

Recommended: true -> set to true, will prevent player to use infinite bullets (exceed maximum bullet amount loaded in weapon or no reload functions)

Config.AntiInfiniteBulletsPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiRapidFire

true: Don't allow players to use rapid fire functions
false: Allow players to use rapid fire functions

Recommended: true -> set to true, will prevent player to send a large amount of bullets in a very short time

Config.AntiRapidFirePenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiNoRecoil

true: Don't allow players to cancel the recoil from your server weapons
false: Allow players to cancel the recoil from your server weapons

Recommended: false -> set to false because you maybe forgot to set recoil on some weapons that you are using on the server and it is not such harmful cheating function

Config.AntiNoRecoilPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiFastReload

true: Don't allow players to fast reload the weapon
false: Allow players to fast reload the weapon

Recommended: false -> set to false because you maybe have players that are bug abusing through different methods due to your server scripts

Config.AntiFastReloadPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiSpreadBullet

true: Don't allow players to shoot multiple players from one single bullet
false: Allow players to shoot multiple players from one single bullet

Recommended: true -> set to true because cheaters can shoot one single bullet and kill multiple players in the same time

Config.AntiSpreadBulletPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiStunPlayer

true: Don't allow players to stun other players from cheating methods
false: Allow players to stun other players from cheating methods

Recommended: true -> set to true, will prevent player to stun other players from executor / menu

Config.AntiStunPlayerPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiSuperPunch

true: Don't allow players to one shot as unarmed from cheating methods
false: Allow players to one shot as unarmed from cheating methods

Recommended: true -> will prevent players to use super punch function by dectecting high amount of damage on punching other players

Config.AntiSuperPunchPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiComponentModifier

true: Don't allow players to modify their weapon components
false: Allow players to modify their weapon components

Recommended: true -> set to true, will prevent players to modify their weapon components and catch the player with component modifier

Config.AntiDamageModifierPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiDamageModifier

true: Don't allow players to modify their weapon damages
false: Allow players to modify their weapon damages

Recommended: true -> set to true, will prevent players to modify their weapon damage and catch the player with damage modifier higher than Config.MaxWeaponDamageModifier (Every default weapon has damage modifier 1.0)

Config.AntiDamageModifierPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiDamageMultiplier

true: Don't allow players to muliply their weapon damages
false: Allow players to modify thei weapon damages

Recommended: true -> set to true, will prevent players to multiply their weapon damage adn catch the player if he deals damage higher than default values (body or headshot)

Config.AntiDamageMultiplierPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiBulletModifier

true: Don't allow players to change their weapon bullets or not allowed bullets
false: Allow players to change their weapon bullets or any bullets

Recommended: true -> set to true, will prevent players to modify their bullets from his weapon. Under this feature the players are not able to change their default (GTA 5) weapon ammo or default (GTA 5) weapon damage type. If a player will be caught with ammo or damage type change, his weapon will be removed. Also, this feature will detect if a player will spam (either cheat function, either bug abuse) the stungun bullets without any cooldown (the default cooldown from GTA 5 is ~ 2.8 seconds).

Config.AntiBulletModifierPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiSilencedWeapon

true: Don't allow players to use suppressor attachment on any weapon or use silent kill cheating functions
false: Allow players to use suppressor attachment on any weapon and use silent kill cheating functions

Recommended: false -> set to false, players can be killed by other players with weapons that have suppressor attachment or silent kill cheating functions (only if break all checks from Config.AntiKill feature -> in case it will ever break, a solution will be found to give penalty for that). You can set to true this feature only if you are very sure that you are not using surpressor attachments on your server

Config.AntiSilencedWeaponPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiRangeModifier

true: Don't allow players to shoot from higher weapon range than default
false: Allow players to shoot from higher weapon range than default

Recommended: true -> set to true, will prevent players to modify their weapon's range. This feature will block range multiplier functions or noclip/freecam functions which make the player shoot from a distance higher than the default maximum weapon range set by GTA 5 from the victim. If you modified the weapon range from your scripts, you should set this feature to false.

Config.AntiRangeModifierPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiPunchPlayer

true: Don't allow cheaters to punch you from cheating methods
false: Allow cheaters to punch you from cheating methods

Recommended: true -> set to true, will prevent cheaters to punch you from executor / menu with different methods.

Config.AntiKillPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiKill

true: Don't allow cheaters to kill you from cheating methods
false: Allow cheaters to kill you from cheating methods

Recommended: true -> set to true, will prevent cheaters to kill you from executor / menu with different methods. This feature also includes the spawn safe/spoof weapon method.

Config.AntiKillPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiKillPlayersInMass

true: Don't allow player to kill too many players in a specific period of time
false: Allow player to kill how many players he can

Recommended: true -> set to true, will prevent player to kill a specific number of players (Config.AntiKillPlayersInMassNumber) in a specific period of time (Config.AntiKillPlayersInMassTimer seconds)

Config.AntiKillPlayersInMassPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiSpawnWeapon

true: Don't allow players spawn weapon to their hand if using weapon wheel as selecting weapon method
false: Allow players spawn weapon to their hand if using weapon wheel as selecting weapon method

Recommended: false -> set as default to false, as you are maybe not using the weapon wheel on your server and may use weapons from inventory as items and you have the weapon wheel disabled. If this feature is set to true, it will prevent player to spawn a weapon if it is not selected from weapon wheel. Set this feature to true, only if you are using the weapon wheel as selecting weapon method.

Config.AntiSpawnWeaponPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiSpoofWeapon

true: Don't allow players to use spoof / spawned safe weapons
false: Allow players to use spoof / spawned safe weapons

Recommended: true -> set to true will prevent player to use spoof or spawned safe weapons from cheating methods. There is no way a legit player will get penalty from this check.

Config.AntiSpoofWeaponPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiMetaFiles

true: Don't allow players to use meta files (citizen files)
false: Allow players to use meta files (citizen files)

Recommended: true -> set to true, will prevent player to use meta files (aimbot file, magic bullet file, fast ladder climbing, fast swim, x64 file, damage boost, fire rate)

Config.AntiMetaFilesPenalty can be WARNING, KICK or BAN.
Recommended: BAN

sv_pureLevel 1

Config.AntiAimbotAccuracy

true: Start monitor players for headshot accuracy
false: Do not monitor players for headshot accuracy

Recommended: true -> set to true, by monitoring players for headshot accuracy, they can be suspicious for having aim assist functions

Config.AntiAimbotRpf

true: Don't allow players using aimbot rpf file and controller aim assist
false: Allow players using aimbot rpf file and controller aim assist

Recommended: true -> set to true, will prevent players to use aimbot rpf file (citizen file) and controller aim assist

sv_pureLevel 1

Config.AntiAimbot1

true: Don't allow players using aimbot functions
false: Allow players using aimbot functions

Recommended: false -> set to true, will prevent players to use any type of aimbot (less than Config.AntiAimbot2), but by default it is set to false, as Config.AntiAimbot2 is set to true

Config.AntiAimbot2

true: Don't allow players using aimbot functions
false: Allow players using aimbot functions

Recommended: true -> set to true, will prevent player to use any type of aimbot

Config.AntiAimbot3

true: Don't allow players using aimbot functions
false: Allow players using aimbot functions

Recommended: true -> set to true, will prevent players to use aimbot functions by give penalty to the players who use such functions, monitoring the player aiming

Config.AntiAimbot3Penalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiSilentAim

true: Don't allow players using silent aimbot or magic bullet functions
false: Allow players using silent aimbot or magic bullet functions

Recommended: true -> set to true, will prevent players to use silent aimbot and magic bullet functions

Config.AntiSilentAim2

true: Don't allow players using silent aimbot functions
false: Allow players using silent aimbot functions

Recommended: true -> set to true, will prevent players to use silent aimbot functions by give penalty to the players who use such functions, monitoring the player shooting

Config.AntiSilentAim2Penalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiMagicBullet

true: Don't allow players using magic bullet functions
false: Allow players using magic bullet functions

Recommended: true -> set to true, will prevent players to use magic bullet functions by give penalty to the players who use such functions, monitoring the player shooting

Config.AntiMagicBulletPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiCornerShoot

true: Don't allow players to shoot from corners or through textures
false: Allow players to shoot from corners or through textures

Recommended: true

Config.AntiTriggerbot

true: Don't allow players using triggerbot
false: Allow players using triggerbot

Recommended: false -> set to true, will prevent players using triggerbot functions, but by default is set to false in order to test on your server if there are no false bans due to some checks

Config.AntiESP1

true: Don't allow cheaters with ESP (visuals)
false: Allow cheaters with ESP (visuals)

Recommended: true -> set to true, will eliminate visible location details of players such as boxes, lines, skeletons, name tag, health bar (ESP) from cheats if the visible location details of players do not show for the dead players

Config.AntiESP2

true: Don't allow cheaters with ESP (visuals)
false: Allow cheaters with ESP (visuals)

Recommended: true -> set to true, will eliminate visible location details of players such as boxes, lines, skeletons, name tag, health bar (ESP) if the players should not be seen (Example: Behind the buildings)

Config.AntiBlacklistedVehicles

true: Despawn from the server a blacklisted vehicle from Config.BlacklistedVehicles table
false: Allow spawning any vehicle on the server

Recommended: true -> set to true, will despawn any vehicle that can be harmful to your server (set by you in Config.BlacklistedVehicles table)

Config.AntiBlacklistedVehiclesPenalty can be WARNING, KICK or BAN.
Recommended: WARNING (will just despawn and log. KICK or BAN can cause false bans due to FiveM random vehicle spawn as environment/population even if you are using OneSync or from your scripts without knowing, so it is recommended to keep on WARNING)

Config.BlacklistedVehicles

Config.BlacklistedVehicles - is a table which contains all vehicles that are not allowed (blacklisted) to be spawned or used on your server. When a blacklisted vehicle is spawned it will get despawned if the car was spawned or deleted if the player is using the vehicle. If any player tries to spam spawning a vehicle (whitelisted or blacklisted) he will get banned for spawn limit entities. In case this is an issue, you should adjust your spawn limit vehicles (Config.VehiclesCounter) and timer (Config.EntitiesTimer) or adjust your script from your server

Config.AntiBlacklistedModels

true: Don't allow using a ped model that is not whitelisted as player
false: Allow using any ped model for you as a player

Recommended: true -> set to true, will penalty a player who has a different ped model which is not whitelisted in Config.WhitelistedModels and that can be harmful for your players' activity on the server (Example: Alien)

Config.AntiBlacklistedModelsPenalty can be WARNING, KICK or BAN.
Recommended: BAN -> it is recommended to remove all scripts from you can load any GTA V ped model (Example: clothing script)

Config.WhitelistedModels

Config.WhitelistedModels - is a table that contains the ped model names that you are allowed to use on the server as a player

Config.AntiBlacklistedPeds

true: Despawn from the server a not whitelisted ped (ped that is not from Config.WhitelistedPeds table)
false: Allow spawning any ped on the server

Recommended: true -> set to true, will despawn any ped that can be harmful to your server (all peds which are not in Config.WhitelistedPeds)

Config.AntiBlacklistedPedsPenalty can be WARNING, KICK or BAN.
Recommended: WARNING (will just despawn and log. kick or ban can cause false bans due to FiveM random ped spawn as environment/population even if you are using OneSync or from your scripts without knowing)

Config.WhitelistedPeds

Config.WhitelistedPeds - is a table which contains all peds that are allowed (whitelisted) to be spawned on your server. When a not whitelisted ped is spawned it will get despawned. If any player tries to spam spawning a ped (whitelisted or blacklisted) he will get banned for spawn limit entities. In case this is an issue, you should adjust your spawn limit peds (Config.PedsCounter) and timer (Config.EntitiesTimer) or adjust your script from your server

Config.AntiBlacklistedProps

true: Despawn from the server a not whitelisted prop/object (prop/object that is not from Config.WhitelistedProps table)
false: Allow spawning any prop/object on the server

Recommended: true -> set to true, will despawn any prop that can be harmful to your server (all props which are not in Config.WhitelistedProps)

Config.AntiBlacklistedPropsPenalty can be WARNING, KICK or BAN.
Recommended: WARNING (will just despawn and log. kick or ban can cause false bans due to FiveM random prop/object spawn as environment/population even if you are using OneSync or from your scripts without knowing)

Config.WhitelistedProps

Config.WhitelistedProps - is a table that contains the whitelisted props / objects that can be used on the server. If the prop / object is not whitelisted it will get despawned. If any player tries to spam spawning an prop / object he will get banned for spawn limit entities. In case this is an issue, you should adjust your spawn limit props / objects (Config.ObjectsCounter) and timer (Config.EntitiesTimer) or adjust your script from your server with a cooldown

If you want to add its name:

[`propname`] = true, -- Example: [`hei_prop_heist_box`] = true,

If you want to add its hash:

["prophash"] = true, -- Example: [`-517243780`] = true,

Config.OneSyncEntities

true: Allow using NPCs (Peds, Vehicles, Objects) on your server
false: Don't allow using NPCs (Peds, Vehicles, Objects) on your server

Recommended: false -> set to false, as the anticheat resource requires OneSync, and usually population should be also removed. Set this feature to true only if you are using NPCs on your server to prevent deleting entities spawned by OneSync and ignore counting them by Config.countEntities feature -> many risks will come due to cheating actions by having population to your server

Config.BurstEntities

true: Start detecting burst entity spawns (multiple entities spawned in a very short time)
false: Don't detect burst entity spawns

Recommended: true -> set to true by default, will start detecting entity spawns Config.BurstEntitiesLimit entities of the same type or Config.BurstEntitiesDiverseModelLimit entities of different models in a very short time (Config.BurstEntitiesWindow seconds). Your server may contain scripts that burst spawn entities (example: job objects), so Config.BurstEntitiesIgnoreObjects is set to true by default to avoid objects deletion. If your server also has scripts that burst spawn vehicles or peds, set Config.BurstEntitiesIgnoreVehicles or Config.BurstEntitiesIgnorePeds to true as well, or set Config.BurstEntities to false to disable the entire feature. If your server does not have any scripts that burst spawn objects, you can set Config.BurstEntitiesIgnoreObjects to false for better protection. This feature does not have a penalty, it only deletes the entities and logs the detection. This feature is different from Config.CountEntities as it detects faster bursts in a shorter time window while Config.CountEntities counts entities over a longer period of time (Config.EntitiesTimer seconds). Both features can be used together for better protection.

Config.CountEntities

true: Start counting each player entities (vehicles, peds, objects) spawned in a specific period of time
false: Don't count each player entities (vehicles, peds, objects) spawned

Recommended: true -> set to true, will start counting each player entities spawned in a specific period of time (Config.EntitiesTimer seconds). If a player spawns an amount of entities, which can be vehicles, peds, objects/props (Config.VehiclesCounter, Config.PedsCounter, Config.ObjectsCounter) even though the vehicle / ped / object / prop is allowed in a certain period of time (Config.EntitiesTimer seconds) he will get penalty. Spawning a big amount of entities in short time can be very harumful to your server because cheaters can spam spawning entities.

Config.CountEntitiesPenalty can be WARNING, KICK or BAN.
Recommended: BAN (never use WARNING because it has no penalty and it can lead to server crash due to high consumption and prints)

Config.EntitySpawnCheck

true: Don't allow spawn entities from cheating methods
false: Allow spawn entities from cheating methods

Recommended: true -> set to true, will prevent players to spawn entities (vehicles, peds or objects/props) from cheating methods If a player spawns an entity from outside the server, the entity will be deleted and send a log to entities room, but if the player will spawn in mass entities (Config.EntitySpawnCount) in Config.EntitiesTimer seconds from outside the server (executors or menus) he will get banned.

Config.AdvancedEntitySpawnCheck

true: Don't allow spawn entities from cheating methods
false: Allow spawn entities from cheating methods

Recommended: true -> set to true, will prevent players to spawn entities (peds, vehicles or objects/props) from unknown or injected (abnormal) scripts that are not supposed to create vehicles, peds or objects/props. If a player spawns an entity from unknown or injected (abnormal) script that are not supposed to create vehicles, peds or objects/props, the entity will be deleted and send a log to entities room, but if the player will spawn in mass entities (Config.AdvancedEntitySpawnCount) in Config.EntitiesTimer seconds from unknown or injected (abnormal) scripts that are not supposed to create vehicles, peds or objects/props, he will get banned.

Config.AnticheatEntityLockdown

true: Don't allow players spawning entities from outside the server (outside of server configuration)
false: Allow players spawning entities from outside the server

Recommended: true + installation -> set to true, will prevent players spawning entities (vehicles, peds, props/objects) from outside the server (outside the server configuration). If a player spawns an entity from outside the server, the entity will be deleted and send a log to entities room, but if the player will spawn in mass entities (Config.AnticheatEntityLockdownCount) in Config.EntitiesTimer seconds from outside the server, he will get banned.

CreateVehicle -> exports['racv2']:CreateVehicle
CreatePed -> exports['racv2']:CreatePed
CreateObject -> exports['racv2']:CreateObject

Examples:

Before

local vehicle = CreateVehicle(hash, x, y, z, 0.0, true, false)

After

if GetResourceState('racv2') == 'started' then
    local vehicle = exports['racv2']:CreateVehicle(hash, x, y, z, 0.0, true, false)
else
    local vehicle = CreateVehicle(hash, x, y, z, 0.0, true, false)
end

Before

local ped = CreatePed(4, hash, x, y, z, 0.0, false, true)

After

if GetResourceState('racv2') == 'started' then
    local ped =  exports['racv2']:CreatePed(4, hash, x, y, z, 0.0, false, true)
else
    local ped = CreatePed(4, hash, x, y, z, 0.0, false, true)
end

Before

local object = CreateObject(hash, x, y, z, true, true, true)

After

if GetResourceState('racv2') == 'started' then
    local object = exports['racv2']:CreateObject(hash, x, y, z, true, true, true)
else
    local object = CreateObject(hash, x, y, z, true, true, true)
end

Config.EntitiesTimer

Config.EntitiesTimer - is a timer in seconds for countering the entities or spawning entities from outside the server. This timer is being used for entities check features (Config.CountEntities, Config.EntitySpawnCheck and Config.AdvancedentitySpawnCount)

Config.AntiInvisibleEntities

true: Don't allow players spawn invisible entities
false: Allow players spawn invisible entities

Recommended: true -> set to true, will prevent players to spawn invisible entities (vehicles, peds or objects/props)

Config.AntiSpawnEntityOnPlayer

true: Don't allow spawning entities on other players
false: Allow spawning entities on other players

Recommended: true -> set to true, will delete the entities spawned at a specific distance from the creator location very close to another player. In case you use scripts (such as job scripts) that spawns vehicles at a long distance from the player you should better adjust the script to first teleport the player to the create vehicle location using SetEntityCoords for your player instead of setting this feature to false. In case you have no access to the script due to encryption, you can se this setting to false on your own risk

Config.AntiAttachEntities

true: Detach the entities attached to you as a player or to your vehicle
false: Don't detach any entity if it is attach to you as a player or to your vehicle

Recommended: true -> set to true, will detach the entities attached to you as a player or to your vehicle. In case of a vehicle attached to you as a player, the vehicle will not be detached if you are trying to enter a vehicle or if you drive the vehicle

Config.AntiEmptyVehicle

true: Stop or delete the empty vehicles (no driver and moving)
false: Allow empty vehicles (no driver and moving)

Recommended: true -> set to true, will stop or delete the vehicles that are moving empty or remotely controlled. In case a vehicle is spawned and remotely controlled (has not a driver, but the vehicle is moving) it will be deleted. In case the vehicle has still not a driver, but the vehicle is moving, if the vehicle reaches an abnormal speed, it will be stopped and if the vehicle is flagged for too many times for this reason, the vehicle will be deleted

Config.AntiFlyingVehicles

true: Don't allow flying nearby vehicles or high speed on using vehicles
false: Allow flying vehicles and high speed on using vehicles

Recommended: true -> set to true, will prevent nearby vehicles flying and some types of functions to launch using vehicles with very high speed while driving by stopping the vehicle if the vehicle speed reaches a speed that is abnormal for that vehicle (it calculates the maximum possible vehicle speed based on its handling)

Config.AntiThrowingVehicles

true: Don't allow cheaters call throw vehicle function
false: Allow cheaters call cheaters call throw vehicle function

Recommended: true -> set to true, will ban the player who throws a vehicle

Config.AntiBlackholeVehicles

true: Don't allow cheaters call blackhole functions on nearby vehicles
false: Allow cheaters call blackhole functions on nearby vehicles

Recommended: true -> set to true, will prevent cheaters to start blackhole function on their owned vehicles

Config.AntiVehicleWeapons

true: Disable vehicle weapons
false: Allow vehicle weapons

Recommended: true -> set to true, will prevent vehicles to have weapons by disabling all kind of weapons on the vehicles

Config.AntiKillEngine

true: Don't allow cheaters to destroy vehicle's engine
false: Allow cheaters to destroy vehicle's engine

Recommended: true

Config.AntiKillWheels

true: Don't allow cheaters to destroy vehicle's wheels
false: Allow cheaters to destroy vehicle's engine

Recommended: true

Config.AntiKickFromVehicle

true: Don't allow cheaters to kick players from vehicles by trying to keep the player inside the vehicle
false: Allow cheaters to kick players from vehicles

Recommended: true -> set to true, will prevent cheaters to kick players from vehicles (kick or hijack cheating functions) or use crashing methods which involves kick from vehicle functions on players

Config.AntiKickFromVehicle2

true: Don't allow cheaters to kick players from vehicles by forcing the player in the driver seat
false: Allow cheaters to kick players from vehicles

Recommended: true -> set to true, will prevent to not allow kick out player from vehicle and take over the place of the initial driver by forcing the player in the driver seat or launch vehicles functions by first ejecting the player from the vehicle, but by default it is set to false as it may cause issues on some servers due to server scripts. This feature will handle only this type of function by keeping the player on driver seat if he is the driver

Config.AntiVDM

true: Don't allow damage from vehicles on players
false: Allow damage from vehicles on players

Recommended: true -> set to true, will prevent damage from cars on players (prevent troll and different situations when cheaters' actions can kill players)

Config.AntiVDMTroll

true: Don't allow players to hit multiple players with their vehicle (VDM on multiple players)
false: Allow players to hit multiple players with their vehicle (VDM on multiple players)

Recommended: true -> set to true, will prevent players to hit multiple players with their vehicle (VDM on multiple players)

Numer of players: 10 (distinct players)

Config.AntiVehicleParachute

true: Don't allow parachute on vehicles
false: Allow parachute on vehicles

Recommended: true -> set to true, will prevent players to set parachute on vehicles through vehicle parachute cheating functions

Config.AntiVehicleJump

true: Don't allow players to jump with vehicles or modify vehicle gravity
false: Allo players to jump with vehicles and modify vehicle gravity

Recommended: true -> set to true, will prevent players to use vehicle jump functions or vehicle gravity modifications, but by default it is set to false as you may have scripts that can change the default mechanism of the vehicles

Config.AntiVehicleNoclipPenalty can be WARNING, KICK or BAN.
Recommended: WARNING (delete the vehicle only)

Config.AntiVehicleNoclip

true: Don't allow players to use noclip while they are inside the vehicle
false: Allow players to use noclip while they are inside the vehicle

Recommended: true -> set to true, will prevent players to use noclip while the players are inside the vehicle (fly with vehicle), but by default it is set to false as you have to add your staff members to whitelist first

Config.AntiVehicleNoclipPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiVehicleFix

true: Don't allow players fix their vehicles multiple times outside the tuning system
false: Allow players fix their vehicles multiple times outside the tuning system

Recommended: true -> set to true, will prevent players to use vehicle fix functions multiple times (excluding the tuning system), but by default it is set to false as you may have scripts in your server that can fix your vehicle beside the tuning system.

Config.AntiVehicleFixPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiVehicleChangeColor

true: Don't allow players change color on their vehicles multiple times outside the tuning system
false: Allow players change color on their vehicles multiple times outside the tuning system

Recommended: true -> set to true, will prevent players to use vehicle change color functions multiple times (excluding the tuning system), but by default it is set to false as you may have scripts in your server that can change color of your vehicle beside the tuning system.

Config.AntiVehicleChangeColorPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiVehicleChangeMods

true: Don't allow players change mods on their vehicles outside the tuning system
false: Allow players change mods on their vehicles outside the tuning system

Recommended: true -> set to true, will prevent players to load too many mods on their vehicle (excluding the tuning system), but by default it is set to false as you may have scripts in your server that can load mods of your vehicle beside the tuning system

Config.AntiVehicleChangeModsPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiTeleportIntoVehicle

true: Don't allow cheaters to teleport into vehicle or other players' vehicle
false: Allow cheaters to teleport into vehicle or other players' vehicle

Recommended: true -> set to true, will prevent cheaters to teleport into vehicle or other player's vehicle beside the vehicle names from Config.TeleportIntoVehicles table

Config.TeleportIntoVehicles

Config.TeleportIntoVehicles - is a table that contains vehicle names that will be ignored by the Config.AntiTeleportIntoVehicle feature

Example: Usage native SetEntityCoords before vehicle creation and warp ped into vehicle

Before

local vehicle = CreateVehicle(hash, x, y, z, 0.0, true, false)
TaskWarpPedIntoVehicle(PlayerPedId(), vehicle, -1)

After

SetEntityCoords(PlayerPedId(), x, y, z, true, true, true, false)
Wait(300)
local vehicle = CreateVehicle(hash, x, y, z, 0.0, true, false)
TaskWarpPedIntoVehicle(PlayerPedId(), vehicle, -1)

Example 2: Usage native SetEntityCoords before vehicle creation and set ped into vehicle

Before

local vehicle = CreateVehicle(hash, x, y, z, 0.0, true, false)
SetPedIntoVehicle(PlayerPedId(), vehicle, -1)

After

SetEntityCoords(PlayerPedId(), x, y, z, true, true, true, false)
Wait(300)
local vehicle = CreateVehicle(hash, x, y, z, 0.0, true, false)
SetPedIntoVehicle(PlayerPedId(), vehicle, -1)

Config.AntiStealVehicle

true: Don't allow cheaters to steal vehicles of other players
false: Allow cheaters to steal vehicles of other players

Recommended: true -> set to true, will prevent cheaters to steal vehicles of other players, while the players are in the vehicle

Config.AntiStealVehiclePenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiVehicleSpeedHack

true: Don't allow using vehicle speed hack function on vehicles
false: Allow using vehicle speed hack function on vehicles

Recommended: true -> set to true, will prevent players from multiplying their vehicle's acceleration to reach abnormally high speeds, cover unexpected distances, or use a rocket boost

Config.AntiVehicleSpeedHackPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Example:

If the default fInitialDriveForce of your vehicle is 0.25, and the tuning system will raise the fInitialDriveForce value from 0.25 to 0.50, this means you have to set Config.AntiVehicleSpeedHackDriveForceMultiplier to 2.0

If the default fInitialDriveForce of your vehicle is 0.25, and the tuning system will raise the fInitialDriveForce value from 0.25 to 0.92, this means you have to set Config.AntiVehicleSpeedHackDriveForceMultiplier to 3.7 or 4.0

Config.AntiVehicleRocketBoost

true: Don't allow rocket boost on using vehicles
false: Allow rocket boost on using vehicles

Recommended: true -> set to true, will disable rocket boost on using vehicles

Config.AntiInstantBrake

true: Don't allow players to instant brake on their vehicles
false: Allow players to instant brake on their vehicles

Recommended: true -> set to true, will not allow players to instant brake on their vehicles multiple times

Config.AntiInstantBrakePenalty can be WARNING, KICK or BAN.
Recommended: BAN (WARNING will just delete the vehicle)

Config.AntiLongDistanceVehicle

true: Don't allow spawning vehicles at a long distance from the creator location
false: Allow spawning vehicles at a long distance from the creator location

Recommended: true -> set to true, will delete the vehicles spawned at a specific long distance (Config.MaxSpawnDistance meters) from the creator location. In case you use scripts (such as job scripts) that spawns vehicles at a long distance from the player you should better adjust the script to first teleport the player to the create vehicle location using SetEntityCoords for your player instead of raising the value for Config.MaxSpawnDistance. In case you have no access to the script due to encryption, you can change the value of Config.MaxSpawnDistance as needed or set Config.AntiLongDistanceVehicle to false in case the value for Config.MaxSpawnDistance is very high

Example of usage native SetEntityCoords before vehicle creation

Before

local vehicle = CreateVehicle(hash, x, y, z, 0.0, true, false)
TaskWarpPedIntoVehicle(PlayerPedId(), vehicle, -1)

After

SetEntityCoords(PlayerPedId(), x, y, z, true, true, true, false)
Wait(300)
local vehicle = CreateVehicle(hash, x, y, z, 0.0, true, false)
TaskWarpPedIntoVehicle(PlayerPedId(), vehicle, -1)

Config.AntiMultipleSameVehicles

true: Don't allow players spawn multiple same vehicles on the server
false: Allow players spawn multiple same vehicles on the server

Recommended: true -> set to true, will delete all the vehicles of the same model if the player spawn more than Config.MultipleSameVehiclesCounter same vehicle on the server

Config.AntiMultipleVehicles

true: Don't allow players have multiple same vehicles on the server
false: Allow players have multiple same vehicles on the server

Recommended: true -> set to true, will delete all the vehicles if the player have more than Config.MaxVehiclesCounter vehicles on the server

Config.AntiNoDriverVehicle

true: Don't allow players spawn vehicles without a driver
false: Allow players spawn vehicles without a driver

Recommended true -> set to true, will delete the vehicles that will have no driver, but by default it is set to false because you can have scripts inside your server that will spawn vehicles in a specific area without a driver in it. Usually, when a player spawns a vehicle, the player will be warped into vehicle, but you can have scripts that will not warp the player into vehicle (Example: Job scripts)

Config.AntiNoDriverExcludeVehicles

Config.AntiNoDriverExcludeVehicles - is a table that contains all vehicle that will be ignored by Config.AntiNoDriverVehicle check

Config.AntiChangeVehiclePlate

true: Don't allow players to change the vehicle plate
false: Allow players to change the vehicle plate

Recommended: false -> set to true, will prevent player to change the vehicle plate while he is in the vehicle

Config.AntiChangeVehiclePlatePenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiBlacklistedPlate

Config.AntiBlacklistedPlates
true: Don't allow blacklisted plates from Config.BlacklistedPlates on his vehicle
false: Allow any plate on his vehicle

Recommended: true -> set to true, will delete the vehicle of the player who changes the vehicle plate into a blacklisted plate from Config.BlacklistedPlates

Config.BlacklistedPlates

Config.BlacklistedPlates - is a table that contains all plates of vehicle that are blacklisted. If a player use one of this plates he will get penalty

Config.AntiPickup

true: Don't allow pickups on your server
false: Allow pickups on your server

Recommended: true -> set to true, will prevent player to collect or use a pickup item / object / prop (ground collectibles (Example: Health bag), reward (Example: Weapons), give weapon method (Example: Minigun))

Config.AntiPickupPenalty can be WARNING, KICK or BAN.
Recommended: BAN (ban will apply only for some methods)

Config.AntiSpamChat

true: Don't allow players to spam your chat
false: Allow players to spam your chat

Recommended: false -> set to true, will prevent players to spam your chat, but by default it is set to false, as you may already have this feature in your chat resource and would be not necesarry to also use it from the anticheat resource. In case you set it to true, the player will be restricted with a timeout of Config.MessagesTimeout seconds if the player spam Config.MessagesNumber messages in Config.MessagesTimer seconds.

Config.AntiBlacklistedWords

true: Don't allow words from Config.BlacklistedWords to be written on chat
false: Allow any word to be written on chat

Recommended: true -> will not let players to write one of these words on chat

Config.AntiBlacklistedWordsPenalty can be WARNING, KICK or BAN.
Recommended: WARNING (set to kick or ban can lead to troll from other players to tell them to write in chat that specific word and get penalty because of them)

Config.BlacklistedWords

Config.BlacklistedWords - is a table that contains all words that are not allowed to be written on chat

Config.AntiBlacklistedCommands

true: Don't allow commands from Config.BlacklistedCommands to be written on chat
false: Allow any commands to be written on chat

Recommended: false -> set to true, in case a player uses one of this commands he will get penalty, but by default it is set to true because of troll from other players to tell them to write in chat that specific command, he will get penalty because of them

Config.BlacklistedCommands

Config.BlacklistedCommands - is a table that contains all commands that are not allowed to be used by the players

Config.AntiSpamCommands

true: Don't allow players to spam commands
false: Allow players to spam commands

Recommended: true -> set to true, in case a player will spam a command for Config.AntiSpamCommandsNumber times in Config.AntiSpamCommandsTimer seconds, he will get penalty

Config.AntiSpamCommandsPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiVoiceExploit

true: Don't allow cheaters to use voice exploit
false: Allow cheaters to use voice exploit

Recommended: true -> set to true, in case a cheater uses functions that exploit the voice script to talk on a very long distance

Config.AntiVoiceExploitPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Event protection (SecuredServerEvents, SecuredClientEvents)

This feature will not allow cheaters to call trigger events from executors only for the secured events. When a secured trigger is called for a player from scripts normally, there will not be any problem, but if the player tries to call the trigger from executor he will be detected and get him banned

The event protection works on tokenizer principle, which means each protected event generates a token when a trigger server event is called from the server, and if the token does not match, the player will get banned

In order to install the event protection for your script, you have to add it manually. To add event protection for specific events, you have to add the event you want to protect in config on SecuredServerEvents or  SecuredClientEvents and add in fxmanifest of the resource you want to protect (from where the trigger belongs to) the following lines:

lua54 "yes"
client_script "@rac/source/client/trigger.lua"
server_script "@rac/source/server/trigger.lua"
shared_scripts {"@ox_lib/init.lua"}
dependencies {"ox_lib"}

Config.AntiSpamTriggers

true: Start count set trigger server events from Config.SpamTriggers table
false: Don't count trigger server events

Recommended: true -> set to true, will count each player trigger calls from Config.SpamTriggers table and give penalty if exceed the corresponding limit in a specific period of time (Config.AntiSpamTriggersTimer seconds)

Config.AntiSpamTriggersPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.SpamTriggers

Config.SpamTriggers - is a table that contains server side event names along with its limit which can be used / excuted / spammed by players in Config.AntiSpamTriggersTimer seconds in order to not affect your server

Config.AntiBlockedEvents

true: Don't allow players to call events from Config.BlockedEvents table
false: Allow players to call events from Config.BlockedEvents table

Recommended: true -> set to true, as if a player calls a trigger that does not even exist in your resources (server or client files), it is obviously that he is using an executor or a cheating menu.

Config.AntiBlockedEventsPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.BlockedEvents

Config.BlockedEvents - is a table that contains names of events registered on server or client and if a player executes them he will get penalty at first execution. In this table you can add different events which are not registered in your resources (server or client files)

Config.TriggerEventsExploitCheck

true: Prevent cheaters spam a trigger for himself or to all players (-1 argument in the events)
false: Don't prevent cheaters spam a trigger for himself or to all players (-1 argument in the events)

Recommended: true -> set to true, will prevent cheaters spam a trigger for himself for Config.TriggerEventsExploitRateLimit times in 10 seconds or to all players (-1 argument in the events) for Config.TriggerEventsExploitCheckLimit times in 10 seconds. Calling server events for himself can lead to player advantages (such as receiving server rewards), and calling server events to all the players (with -1 argument) can lead to server timeout, server crash or other exploits, so it is recommended to set it to true.

Config.TriggerEventsExploitCheckPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiBlacklistedAnims

true: Don't allow players to use blacklisted animations
false: Allow players to use any animation

Recommended: true -> will prevent players from using blacklisted animations that can be harmful for other players, by stopping the animation

Config.BlacklistedAnims

Config.BlacklistedAnims - is a table which contains the animation dictionaries and animation names that players are not allowed to use

Config.AntiAttachToPlayerWithEmote

true: Don't allow players to attach to other players through emotes
false: Allow players to attach to other players through emotes

Recommended: true -> will prevent players from attaching to other players through emotes that are not in the Config.AttachToPlayerWhitelistedEmotes table, but this option is set to false by default, because before enabling it, you need to add all paired (synced) animations used by your emote menu script to Config.AttachToPlayerWhitelistedEmotes.

Config.AttachToPlayerWhitelistedEmotes

Config.AttachToPlayerWhitelistedEmotes - is a table which contains the animation dictionaries and animation names that are allowed while a player is attached to another player

Config.AntiClearPedTasksEvent

true: Don't allow cheaters to manipulate other players
false: Allow cheaters to manipulate other players

Recommended: true -> set to true, will prevent cheaters to perform manipulation on players or vehicles (vehicle kick, fly all vehicles, fly all players, carry all players and more -> most of them are old methods, but newer methods are blocked by other anticheat features)

Config.AntiClearPedTasksEventPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiFreeze

true: Don't allow players or players' vehicles to get frozen
false: Allow players and players' vehicles to get frozen

Recommended: true -> set to true, will unfreeze the player or player's vehicle if he/it is frozen

Config.AntiFire

true: Don't allow fire on your server
false: Allow fire on your server

Recommended: true -> set to true, will prevent fire to be spawned on the server from any actions (including cheating methods that can spawn fire on players and vehicles)

Config.AntiVoid

true: Don't allow cheaters make players falling into void
false: Allow cheaters make players falling into void

Recommended: true -> set to true, will prevent players from falling into void (falling or teleporting into invalid positions)

Config.AntiSound

true: Don't allow sending sounds to all players
false: Allow sending sounds to all players

Recommended: true -> set to true, will prevent cheaters to send sounds on the server to all players

Config.AntiSoundPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiSpectate

true: Don't allow players to spectate other players
false: Allow players to spectate other players

Recommended: true -> set to true, will prevent players spectating other players (old methods from lua menus), but you have to add your staff members to whitelist first, as you may have spectate functions in your server (such as TX Admin or server script functions). The newer spectate functions from executors are using similar functions to noclip or freecam

Config.AntiSpectatePenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiFreecam

true: Don't allow players using freecam mode
false: Allow players using freecam mode

Recommended: true -> set to true, will prevent players to use freecam mode by checking the distance between player and his camera location

Config.AntiFreecamPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiFreecamDisplay

true: Display the name of players who are using freecam mode at the player and camera location
false: Don't display the name of players who are using freecam mode at the player and camera location

Recommended: true -> set to true, will display the name of players who are using freecam mode at the player and camera location in order to catch them

Config.AntiAttachPlayerDisplay

true: Display the name of players who are attached to you without seeing them
false: Don't display the name of players who are attached to you without seeing them

Recommended: true -> set to true, will display the name of players who are attached to you without seeing them as they may troll other players

Config.AntiFreecamShot

true: Don't allow players to shoot from freecam
false: Allow players to shoot from freecam

Recommended: true -> set to true, will prevent players to shoot with bullets from freecam

Config.AntiFreecamShotPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiFreecamFunctions

true: Don't allow players to use freecam functions
false: Allow players to use freecam functions

Recommended: true -> set to true, will prevent players to use freecam functions such as entity creations, explosions, projectiles, damage players, fire, particle effects

Config.AntiFreecamShotPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiNoclip

true: Don't allow players using noclip functions
false: Allow players using noclip functions

Recommended: false -> set to true, will prevent players to use noclip / fly functions, but by default it is set to false as you have to add your staff members to whitelist first.

Config.AntiNoclipPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiNoclipShot

true: Don't allow players to shoot from noclip
false: Allow players to shoot from noclip

Recommended: true -> set to true, will prevent players to shoot with bullets from noclip

Config.AntiNoclipShotPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiTeleport

true: Don't allow players to teleport multiple times
false: Allow players to teleport multiple times

Recommended: true -> set to true, will prevent players to teleport multiple times by monitoring the player movement and environment, but by default it is set to false as you have to add your staff members to whitelist first.

Config.AntiTeleportPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiTeleportToWaypoint

true: Don't allow players to teleport to waypoint
false: Allow players to teleport to waypoint

Recommended: true -> set to true, will prevent players to teleport to waypoint by monitoring the player action, player movement and environment, but by default it is set to false as you have to add your staff members to whitelist first.

Config.AntiTeleportToWaypointPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiInvisible

true: Don't allow players to be invisible
false: Allow players to be invisible

Recommended: false -> set to true, will prevent players to use invisible mode, but by default it is set to false as you have to add your staff members to whitelist first (invisible functions are used in invisible, noclip or other staff member functions)

Config.AntiInvisiblePenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiWalkUnderWater

true: Don't allow players to walk under water
false: Allow players to walk under water

Recommended: false -> set to true, will prevent players to walk under water, but by default it is set to false as there are very few cheats with such function and it is not that harmful

Config.AntiWalkUnderWaterPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiDisableHeadshot

true: Don't allow players to disable headshot damage
false: Allow players to disable headshot damage

Recommended: false -> set to true, will prevent players to use disable headshot damage (headshot critical shot) or no headshot functions (any shot in head will be a normal body shot), but by default it is set to false as you may have it already disabled in your server this type of feature in different situations.

Config.AntiDisableHeadshotPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiTargetEvade

true: Don't allow players using functions that do not allow players to target them
false: Allow players using functions that do not allow players to target them

Recommended: true -> set to true, will prevent players to use functions that do not allow players to target or aim them.

Config.AntiTargetEvadePenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiGodmode

true: Don't allow players using god mode functions
false: Allow players using god mode functions

Recommended: true -> set to true, will prevent players to use god mode functions. A player is considered using a god mode function if he is shot multiple times but take no damage in order to avoid false positive detections.

Config.AntiGodmodePenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiGodmode2

true: Don't allow players using god mode functions outside the safezones
false: Allow players using god mode functions outside the safezones

Recommended: false -> set to true, will prevent players to use god mode functions outside the safezones, but by default it is set to false because you have to set your server safezones first in Config.ServerSafezones table (position and radius). In order to set your server safezones you have to add the coordinates of all your server safezones and the radius of your server safezones. It is recommended to add 20.0 to your actual radius for the server safezone (for example if your radius is 100.0, you should set it to 120.0). A player is considered using a god mode function outside the safezones if he is shot outside the safezones multiple times but take no damage in order to avoid false positive detections.

Config.AntiGodmode2Penalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiDamageAbsorption

true: Don't allow players using damage absorption functions
false: Allow players using damage absorption functions

Recommended: true -> set to true, will prevent players to use damage absorption functions. A player is considered using a damage absorption function if he receives less damage than expected.

Config.AntiDamageAbsorptionPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiInfiniteHealth

true: Don't allow players have infinite health
false: Allow players have infinite health

Recommended: true -> set to true, will prevent players to exceed 200 health (theoretically it is not possible, but maybe there can be a way in cheating methods)

Config.AntiInfiniteHealthPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiRevive

true: Don't allow cheaters using revive function
false: Allow cheaters using revive function

Recommended: true + installation -> set to true, will prevent players using revive functions from outside the server (outside the server configuration). If a player revives from outside the server, the player will get penalty.

Config.AntiRevivePenalty can be WARNING, KICK or BAN.
Recommended: WARNING (as it is not that harmful to the server and you can see above their head a message + log that he revived from cheating method) or BAN (if you are confident you replaced everything correctly inside your server)

SetEntityHealth -> exports['racv2']:SetEntityHealth
NetworkResurrectLocalPlayer -> exports['racv2']:NetworkResurrectLocalPlayer 

Example

Before

SetEntityHealth(PlayerPedId(), 200)

After

if GetResourceState('racv2') == 'started' then
    exports['racv2']:SetEntityHealth(PlayerPedId(), 200)
else
    SetEntityHealth(PlayerPedId(), 200)
end

Before

NetworkResurrectLocalPlayer(spawn.x, spawn.y, spawn.z, spawn.heading, true, true, false)

After

if GetResourceState('racv2') == 'started' then
    exports['racv2']:NetworkResurrectLocalPlayer(spawn.x, spawn.y, spawn.z, spawn.heading, true, true, false)
else
    NetworkResurrectLocalPlayer(spawn.x, spawn.y, spawn.z, spawn.heading, true, true, false)
end

Config.AntiInfiniteArmour

Config.AntiInfiniteArmor
true: Don't allow players have infinite armour
false: Allow players have infinite armour

Recommended: true -> set to true, will prevent players to exceed 100 armour (theoretically it is not possible, but maybe there can be a way in cheating methods)

Config.AntiInfiniteArmourPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiArmour

true: Don't allow cheaters using armour function
false: Allow cheaters using armour function

Recommended: true + installation -> set to true, will prevent players using armour functions from outside the server (outside the server configuration). If a player armours from outside the server, the player will get penalty.

Config.AntiArmourPenalty can be WARNING, KICK or BAN.
Recommended: WARNING (as it is not that harmful to the server and you can see above their head a message + log that he armoured from cheating method) or BAN (if you are confident you replaced everything correctly inside your server)

SetPedArmour -> exports['racv2']:SetPedArmour
AddArmourToPed -> exports['racv2']:AddArmourToPed

Example

Before

SetPedArmour(PlayerPedId(), 100)

After

if GetResourceState('racv2') == 'started' then
    exports['racv2']:SetPedArmour(PlayerPedId(), 100)
else
    SetPedArmour(PlayerPedId(), 100)
end

Before

AddArmourToPed(PlayerPedId(), 25)

After

if GetResourceState('racv2') == 'started' then
    exports['racv2']:AddArmourToPed(PlayerPedId(), 25)
else
    AddArmourToPed(PlayerPedId(), 25
end

Config.AntiInfiniteStamina

true: Don't allow players using infinite stamina functions
false: Allow players using infinite stamina functions

Recommended: false -> set to true, will prevent players to use infinite stamina functions, but by default it is set to false, as this kind of functions is not harmful to your server and it's useless. This feature has been created just to exist.

Config.AntiInfiniteStaminaPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiRagdoll

true: Don't allow players to use ragdoll function
false: Allow players to use ragdoll function

Recommended: false -> set to true, will prevent players to use ragdoll function, but by default it is set to false as you maybe use ragdoll function while the player is dead or other functions as an emote.

Config.AntiRagdollPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiNightVision

true: Don't allow players using night vision
false: Allow players using night vision

Recommended: true -> set to true, will prevent players to use night vision

Config.AntiNightVisionPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiThermalVision

true: Don't allow players using thermal vision
false: Allow players using thermal vision

Recommended: true -> set to true, will prevent players to use thermal vision

Config.AntiThermalVisionPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiMenyoo

true: Don't allow players using menyoo
false: Allow players using menyoo

Recommended: true -> set to true, will prevent players to use menyoo functions (creating objects/props)

Config.AntiMenyooPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiTrackPlayers

true: Don't allow players to track other players on the map
false: Allow players to track other players on the map

Recommended: false -> set to true, will prevent players to track other players on the map with blips/sprites, but by default it is set to false as you have to add your staff members to whitelist first, as you may have in the server functions for staff members that will display blips/sprites for all players on the map.

Config.AntiTrackPlayersPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiSpeedHack

true: Don't allow speed hack on player ped
false: Allow speed hack on player ped

Recommended: true -> set to true, will prevent players to run faster than normally (speed limitation on player ped)

Config.AntiSpeedHackPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiTinyPed

true: Don't allow players to use tiny ped functions from cheating methods
false: Allow players to use tiny ped functions from cheating methods

Recommended: true -> set to true, will prevent players to use tiny ped functions from cheating methods (make the player ped smaller)

Config.AntiTinyPedPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiSuperJump

true: Don't allow players using super jump
false: Allow players using super jump

Recommended: true -> set to true, will prevent player to use super jump functions (also get limited because of Config.AntiSpeedHack, so false bans may be only rare edge cases)

Config.AntiSuperJumpPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiFallingPeds

true: Don't allow cheaters make players falling
false: Allow cheaters make players falling

Recommended: true -> set to true, will prevent players from falling through the map, force fall (ragdolling by someone who is cheating)

Config.AntiClonePed

true: Don't allow clone peds on your server
false: Allow clone peds on your server

Recommended true -> set to true, will delete all spawned peds that has your ped model (mp_m_freemode_01 or mp_f_freemode_01), but it is not a player

Config.AntiAggressivePeds

true: Don't allow aggressive peds on your server
false: Allow aggressive peds on your server

Recommended: true -> set to true, will delete all spawned peds that become aggressive or target or going to attack you

Config.AntiCrasher

true: Don't allow players to crash your server
false: Allow players to crash your server

Recommended: true -> set to true, will prevent players to crash your server with different crashing methods. Crashing the server is possible due to not updating the artifacts. Updating your artifacts is the best fix.

Config.AntiDevTools

true: Don't allow players using dev tools
false: Allow players using dev tools

Recommended: true -> set to true, will prevent player to access the dev tools (a player does not need access to see what is in dev tools. In this way, there are no risk of stealing NUI from the server or executing code using JavaScript)

Config.AntiDevToolsPenalty  can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiSoloSession

true: Don't allow players to join solo session
false: Allow players to join solo session

Recommended: true -> set to true, will prevent players to be on solo session (isolated session without any other players) in order to avoid issues with tracking that player who is on solo session or other server issues (desync, lag, crash)

Config.AntiFakeDesync

true: Don't allow players using fake desync functions
false: Allow players using fake desync functions

Recommended: true -> set to true, will prevent players to using fake desync functions that can manipulate their position on their client without being seen or missing player details

Config.AntiFakeDesyncPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiCombatRoll

true: Don't allow players to combat roll while they are aiming
false: Allow players to combat roll while they are aiming

Recommended: false -> set to true, will prevent players to combat roll while they are aiming, but by default it is set to false because you maybe prefer this to not be prevented in players' gun fights. This feature also prevent infinite combat roll from cheats.

Config.AntiInfiniteRoll

true: Don't allow players infinite combat roll
false: Allow players infinite combat roll

Recommended: false -> set to true, will prevent players to infinite combat roll

Config.AntiBlacklistedOutfits

true: Don't allow players to equip blacklisted outfits
false: Allow players to equip any outfit

Recommended: true -> set to true, will prevent players to use outfits that are blacklisted by you in the Config.BlacklistedOutfitsMale (for ped mp_m_freemode_01) or Config.BlacklistedOutfitsFemale (for ped mp_f_freemode_01) tables, but by default this feature is set to false in order to set your blacklisted outfits first.

Config.AntiBlacklistedOutfitsPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Example:

{ face = 0, mask = 207, hair = 1, hands = 171, pants = 239, bag = 0, shoes = 0, accessory = 0, undershirt = 15, kevlar = 0, badge = 0, jacket = 444 },

Example:

{ hands = 213, pants = 290, jacket = 607 },

Config.AntiCopyOutfit

true: Don't allow players to copy other player's outfit
false: Allow players to copy other player's outfit

Recommended: true -> set to true, will prevent players to copy or steal the outfit from other players, but by default, this feature is set to false as it can be useless for your server and it is not really needed to punish a player for copying or stealing the outfit of other players, or to make sure that does not impact with any script from your server.

Config.AntiCopyOutfitPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.AntiRandomizeOutfit

true: Don't allow players to randomize outfit multiple times
false: Allow players to randomize outfit multiple times

Recommended: true -> set to true, will prevent players to randomize their outfit multiple times, even though you may have scripts beside the the clothing system that can randomize the player outfit; the detection will not be triggered in such cases

Config.AntiRandomizeOutfitPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.UseModuleScreenshotBasic

true: Use screenshot-basic resource as module for screenshots capture
false: Don't use screenshot-basic resource as module for screenshots capture

Recommended: true -> set to true, will check if you have installed the screenshot-basic resource in your server

Config.AntiBlacklistedWordsOnScreen

true: Start monitoring player's screen for blacklisted words from Config.BlacklistedWordsOnScreen table
false: Don't monitor player's screen for any word

Recommended: true -> set to true, will prevent players to use menus by detecting blacklisted words on the player's screen through OCR (Optical Character Recognition) system

Config.AntiBlacklistedWordsOnScreenPenalty can be WARNING, KICK or BAN.
Recommended: BAN

Config.BlacklistedWordsOnScreen

Config.BlacklistedWordsOnScreen - is a table which contains a list of words that can be found in majority of cheating menus