# FAQ

## How to do localization <a href="#how-to-do-localization" id="how-to-do-localization"></a>

{% code title="0r-vehiclekeys/config/main.lua" %}

```lua
Locale = 'en', -- You specify the primary language of your script. (Supported Locales: en)
```

{% endcode %}

If the language you are using is not supported by the script, you can copy the en.json file and edit its contents for your own language. Then, save the file with a name that includes your language abbreviation (e.g., en, tr) and enter the file name you set in the config.

You can also send this translation file you have set up to the user named **No.1 (vezironi)** on Discord, and your translation file will be added to the script in the next update.

## How can i integrate my inventory ? <a href="#how-can-i-integrate-my-inventory" id="how-can-i-integrate-my-inventory"></a>

| Scripts          | Status                   |
| ---------------- | ------------------------ |
| qb-inventory     | Supported                |
| ox\_inventory    | Supported                |
| ps-inventory     | Supported but not tested |
| tgiann-inventory | Supported but not tested |
| codem-inventory  | Supported but not tested |

As long as you do not configure the script differently, if you are using a script supported by the script, it will automatically detect it and configure itself accordingly.

Copy and paste any script file from `0r-vehiclekeys/modules/inventory/`, then rename the folder to the name of the script you want. You can then integrate your script by looking at the other modules. It has a very modular and understandable file structure.

## How can i integrate my target script ? <a href="#how-can-i-integrate-my-target-script" id="how-can-i-integrate-my-target-script"></a>

| Scripts             | Status                   |
| ------------------- | ------------------------ |
| ox\_target          | Supported                |
| qb-target           | Supported                |
| sleepless\_interact | Supported but not tested |
| drawtext            | Supported                |

As long as you do not configure the script differently, if you are using a script supported by the script, it will automatically detect it and configure itself accordingly.

Copy and paste any script file from `0r-vehiclekeys/modules/target/`, then rename the folder to the name of the script you want. You can then integrate your script by looking at the other modules. It has a very modular and understandable file structure.

## How can i integrate my dispatch script ? <a href="#how-can-i-integrate-my-target-script" id="how-can-i-integrate-my-target-script"></a>

| Scripts             | Status                   |
| ------------------- | ------------------------ |
| bub\_mdt            | Supported but not tested |
| cd\_dispatch        | Supported but not tested |
| lb-tablet           | Supported but not tested |
| linden\_outlawalert | Supported but not tested |
| ps-dispatch         | Supported but not tested |
| qs-dispatch         | Supported but not tested |
| redutzu-mdt         | Supported but not tested |
| tk\_dispatch        | Supported but not tested |

As long as you do not configure the script differently, if you are using a script supported by the script, it will automatically detect it and configure itself accordingly.

Copy and paste any script file from `0r-vehiclekeys/modules/`dispatch`/`, then rename the folder to the name of the script you want. You can then integrate your script by looking at the other modules. It has a very modular and understandable file structure.


---

# 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.0resmon.org/0resmon/0resmon-1/0r-resources/0r-vehicle-keys/faq.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.