> For the complete documentation index, see [llms.txt](https://visionstore.gitbook.io/visionstore-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://visionstore.gitbook.io/visionstore-docs/scripts/crafting/configuration/stash.md).

# Bench stash

Give every bench its own ox\_inventory stash that players buy and upgrade.

Every bench can buy its own ox\_inventory stash. The stash belongs to the **bench**, not to a player: it travels with the bench when it's picked up, traded and placed again. Settings are in `config/config.lua`.

```lua
Config.CraftingStash = {
    enabled = true,
    account = 'bank',  -- money account charged: 'cash' | 'bank'
    label   = nil,     -- nil = locale string 'stash.label'

    depositAnyCraft = true,

    levels = {
        [1] = { price = 10000, slots = 50,  weight = 100000 },
        [2] = { price = 15000, slots = 100, weight = 250000 },
        [3] = { price = 25000, slots = 150, weight = 500000 },
    },
}
```

| Option            | Default  | What it does                                                                                                                                                                                  |
| ----------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `enabled`         | `true`   | Turn bench stashes off with `false`.                                                                                                                                                          |
| `account`         | `'bank'` | Money account charged: `'cash'` or `'bank'`.                                                                                                                                                  |
| `label`           | `nil`    | Stash name. `nil` uses the locale text ("Bench Stash").                                                                                                                                       |
| `depositAnyCraft` | `true`   | Anyone at the bench may send a finished craft (even someone else's) into the bench stash, so a bench is never blocked by an absent crafter. Taking a craft **to a bag** is always owner-only. |
| `levels`          | 3 levels | Level 1 is the purchase, later levels are upgrades.                                                                                                                                           |

## Levels

| Level        | Price   | Slots | Max weight |
| ------------ | ------- | ----- | ---------- |
| 1 (purchase) | $10,000 | 50    | 100 kg     |
| 2            | $15,000 | 100   | 250 kg     |
| 3            | $25,000 | 150   | 500 kg     |

Weights are in grams (`100000` = 100 kg). Add more levels by continuing the list (`[4] = { ... }`).

## How players use it

At the bench, open **Table Information**:

* **Buy Stash** buys level 1. **Upgrade Stash** buys the next level.
* **Open Stash** opens it like any ox\_inventory stash.
* On a finished craft, **Send to Table Stash** puts the result straight into it. **Send All to Stash** sends every finished craft at once.


---

# 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://visionstore.gitbook.io/visionstore-docs/scripts/crafting/configuration/stash.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.