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

# Configuration

Configure interactions, blocked items, language, and logging.

Back up the original configuration file before making changes. Edit only the files supplied as configurable.

### Interaction method

Choose the supported target or interaction option used by your server. Confirm the selected resource starts before the Pawn Shop script.

### Blocked items

Use the configuration to prevent selected inventory items from being displayed or sold. Enter item names exactly as they appear in QBCore and qb-inventory.

### Language

Edit the supplied language file to change player-facing text. Keep keys and formatting intact while translating values.

### Logging

Configure the supported logging option if you want records of pawn shop actions. Never place private webhook values in files that are shared publicly.

### Testing changes

Restart the Pawn Shop resource after configuration changes, then test with a non-production character before opening the shop to players.


---

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