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

# Changelog

## 1.0.0 — first public release

### Marketplace

* Fixed-price listings with a shopping cart, partial purchases and per-item payment restrictions
* Offers with escrow and counter-offers
* Auctions with buyout, anti-snipe and optional bid money hold (on by default)
* Buy orders with escrow, partial fulfillment and a claim depot
* Featured listings and auctions
* Seller ratings, seller profiles, price history, watchlist with price-drop alerts
* Dashboard with market pulse, sales chart, top items, ending-soon auctions, your open buy orders and a one-click claim for stored items
* Discord logs for listings, purchases, bids, auction results and offers
* English, Turkish, German, Spanish and French

### Setup

* Works with QBX, QBCore and ESX, and with ox, qb, ps, lj, qs and codem inventories
* Database tables are created automatically (MariaDB and MySQL 8)
* NPC interaction through ox\_target / qb-target, or a marker + **E** automatically
* Multiple market locations with job, category and item restrictions
* Admin moderation command, client/server exports, fee hook for society accounts, automatic cleanup of old records
* Config check on start with clear error messages
* Optional listing fee, per-item price limits, weapon blocking
* Custom interaction hook (any target/interact resource)
* Queued Discord logs including buy orders, cancellations, featured purchases and admin actions

### Safety

* All money and item transfers are validated and claimed atomically on the server
* Item metadata (durability, serial numbers) is preserved through every trade
* Items that can't be delivered are stored and handed over later, never lost
* Actions require the player to be at the market they opened
* Players never receive other players' real identifiers
* Offline players get their notifications the next time they open the marketplace


---

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