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

# Getting started

Work Orders is **server-side only** — drop the jar in, and there's nothing for your players to install.

## Install

1. Download the latest `WorkOrders.jar`.
2. Drop it into your server's `plugins/` folder.
3. Restart the server. A `config.yml` is generated on first run — everything works out of the box, no setup required.

## The whole loop, in three steps

1. **Craft** the Work Order for the job you want (see [recipes](#recipes) below).
2. **Right-click** a copper golem while holding it — the golem takes the job.
3. **Tap a container** to set the pickup, then **tap another** for the drop-off. It gets to work.

That's it. The golem walks the route, carries one stack at a time, and keeps at it as long as a player is nearby.

{% hint style="success" %}
Every transfer is a real item move — **never duplicated, never voided**. If the destination is full, the golem simply holds the cargo until there's room.
{% endhint %}

## Recipes

Every Work Order shares the same frame — **copper ingots around a sheet of paper** — with the **job's tool** in the bottom-center slot. Craft the one you want, then hand it to a golem.

**Courier** — the template: a copper-ingot frame, paper in the centre, the hopper below.

|                                                                                                                  |                                                                                                                  |                                                                                                                  |
| :--------------------------------------------------------------------------------------------------------------: | :--------------------------------------------------------------------------------------------------------------: | :--------------------------------------------------------------------------------------------------------------: |
| <img src="https://mc.nerothe.com/img/1.21.4/minecraft_copper_ingot.png" alt="Copper Ingot" data-size="original"> | <img src="https://mc.nerothe.com/img/1.21.4/minecraft_copper_ingot.png" alt="Copper Ingot" data-size="original"> | <img src="https://mc.nerothe.com/img/1.21.4/minecraft_copper_ingot.png" alt="Copper Ingot" data-size="original"> |
| <img src="https://mc.nerothe.com/img/1.21.4/minecraft_copper_ingot.png" alt="Copper Ingot" data-size="original"> |        <img src="https://mc.nerothe.com/img/1.21.4/minecraft_paper.png" alt="Paper" data-size="original">        | <img src="https://mc.nerothe.com/img/1.21.4/minecraft_copper_ingot.png" alt="Copper Ingot" data-size="original"> |
| <img src="https://mc.nerothe.com/img/1.21.4/minecraft_copper_ingot.png" alt="Copper Ingot" data-size="original"> |       <img src="https://mc.nerothe.com/img/1.21.4/minecraft_hopper.png" alt="Hopper" data-size="original">       | <img src="https://mc.nerothe.com/img/1.21.4/minecraft_copper_ingot.png" alt="Copper Ingot" data-size="original"> |

→ **Work Order: Courier**

For the other five jobs, keep the copper-and-paper frame and just **swap the bottom-center tool**:

| Job           | Tool                                                                                                                                  |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| **Courier**   | <p><img src="https://mc.nerothe.com/img/1.21.4/minecraft_hopper.png" alt="Hopper" data-size="original"></p><p> Hopper</p>             |
| **Stoker**    | <p><img src="https://mc.nerothe.com/img/1.21.4/minecraft_furnace.png" alt="Furnace" data-size="original"></p><p> Furnace</p>          |
| **Restocker** | <p><img src="https://mc.nerothe.com/img/1.21.4/minecraft_barrel.png" alt="Barrel" data-size="original"></p><p> Barrel</p>             |
| **Janitor**   | <p><img src="https://mc.nerothe.com/img/1.21.4/minecraft_brush.png" alt="Brush" data-size="original"></p><p> Brush</p>                |
| **Sorter**    | <p><img src="https://mc.nerothe.com/img/1.21.4/minecraft_comparator.png" alt="Comparator" data-size="original"></p><p> Comparator</p> |
| **Farmhand**  | <p><img src="https://mc.nerothe.com/img/1.21.4/minecraft_iron_hoe.png" alt="Iron Hoe" data-size="original"></p><p> Iron Hoe</p>       |

{% hint style="info" %}
Recipes are fully configurable — server owners can change the shape, ingredients, and cost in [`config.yml`](/machina-docs/workorders/configuration.md).
{% endhint %}

Next: meet [**the jobs**](/machina-docs/workorders/jobs.md) →

***

*Work Orders is built by* [***Machina***](https://wearemachina.com) *— custom Minecraft plugins and more at* [*wearemachina.com*](https://wearemachina.com)*.*


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://machina-1.gitbook.io/machina-docs/workorders/getting-started.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.