> For the complete documentation index, see [llms.txt](https://corem.gitbook.io/corem/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://corem.gitbook.io/corem/crm-multicharacter/common-issues.md).

# Common Issues

### CreatePed Error

<details>

<summary><strong>CreatePed Native Failing</strong></summary>

Some users report an error that looks like it comes from **crm-multicharacter**, especially because it loads early when joining the server. However, this is a common misunderstanding.

<figure><img src="/files/uOjSsSSO5nFW3S3CDnWK" alt="CreatePed error native"><figcaption></figcaption></figure>

This happens when the server tries to create a ped (character model), and the native function fails.

**Important: This Is&#x20;*****Not*****&#x20;a `crm-multicharacter` Problem**

crm-multicharacter simply loads the ped that your server provides.\
If that ped cannot be created, the problem comes from your **server files**, not from the script.

**Common Causes**

The CreatePed failure is usually caused by one of the following:

**1. Wrong or unstable server artifacts**

Outdated, broken, or experimental artifacts can break ped creation native.

**2. Broken or incompatible clothing packs**

Addon clothing, DLC packs, or custom models with:

* missing textures
* wrong model structure
* corrupted YDD/YMT files

These will crash the ped creation process.

**3. Conflicting or corrupted streamed ped files**

If two resources stream the same file or a corrupted outfit, CreatePed may fail.

**4. YMT Limit Reached**

If your clothing pack exceeds GTA’s native **YMT component limits**, peds will stop loading correctly.

**✅ How to Fix It**

* Change your server artifacts
* Test your clothing packs one-by-one
* Remove or repair corrupted clothing packs

</details>

***

### ID Card / Driver License Not Working

<details>

<summary>ID Card / Driver License Not Working with <code>crm-multicharacter</code> + <code>qbx_idcard</code></summary>

**🔧 Fix**

Go to:

```
crm-multicharacter/crm-open/crm-server/crm-main.lua
```

Replace the **`crm_starter_items`** function with:

```lua
function crm_starter_items(crm_framework, crm_source, crm_identifier, crm_data)
    Citizen.Wait(1000)
    local crm_starting = crm_config.crm_items
    if crm_starting.crm_enable then
        if crm_framework == "crm_esx" then
            for _, crm_item in pairs(crm_starting.crm_items) do
                local crm_metadata = {}
                crm_inv.crm_add(crm_source, crm_item.crm_item, crm_item.crm_amount, false, crm_metadata, "Starting Items")
            end
        else
            local crm_citizenid = crm_lib.crm_getplayerid(crm_source)
            local crm_info = crm_data.charinfo
            for _, crm_item in pairs(crm_starting.crm_items) do
                local crm_metadata = {}
                if crm_item.crm_item == "id_card" then
                    crm_metadata = exports.qbx_idcard:GetMetaLicense(crm_source, {'id_card'})
                elseif crm_item.crm_item == "driver_license" then
                    crm_metadata = exports.qbx_idcard:GetMetaLicense(crm_source, {'driver_license'})
                end
                crm_inv.crm_add(crm_source, crm_item.crm_item, crm_item.crm_amount, false, crm_metadata, "Starting Items")
            end
        end
    end
end

```

#### ✅ Result

This ensures ID cards and driver licenses are created with the correct metadata, allowing **qbx\_idcard** to display and use them properly.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://corem.gitbook.io/corem/crm-multicharacter/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.