> For the complete documentation index, see [llms.txt](https://zloma-scripts.gitbook.io/zloma-scripts/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zloma-scripts.gitbook.io/zloma-scripts/zloma_core-free/configuration.md).

# Configuration

zloma\_core is **plug-and-play** — zero configuration required. Everything is auto-detected on resource start.

This page covers optional configuration for advanced users.

***

## Auto-Detection (Default)

By default, all settings in `shared/config.lua` are set to `'auto'`:

```lua
ZlomaCore.Config.Manual = {
    Framework = 'auto',
    Inventory = 'auto',
    Billing = 'auto',
    Notification = 'auto',
    Appearance = 'auto',
    Keys = 'auto',
    Dispatch = 'auto',
    Target = 'auto',
    Fuel = 'auto',
    Society = 'auto'
}
```

zloma\_core checks which resources are started and picks the right one automatically.

***

## Manual Override

If auto-detection picks the wrong system (rare) or you want to force a specific one:

```lua
ZlomaCore.Config.Manual = {
    Framework = 'ESX',              -- Force ESX
    Inventory = 'ox_inventory',     -- Force ox_inventory
    Billing = 'auto',               -- Still auto-detect billing
    Notification = 'ox_lib',        -- Force ox_lib notifications
    Appearance = 'illenium-appearance', -- Force appearance integration
    Keys = 'auto',                  -- Still auto-detect keys
    Dispatch = 'ps-dispatch',       -- Force a dispatch integration
    Target = 'ox_target',           -- Force ox_target
    Fuel = 'auto',                  -- Still auto-detect fuel
    Society = 'auto'                -- Still auto-detect society
}
```

You can mix `'auto'` and manual values freely.

**When to use manual:**

* Custom resource names that don't match expected names
* Multiple systems installed but you want to force one
* Testing/debugging a specific system
* Slightly faster startup (skips detection for that category)

***

## Debug Mode

Enable detailed console logging:

```lua
ZlomaCore.Config.Debug = true
```

This outputs every detection step, every export call, and every fallback — useful for troubleshooting.

***

## Timeouts

Adjust timing if you have slow-starting resources:

```lua
ZlomaCore.Config.Timeouts = {
    CallbackDefault = 5000,   -- Callback timeout (ms)
    InitWait = 500,           -- System initialization wait (ms)
    DetectionWait = 200,      -- Detection loop wait (ms)
    PollingInterval = 50      -- Callback polling interval (ms)
}
```

Normally you don't need to touch these.

***

## Appearance Support

`zloma_core` also detects supported clothing and appearance resources on the client side.

Use `ZlomaCore.Config.Manual.Appearance` only if you need to force a specific resource.

Supported values:

* `illenium-appearance`
* `qs-appearance`
* `crm-appearance`
* `qb-clothing`
* `rcore_clothing`
* `tgiann-clothing`
* `p_appearance`
* `esx_skin`

***

## Dispatch Support

`zloma_core` can auto-detect or manually force a police dispatch system for resources like `zloma_keys`.

Use `ZlomaCore.Config.Manual.Dispatch` when multiple dispatch resources are installed or when you want deterministic routing.

Supported values:

* `ps-dispatch`
* `piotreq_gpt`
* `cd_dispatch`
* `cd_dispatch3d`
* `qs-dispatch`
* `tk_dispatch`
* `rcore_dispatch`
* `lb-tablet`
* `kartik-mdt`
* `origen_police`
* `none`


---

# 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://zloma-scripts.gitbook.io/zloma-scripts/zloma_core-free/configuration.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.