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

# Configuration

Everything is in `config.lua`, grouped by feature and commented. The file stays editable in both editions — the escrow edition never encrypts it.

Most servers only need to change three things: `Config.Locale`, `Config.Locations` and `Config.BlacklistedItems`. Everything else has working defaults.

{% hint style="info" %}
The config is validated on every start. Blocking mistakes are printed as `CONFIG ERROR`, things worth checking as `Config warning`. Read the console after your first start.
{% endhint %}

## Map of the file

| Block                                                                                                                | Page                                                                                         |
| -------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
| `Config.Debug`, `Locale`, `Framework`, `TargetSystem`, `CustomTarget`, `Inventory`, `Notify`, `UI`                   | [General](/daddy-studios-docs/scripts/daddy-marketplace/configuration/general.md)            |
| `Config.Locations`, `Config.Marker`                                                                                  | [Locations](/daddy-studios-docs/scripts/daddy-marketplace/configuration/locations.md)        |
| `Config.Categories`, `ItemCategories`, `BlacklistedItems`, `BlockWeapons`, `ItemPaymentOverrides`, `ItemPriceLimits` | [Items & Categories](/daddy-studios-docs/scripts/daddy-marketplace/configuration/items.md)   |
| `Config.Marketplace` (listings, tax, listing fee), `Config.OnFeeCollected`                                           | [Fees & Taxes](/daddy-studios-docs/scripts/daddy-marketplace/configuration/fees.md)          |
| `Config.Auction`                                                                                                     | [Auctions](/daddy-studios-docs/scripts/daddy-marketplace/configuration/auctions.md)          |
| `Config.Offers`, `Config.BuyOrders`                                                                                  | [Offers & Buy Orders](/daddy-studios-docs/scripts/daddy-marketplace/configuration/offers.md) |
| `Config.Featured`                                                                                                    | [Featured Listings](/daddy-studios-docs/scripts/daddy-marketplace/configuration/featured.md) |
| `Config.Security`, `Config.HistoryRetentionDays`                                                                     | [Security](/daddy-studios-docs/scripts/daddy-marketplace/configuration/security.md)          |
| `Config.Locale`, `locales/`                                                                                          | [Languages](/daddy-studios-docs/scripts/daddy-marketplace/configuration/languages.md)        |
| `Config.Webhooks`                                                                                                    | [Discord Webhooks](/daddy-studios-docs/scripts/daddy-marketplace/configuration/webhooks.md)  |

## Applying changes

`config.lua` is a shared script, so a change needs a resource restart:

```
restart daddy-marketplace
```

Active listings, auctions, buy orders and pending deliveries survive a restart — they live in the database, not in memory. Expiry and settlement jobs pick up where they left off.

{% hint style="warning" %}
Changing a key in `Config.Locations` renames the market. Listings created under the old key stay in the database and still expire back to their owners, but they are no longer visible at any market. Pick your location keys before players start using them.
{% endhint %}


---

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