Reason Anticheat Documentation
  • Introduction
  • Information
  • Links
  • FAQ
  • Resources Documentation
    • 🟣Reason Anticheat
      • Features
      • Dependencies
      • Commands
      • Logs
      • Menu
      • Installation
      • Configuration
      • Webhooks
      • Bans
      • Showcase
      • Set your game build and artifacts
      • Server crash prevention
      • Secure your server
    • 🟣Anti aimbot
    • 🟣Anti trigger event protection
    • 🟣Anti dumper
    • 🟣Anti weapons
    • 🟣Framework protections
Powered by GitBook
On this page
  • Description
  • Usage
  • Showcase
  1. Resources Documentation

Anti dumper

PreviousAnti trigger event protectionNextAnti weapons

Last updated 2 months ago

Anti dump protection is a standalone resource that prevent players to dump your client files in case you do not want to use escrow system provided by FiveM. This feature is collected from Reason Anticheat and can be used separately in case you need only this feature.

This resource uses Asset Escrow System provided by FiveM.

Description

Anti dump protection feature will prevent players to dump your client files. This command can be used in case you do not want to escrow your resource on keymaster and keep your resource open source in server. If a player dumps your resource or server he will not get banned, but he will not receive the client files if the resource is protected. We encourage you to use escrow system, but in case you do not want to use it, you can use this resource in order to prevent dumping your client file.

Usage

Command racdumpprotection [install] [resource name] will add dump protection to the mentioned resource. This feature will not allow players to dump your client files. When this command is executed in server console the fxmanifest of your resource will be affected and it creates a backup folder with all your client files in open source so you can modify your code.

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

Make sure to create a backup of your resource before you use this command in case you want to recover it.

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 files from backup folder you do not have to add them. This is how this feature works.

In case the command for adding dump protection to the resource does not work properly for you, you can add the dump protection manually. To add dump protection manually you have to create a new folder inside your resource called backup and move all your client files from initial resource to new folder backup that you created (you can use cut files function) and add in fxmanifest the following lines:

lua54 "on"
server_script "@antidump/source/server/dump.lua"
client_script "@antidump/source/client/dump.lua"

Showcase

The racdumpprotection command is no longer working on the latest server artifacts. In order to make it work, you must temporarily turn off your server and switch to an older artifacts version where the command is still supported, for example the Last Recommended (7290). After you switched to an older artifacts version, run the command to install dump protection on all your resources where you need the dump protection. After you added the dump protection to your needed resources, you can revert back to the latest artifacts version. If you do not want to change your artifacts and then revert to your initial artifacts, you can do the process of adding dump protection manually.

🟣
Resource testresource before executing command
Execute command to add dump protection
Resource testresource after executing command
Dumper cannot see the client file because it is in the backup folder, not as it is declared in lines 10 to 12 in fxmanifest. Client file is still working even through it is not declared in fxmanifest with the help of lines 2 to 3 which have been added when the command was executed