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

# General

The top of `config.lua`: detection, interaction, inventory images, notifications and the optional chat command.

## Basics

```lua
Config.Debug        = false
Config.Locale       = 'en'
Config.Framework    = 'auto'
Config.TargetSystem = 'auto'
```

| Option         | Values                                                       | Meaning                                                                                                                   |
| -------------- | ------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------- |
| `Debug`        | `true` / `false`                                             | Extra console output while troubleshooting. Leave off on a live server.                                                   |
| `Locale`       | `'en'`, `'tr'`, `'de'`, `'es'`, `'fr'`                       | Language file from `locales/`. See [Languages](/daddy-studios-docs/scripts/daddy-marketplace/configuration/languages.md). |
| `Framework`    | `'auto'`, `'qbx'`, `'qb'`, `'esx'`                           | `auto` detects `qbx_core`, `qb-core` or `es_extended`. Force a value only if detection picks the wrong one.               |
| `TargetSystem` | `'auto'`, `'ox_target'`, `'qb-target'`, `'custom'`, `'none'` | `auto` uses ox\_target or qb-target when one is running. `none` always uses a marker + **E**.                             |

## Custom interaction

Set `Config.TargetSystem = 'custom'` and fill in `Config.CustomTarget` to use any other interaction resource. It runs on the client, once per spawned NPC:

```lua
Config.CustomTarget = function(ped, locationId, location, open)
    exports.your_interact:AddLocalEntityInteraction({
        entity   = ped,
        label    = 'Open Marketplace',
        onSelect = open,
    })
end
```

Call `open()` with no arguments when the player interacts. Details and parameters are on the [Config Hooks](/daddy-studios-docs/scripts/daddy-marketplace/hooks.md) page.

## Inventory

```lua
Config.Inventory = {
    system = 'auto',              -- 'auto', 'ox', 'qb', 'ps', 'lj', 'qs', 'codem'
    imageExtension = '.png',
    imagePaths = {
        ['ox']      = 'nui://ox_inventory/web/images/',
        ['qb']      = 'nui://qb-inventory/html/images/',
        ['ps']      = 'nui://ps-inventory/html/images/',
        ['lj']      = 'nui://lj-inventory/html/images/',
        ['qs']      = 'nui://qs-inventory/html/images/',
        ['codem']   = 'nui://codem-inventory/html/images/',
        ['default'] = 'nui://qb-inventory/html/images/',
    },
}
```

`system = 'auto'` detects the running inventory. The paths only affect **item images in the UI** — if icons are missing, correct the path for your inventory here. Item handling itself goes through `modules/inventory/bridge.lua`, which stays editable in both editions.

{% hint style="info" %}
On QBX, `ox_inventory` is required. Item metadata (durability, serial numbers) is preserved on every inventory that supports it.
{% endhint %}

## Notifications

```lua
Config.Notify = {
    type     = 'auto',          -- 'auto', 'ox_lib', 'qb', 'esx', 'custom'
    title    = 'Marketplace',
    position = 'top-right',     -- ox_lib only
    duration = 5000,            -- milliseconds

    custom = function(source, message, notifyType, duration)
        -- TriggerClientEvent('your_notify:show', source, message, notifyType, duration)
    end,
}
```

`auto` uses `ox_lib` when it is running, otherwise the framework's own notification. Set `type = 'custom'` to route **every** message through `Config.Notify.custom`, which runs on the server. `notifyType` is one of `success`, `error`, `info`, `warning`.

## Chat command

```lua
Config.UI = {
    enableCommand = false,
    openCommand   = 'marketplace',
}
```

Off by default. When enabled, `/marketplace` opens the nearest location, but only within `Config.Security.maxDistance`. See [Commands & Permissions](/daddy-studios-docs/scripts/daddy-marketplace/commands-and-permissions.md).

## Next steps

* [Locations](/daddy-studios-docs/scripts/daddy-marketplace/configuration/locations.md)
* [Items & Categories](/daddy-studios-docs/scripts/daddy-marketplace/configuration/items.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-marketplace/configuration/general.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.