> For the complete documentation index, see [llms.txt](https://drfx-store.gitbook.io/drfx-store-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://drfx-store.gitbook.io/drfx-store-docs/documentation/products/qb-pawn-shop-script/troubleshooting.md). # Troubleshooting Fix common Pawn Shop dependency and inventory issues. ### The script does not start * Confirm QBCore, ox\_lib, and qb-inventory start first. * Confirm the resource folder name matches the ensure line. * Check the purchasing CFX account has access to the asset. * Read the first Pawn Shop error in the server console. ### The interaction does not appear Confirm the configured target or interaction resource is installed, running, and selected correctly in the configuration. ### Items cannot be displayed Check that the item exists in QBCore and qb-inventory, the item name is spelled correctly, and it is not included in the blocked-items configuration. ### Purchases or retrievals fail Check inventory capacity, player funds, persistent data, and the server console. Reproduce the issue with one item and one player before testing again. ### Listings do not survive a restart Confirm the full installation steps from the included README were completed and look for storage or database errors during server startup. ### Still need help? Join the DrFx Discord and include the framework version, dependency versions, relevant configuration section, reproduction steps, and console error: --- # 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://drfx-store.gitbook.io/drfx-store-docs/documentation/products/qb-pawn-shop-script/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.