Commands

Commands list

• Version
• Scanner
• Refresh config
• Help
• Clear everything
• Clear vehicles
• Clear peds
• Clear objects
• Bans
• Unban
• Unban all

Commands usage

Help

Command rachelp in server console will show you all the available commands:

racversion - The anticheat version that you are running on your server
racscan - Scan your server for backdoors
racdeletemalware - Scan your server for malware and neutralize all infected resources
racrefreshconfig - Refresh your config file after updating fields from config file
clearall - Clear vehicles, peds, objects
clearvehicles - Clear vehicles
clearpeds - Clear peds
clearobjects - Clear objects
racbans - Bans list
racunban <Id> - Unban player from anticheat
racunbanall - Unban all players from anticheat

Version

Command racversion in server console will show the anticheat version that you are running on your server.

Scanner

Command racscan in server console will print backdoors such as hidden / obfuscated commands or cipher or malware content from your server files which were found in your server resources that can have a risk or even high risk to your server. If a backdoor has been found, you can contact support to give you more information about the found backdoor by inspecting found code.

Delete malware

Command racdeletemalware in server console will neutralize malware content from your server files which were found in your server resources that can have a very high risk to your server. If a backdoor has been found, you can contact support to give you more information about the found backdoor by inspecting found code.

Refresh config

Command racrefreshconfig in server console will refresh your config file after updating fields from config file without restarting/ensuring the anticheat resource.

We recommend to use racrefreshconfig in the console to apply changes to your config file instead of restarting/ensuring the anticheat resource. Avoid restarting the resource while players are online, as the live map feature causes long load times and cache saving delays due to large amount of files.

Clear Everything

Command clearall in server console will delete every unused vehicles, peds and objects on the server. You can change this command from config file (Config.ClearAllCommand).

Clear vehicles

Command clearvehicles in server console will delete every unused vehicles on the server. You can change this command from config file (Config.ClearVehiclesCommand).

Clear ped

Command clearpeds in server console will delete every ped on the server. You can change this command from config file (Config.ClearPedsCommand).

Clear objects

Command clearobjects in server console will delete every object / prop on the server. You can change this command from config file (Config.ClearObjectsCommand).

Ban list

Command racbans in server console will print on console all bans from bans.json file. The result will show the Id, Player name, Reason and Date. You can change this command from config file (Config.BanListCommand)

Example of ban list result

Unban player from server console

Command racunban <Id> in server console will remove (unban) the player with the entered Id from the anticheat ban list. Before enter the Id to unban the player, you have to use the Ban list command (Config.BanListCommand) in order to get the Id you want to remove (unban) or check the bans.json file and get the "id". You can change the unban player command from config file (Config.UnbanCommand).

The Id you enter is not the player id from your server, the Id is the number of ban got in the ban list. You have get the Id by typing Ban list command (Config.BanListCommand) in server console and it will provide as first element for each ban or get it from bans.json file, the field "id"

As an example for the above ban list, if we want to remove the player with Id 3, we have to type racunban 3

Example of unban player

By unbanning a player from server console with Config.UnbanCommand, the file bans.json will also get updated.

Unban all players from server console

Command racunbanall will remove (unban) all players from the anticheat ban list. You can change this command from config file (Config.UnbanAllCommand)

By unbanning all players from server console with Config.UnbanAllCommand, the file bans.json will also get updated.

Event Protection

Make sure that you started the anticheat resource as first resource in server.cfg, above your resource list

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 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"}

After server restart events from resource testresource have been protected

Showcase available on Anti trigger event protection category

Dump protection

Make sure that you started the anticheat resource as first resource in server.cfg, above your resource list.

This feature will not allow cheaters to dump the client and NUI files only for secured resources. When a cheater will dump the resource, the client and NUI files will not be received.

Make sure to create a backup of your resource before you secure your resource from dump.

In order to make the dump protection working, it requires manually implementation by following the next steps:
1. Turn off your server
2. Add the following lines in the fxmanifest of the resource you want to secure

lua54 "yes"
server_script "@rac/source/server/dump.lua"
client_script "@rac/source/client/dump.lua"
files {'html/index.html'}
ui_page 'html/index.html'

3. Create a backup folder inside the resource you want to secure

Resource testresource before implementing the dump protection

Resource testresource after adding backup folder

4. Move the client and NUI files from the resource you want to secure inside the backup folder
5. Add the index.json file from assets archive (.rar) from the anticheat resource (rac > assets.rar > backup) in the backup folder of the resource you want to secure
6. Add the index.html file from assets archive (.rar) from the anticheat resource (rac > assets.rar > html) in the html folder of the resource you want to secure

Resource testresource after placing client, NUI files, index.json list of client and NUI files, and index.html file that need to be secured

The index.json file inside the backup folder of the resource that you want to secure contains the name of client and NUI files (example shown above: client file c_testresource.lua and NUI files index.html, style.css, script.js). In case there are more client or NUI files, the list can continue with the name of all files, but the list has to respect the json syntax

[
  "c_testresource.lua",
  "index.html",
  "style.css",
  "script.js"
]

Do not change the name of folder backup. Keep it named backup. In case you rename it, the resource will not work.

Even though the fxmanifest of your resource does not contain the client and NUI files from backup folder you do not have to add them. This is how this feature works, so do not change anything in fxmanifest beside adding the shared lines from above on point (2).

Showcase available on Anti dumper category