# Common Issues

<details>

<summary>Ilegal mix of collations</summary>

<figure><img src="/files/u4lnudQAxQaedFFbdkja" alt=""><figcaption><p>Example of Error</p></figcaption></figure>

{% hint style="info" %}
Works for every script with this error
{% endhint %}

### Solution for PhpMyAdmin

1. Open your PhpMyAdmin Panel
2. Select Database which u are using for your FiveM Server in Panel on Left Side
3. Click `Operations` Section on Top of Panel

<img src="/files/TzrRtuLJsR0YAvtUMcTx" alt="" data-size="original">

4. Scroll to `Collation` Section on **Bottom** of `Operations` Page
5. Select `utf8mb4_unicode_ci` from Dropdown List - Make sure to check 2 checkboxes and click `Go`

<figure><img src="/files/1x9vsKdSJwv4vujAB7nz" alt=""><figcaption><p>Example</p></figcaption></figure>

{% hint style="danger" %}
\[QB] Cannot change column 'citizenid': used in a foreign key constraint 'fk\_citizenid' of table 'database\_name.player\_groups'
{% endhint %}

Solution for this Error

1. Go to `player_groups` table - Open `Structure` Page and Select `Relation view`

<div align="left"><figure><img src="/files/eYr69RnQYPPrZZlr761u" alt=""><figcaption><p>Example</p></figcaption></figure></div>

2. Click `Drop` on `fk_citizenid` key and Change Collation again :)

<div align="left"><figure><img src="/files/uLqM4td0csoSUCEQwWeZ" alt=""><figcaption><p>Example</p></figcaption></figure></div>

### Solution for HeidiSQL

1. Open your database and find tables from error in your server console - in my example it will be `players` and `doj_citizen_profiles`

<figure><img src="/files/QHdKpLmO76yyDTa3lFBz" alt=""><figcaption><p>Example of Error</p></figcaption></figure>

2. Go to first table \[in my example it will be `players`] and check collation of every column. Collation should be the same in every column and in both tables. If they are different, double click on it and change. Do the same with second table.

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

</details>

<details>

<summary>GPT won't open</summary>

To ensure your job is correctly configured, you need to verify the `config.lua` file of the GPT system. Follow these steps:

1. Open the `config.lua` file in your preferred text editor.
2. Locate the section where jobs are defined.
3. Check if your specific job is listed and configured correctly.
4. Make any necessary adjustments to ensure it aligns with your server’s requirements.
5. Save the file and restart the server to apply changes.

</details>

<details>

<summary>I see all options on target without required job!</summary>

You probably use qb-core and ox\_target. This target system doesn't support qb-core anymore on version higher than 1.16.0. You can revert your ox\_target to 1.16.0 or put files below to your current ox\_target.

Path - `ox_target/client/framework`

{% file src="/files/Nsv48eLMaspCetoSwBTZ" %}

Path - `ox_target/client` \[replace with utils.lua]

{% file src="/files/tiEN8WXHS8H2QR9bOqVA" %}

</details>

<details>

<summary>Resources are taking a lot of performance/ms in resmon</summary>

If u are using Anti-Cheat, try to temporary disable it. Some of anti-cheats override game natives with their functions etc. This can cause some performance issues.

</details>


---

# 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://piotreq-scripts.gitbook.io/piotreq-scripts/information/common-issues.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.