# 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 <mark style="color:yellow;">HUNK\_AC.AntiDumpResources</mark>

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

{% hint style="warning" %}
do not add the scripts you bought from Tebex into <mark style="color:yellow;">HUNK\_AC.AntiDumpResources</mark>

do not add vehicles/maps/weapons/clothes into <mark style="color:yellow;">HUNK\_AC.AntiDumpResources</mark>
{% endhint %}

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

then use the <mark style="color:yellow;">antidump</mark> command

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

<mark style="color:purple;">this resource is using @ sign for importing files from another resources</mark>

In this case you need to go to the resource and open the fxmanifest.lua or \_\_resource.lua

then find the <mark style="color:yellow;">@</mark> sign that is used to import a client file from another script

and cut it out from <mark style="color:yellow;">client\_script</mark> or <mark style="color:yellow;">client\_scripts</mark>

then add the imported file into another line like this:

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

### Example 1

<mark style="color:yellow;">default fx file:</mark>

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

new fx file

<pre class="language-lua"><code class="lang-lua">client_script '@es_extended/locale.lua' ignore 'yes'

<strong>client_scripts {
</strong>	'locales/en.lua',
	'client.lua',
	'Config.lua',
}
</code></pre>

### Example 2

<mark style="color:yellow;">default fx file:</mark>

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

<mark style="color:yellow;">new fx file:</mark>

<pre class="language-lua"><code class="lang-lua">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'
<strong>
</strong><strong>client_scripts {
</strong>    'client.lua'
}
</code></pre>

### Example 3

#### <mark style="color:yellow;">default fx file:</mark>

```lua
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'
}
```

#### <mark style="color:yellow;">new fx file:</mark>

```lua
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'
}
```

{% hint style="warning" %}
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
{% endhint %}

#### after you modify the fx file save it and use <mark style="color:yellow;">antidump</mark> command again

then restart the server

## <mark style="color:purple;">other commands for anti-dump part:</mark>

* <mark style="color:yellow;">antidumpon</mark> : 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: <mark style="color:yellow;">antidumpon qb-vehicleshop</mark>
* <mark style="color:yellow;">noantidump</mark> : will uninstall the anti-dump from resources
* <mark style="color:yellow;">noantidumpon</mark> : will uninstall the anti-dump from a single resource

&#x20;example: <mark style="color:yellow;">noantidumpon qb-vehicleshop</mark>

## <mark style="color:purple;">How about UI files ?</mark>

but how about the UI files like <mark style="color:blue;">HTML</mark> or <mark style="color:yellow;">js</mark> files?

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

for <mark style="color:yellow;">js</mark> files <https://obfuscator.io/>

for <mark style="color:blue;">HTML</mark> files <https://www.wmtips.com/tools/html-obfuscator/>

for <mark style="color:red;">CSS</mark> files <http://cssobfuscator.com/>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://unique-store.gitbook.io/hunk-ac/overview/dumping-protection.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
