👮Dumping Protection

first, to use the anti-dump feature you need to go inside configs/server/base.lua

at the end of the file you can find HUNK_AC.AntiDumpResources

you need to add the scripts that you want to protect your client lua files against dumpers

do not add the scripts you bought from Tebex into HUNK_AC.AntiDumpResources

do not add vehicles/maps/weapons/clothes into HUNK_AC.AntiDumpResources

after you have put all the resources now restart the anti-cheat and go to the server console

then use the antidump command

while you are installing the anti-dump you might face some messages like this:

this resource is using @ sign for importing files from another resources

In this case you need to go to the resource and open the fxmanifest.lua or __resource.lua

then find the @ sign that is used to import a client file from another script

and cut it out from client_script or client_scripts

then add the imported file into another line like this:

client_script '@es_extended/locale.lua' ignore 'yes'

Example 1

default fx file:

client_scripts {
	'@es_extended/locale.lua',
	'locales/en.lua',
	'client.lua',
	'Config.lua',
}

new fx file

client_script '@es_extended/locale.lua' ignore 'yes'

client_scripts {
	'locales/en.lua',
	'client.lua',
	'Config.lua',
}

Example 2

default fx file:

client_scripts {
    '@PolyZone/client.lua',
    '@PolyZone/BoxZone.lua',
    '@PolyZone/EntityZone.lua',
    '@PolyZone/CircleZone.lua',
    '@PolyZone/ComboZone.lua',
    'client.lua'
}

new fx file:

client_script '@PolyZone/client.lua' ignore 'yes'
client_script '@PolyZone/BoxZone.lua' ignore 'yes'
client_script '@PolyZone/EntityZone.lua' ignore 'yes'
client_script '@PolyZone/CircleZone.lua' ignore 'yes'
client_script '@PolyZone/ComboZone.lua' ignore 'yes'

client_scripts {
    'client.lua'
}

Example 3

default fx file:

client_script '@Protector/loader.lua'

shared_script {
    'config.lua',
    '@qb-core/shared/locale.lua',
    'locales/en.lua',
    'locales/*.lua'
}

client_scripts {
    'client.lua'
}

server_scripts {
    '@oxmysql/lib/MySQL.lua',
    'server.lua'
}

new fx file:

client_script '@Protector/loader.lua' ignore 'yes'

shared_script {
    'config.lua',
    '@qb-core/shared/locale.lua',
    'locales/en.lua',
    'locales/*.lua'
}

client_scripts {
    'client.lua'
}

server_scripts {
    '@oxmysql/lib/MySQL.lua',
    'server.lua'
}

do not touch server and shared files

means do not touch server_script / server_scripts / shared_script

because we only do it on client files

after you modify the fx file save it and use antidump command again

then restart the server

other commands for anti-dump part:

• antidumpon : used for installing the anti-dump on a single resource, it can be a new resource that you have added to the server recently, example: antidumpon qb-vehicleshop

• noantidump : will uninstall the anti-dump from resources

• noantidumpon : will uninstall the anti-dump from a single resource

example: noantidumpon qb-vehicleshop

How about UI files ?

but how about the UI files like HTML or js files?

if your resource is important on the UI side then you can also use these sites for obfuscating the files

for js files https://obfuscator.io/

for HTML files https://www.wmtips.com/tools/html-obfuscator/

for CSS files http://cssobfuscator.com/