# albm\_citizenblock

<figure><img src="/files/WETBxZQH0qEF0uh5uPiQ" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
**ATTENTION**

Not everything can be blocked because for some files there is no appropriate [data\_file](https://docs.fivem.net/docs/game-references/data-files/) for fxmanifest to be loaded correctly.

\
To add more blockades to be overwritten by this script you need to add it correctly. If the file is added not correctly, the script may stop working, be careful.
{% endhint %}

## 1 ADDING NEW TYPE OF BLOCK

If you want to add a new block then the location of the file in the albm\_citizenblock folder must match the location of this file in Open IV

Example: \
&#x20;   **@albm\_citizenblock**/common/data/effects/liquidfx.dat\
&#x20;   **Grand Theft Auto V**/common.rpf/data/effects/liquidfx.meta\
\
&#x20;   **@albm\_citizenblock**/meta/time.xml\
&#x20;   **Grand Theft Auto V**/common.rpf/data/time.xml

Some files to append to the **gta5.meta** file located on this location @albm\_citizenblock\meta\\**gta5.meta**

```xml

<Item>
	<filename>resources:/albm_citizenblock/data/effects/liquidfx.dat</filename>
	<fileType>LIQUIDFX_FILE</fileType>
</Item>

<Item>
  	<filename>resources:/albm_citizenblock/meta/time.xml</filename>
	<fileType>TIME_FILE</fileType>
</Item>

```

Each new file must be added to **\_\_resource.lua** and and for the most part there must be an appropriate **data\_file** witch we get from **gta5.meta** of **`<fileType>`**

```lua

files {
    'data/effects/liquidfx.dat',
    'meta/time.xml',
}

data_file "TIME_FILE" 'time.xml'

```

In the case of props, i.e. .**ytd**, **.ydr**, just add to the **stream** folder


---

# 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://docs.vames-store.com/free-assets/albm_citizenblock.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.