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

# Stations

Crafting stations are in `location.json`. Each station has its own workbench, parts rack and build spot, and one build can run at a time per station.

| Field                                         | What it is                                                                             |
| --------------------------------------------- | -------------------------------------------------------------------------------------- |
| `id`                                          | Unique name. Running builds are saved with it, don't rename it while a build is active |
| `bench`                                       | Workbench prop (`model`, `x`, `y`, `z`, `w`), spawned by the script                    |
| `coords`, `rotation`, `dimensions`, `heading` | Position and size of the screen drawn on the bench                                     |
| `cameraOffset`, `fov`                         | Camera while the screen is open                                                        |
| `playerPoint`                                 | Where the player stands at the bench                                                   |
| `buildPoint`, `creeperPoint`                  | Where the car body and the creeper are placed                                          |
| `partsPed`                                    | The mechanic players take parts from                                                   |
| `deliveryPoints`                              | Parking spots for the finished vehicle, the first free one is used                     |

## Adding a station

1. Copy the existing station block in `location.json`, give it a new `id` and change the points. Use your favourite coordinate tool for `x`, `y`, `z` and the heading `w`.
2. Restart the resource, stand at the new bench and run `/carcraft_editor <station id>`.
3. Move and rotate the screen and the camera live:

| Key                | Action                                                            |
| ------------------ | ----------------------------------------------------------------- |
| Arrow up / down    | Choose a value                                                    |
| Arrow left / right | Change it (hold **Shift** for big steps, **Ctrl** for fine steps) |
| E                  | Move the screen in front of you                                   |
| Enter              | Copy the values to the clipboard                                  |
| Backspace          | Exit                                                              |

4. Paste the copied values into the station in `location.json` and run `/carcraft_reload`.

{% hint style="warning" %}
`/carcraft_reload` refuses to move a station while a build is running on it. Cancel the build first with `/carcraft_cancel <station id> refund`.
{% endhint %}


---

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