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

# Crafting

Workbenches with recipes, job or gang locks and a progress bar.

File: `editable/crafting.lua`.

Press `E` at a workbench. The recipes show on the right like a shop. Recipes you cannot make are greyed out, and the tooltip lists what is needed. Drag a recipe to your inventory, pick how many, and a progress bar runs.

The server checks everything again at the end (time, place, ingredients). The ingredients are swapped for the result in one step: if the result does not fit, nothing is taken.

## Config

| Option        | Default     | What it does                      |
| ------------- | ----------- | --------------------------------- |
| `Enabled`     | `true`      | Crafting on / off                 |
| `MaxPerCraft` | `10`        | Most crafts in one go             |
| `Anim`        | repair      | Animation during the progress bar |
| `Benches`     | 1 workbench | The benches (see below)           |

```lua
Benches = {
    {
        id = 'workbench_sandy',
        label = 'Workbench',
        coords = vector4(1707.0, 3779.7, 34.5, 210.0),
        interactionDistance = 1.5,
        groups = nil,                       -- { mechanic = 0, lostmc = 2 } = only these jobs / gangs (minimum grade)
        blip = { sprite = 566, scale = 0.7, color = 47 },
        recipes = {
            { name = 'lockpick', amount = 1, time = 4000, ingredients = { metalscrap = 4, plastic = 2 } },
            { name = 'repairkit', amount = 1, time = 8000, ingredients = { metalscrap = 12, steel = 6, rubber = 4 },
              groups = { mechanic = 0 } },
        },
    },
},
```

| Recipe field  | What it does                            |
| ------------- | --------------------------------------- |
| `name`        | Item made                               |
| `amount`      | How many one craft makes (`1`)          |
| `time`        | Milliseconds per craft (`3000`)         |
| `ingredients` | `{ item = count }` per craft            |
| `groups`      | Only these jobs or gangs see the recipe |
| `info`        | Metadata on the made item               |

{% hint style="info" %}
Every item and ingredient must exist in your item list. A recipe with an unknown item is skipped and logged in the server console.
{% endhint %}

Other scripts add benches with `RegisterCraft`. See [Server exports](/docs/striga-inventory/exports-and-events/server.md#stashes-shops-drops-and-crafting).

{% content-ref url="/pages/hI4JA5vIiObhv6thlDLn" %}
[Converting from another inventory](/docs/striga-inventory/converting-from-another-inventory.md)
{% endcontent-ref %}


---

# 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://striga.gitbook.io/docs/striga-inventory/crafting.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.