> 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/troubleshooting.md). # Troubleshooting ## Start-up | Message | Meaning | | --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | | `Database ready.` | Normal. Tables exist and migrations ran. | | `CONFIG ERROR ...` | A blocking mistake in `config.lua` — an unknown category, an invalid payment method, a bad duration. Fix it and restart. | | `Config warning ...` | Worth checking but not blocking, for example a location still sitting at 0, 0, 0. | | `No framework detected` | The framework started **after** the marketplace, or none of `qbx_core`, `qb-core`, `es_extended` is running. Fix your `ensure` order. | | `Locale "xx" not found, falling back to "en"` | `Config.Locale` does not match a file in `locales/`. | ## Common problems | Problem | Fix | | -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Nothing happens at the NPC | Check `Config.TargetSystem`. With no target resource, a marker + **E** is used — walk closer than `Config.Marker.interactDistance`. | | No NPC at all | `usePed = false` on that location, or the coords are wrong. Check the blip on the map. | | Item images are missing | Set the path for your inventory in `Config.Inventory.imagePaths`. | | "You are too far away" | Stand within `Config.Security.maxDistance` of the market you opened. | | Text shows raw keys like `notify.xxx` | A key is missing from a custom locale file. Copy it from `locales/en.lua`. | | A message shows `%s` or `%d` literally | A placeholder was removed or its type changed in a locale file. See [Languages](/daddy-studios-docs/scripts/daddy-marketplace/configuration/languages.md). | | An item cannot be listed | It is in `Config.BlacklistedItems`, it is a weapon while `Config.BlockWeapons` is on, its price is outside `Config.ItemPriceLimits`, or the location's `categories` / `allowedItems` exclude it. | | Players are blocked during normal use | Raise `Config.Security.maxRateLimitViolations` before touching `rateLimitMs`. | | The UI opens but stays empty | The framework or inventory bridge could not identify the player. Check the server console for errors on open, and confirm the start order. | ## "My item is gone" It is almost always in the delivery depot: anything that cannot be handed over at that moment — full inventory, player offline — is stored instead of being dropped. ``` /marketplaceadmin deliveries ``` The player claims it with the **Claim Stored Items** button on the dashboard the next time they open the marketplace. Undelivered depot rows are never removed by the retention cleanup. ## A stuck listing or auction ``` /marketplaceadmin listing /marketplaceadmin auction /marketplaceadmin buyorder ``` Each of these cancels the record and returns everything: items to the seller, held bids to the bidder, open offers and remaining escrow to the buyers. The commands also work from the server console, which is the way to fix something while nobody is online. ## After a restart Listings, auctions, buy orders, offers and pending deliveries all live in the database, so a `restart daddy-marketplace` or a full server restart loses nothing. Expiry and settlement jobs resume on the next interval (`checkIntervalSeconds` per feature), so an auction whose deadline passed while the server was down is settled shortly after it comes back up. ## Debug output ```lua Config.Debug = true ``` Adds console output for framework and inventory detection and for the action flow. Turn it off again on a live server — it is noisy. ## Reporting a problem Include: * the framework and inventory you run, with versions * the server console output from start-up (the `Database ready.` block and anything red) * the client console (F8) if the UI is involved * whether the problem also happens on an unmodified copy of the resource ## Next steps * [Commands & Permissions](/daddy-studios-docs/scripts/daddy-marketplace/commands-and-permissions.md) * [Database](/daddy-studios-docs/scripts/daddy-marketplace/database.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/troubleshooting.md?ask=&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.