> 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/installation.md).

# Installation

## Requirements

| Resource                  | Required | Notes                                                                                                                                                          |
| ------------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `oxmysql`                 | Yes      | Database access. Tables are created automatically.                                                                                                             |
| Framework                 | Yes      | `qbx_core`, `qb-core` or `es_extended` — auto-detected                                                                                                         |
| Inventory                 | Yes      | `ox_inventory` (recommended, required on QBX), `qb-inventory`, `ps-inventory`, `lj-inventory`, `qs-inventory`, `codem-inventory`, or the default ESX inventory |
| `ox_lib`                  | No       | Used for notifications when it is running                                                                                                                      |
| `ox_target` / `qb-target` | No       | NPC interaction. Without one, a marker + **E** is used automatically                                                                                           |

Database: MariaDB 10.3+ or MySQL 5.7+/8.

## Steps

### 1. Download and extract

Download the resource from your [Cfx Portal](https://portal.cfx.re/assets/granted-assets) (escrow edition) or from the store (open-source edition) and extract the archive.

### 2. Add the folder

Place the `daddy-marketplace` folder in your server's `resources` directory.

{% hint style="warning" %}
Do not rename the folder. Other resources call the marketplace with `exports['daddy-marketplace']`, and the UI is served from this resource name.
{% endhint %}

### 3. Start order

The marketplace must start **after** oxmysql, your framework and your inventory:

```cfg
ensure oxmysql
ensure qbx_core        # or qb-core / es_extended
ensure ox_inventory    # your inventory
ensure ox_target       # optional
ensure daddy-marketplace
```

### 4. Configure the minimum

Open `config.lua` and set at least:

* `Config.Locale` — `'en'`, `'tr'`, `'de'`, `'es'` or `'fr'`
* `Config.Locations` — where your marketplace NPCs stand. The shipped entry is a placeholder at Legion Square.
* `Config.BlacklistedItems` — items that must never be traded on your server

### 5. Start the server

The database tables are created on the first start. You should see:

```
[Daddy Marketplace] Database ready.
```

The config is validated on every start. Mistakes are printed as `CONFIG ERROR` (blocking problems, such as an unknown category or an invalid payment method) and `Config warning` (things worth checking, such as a location still sitting at 0, 0, 0).

{% hint style="success" %}
No SQL import and no source editing is needed.
{% endhint %}

### 6. Admin permission

Give your admins the moderation command in `server.cfg`:

```cfg
add_ace group.admin command.marketplaceadmin allow
```

See [Commands & Permissions](/daddy-studios-docs/scripts/daddy-marketplace/commands-and-permissions.md).

## Updating

1. Back up `config.lua` and any locale file you changed. In the open-source edition also back up your changes to `modules/framework/*.lua` and `modules/inventory/bridge.lua`.
2. Replace the folder with the new version.
3. Re-apply your changes, comparing against the new files and the [Changelog](/daddy-studios-docs/scripts/daddy-marketplace/changelog.md).

Database tables are migrated automatically on start; existing listings, auctions, orders and pending deliveries are preserved.

## Next steps

* [Configuration](/daddy-studios-docs/scripts/daddy-marketplace/configuration.md)
* [Locations](/daddy-studios-docs/scripts/daddy-marketplace/configuration/locations.md) — where your markets stand
* [Items & Categories](/daddy-studios-docs/scripts/daddy-marketplace/configuration/items.md) — what may be traded


---

# 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/installation.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.