> For the complete documentation index, see [llms.txt](https://bso-wiki.oldschool.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bso-wiki.oldschool.gg/minigames/tinkering-workshop.md).

# Tinkering Workshop

You can start this miningame with the command `/bsominigames tinkering_workshop start`.

Tinkering Workshop is an invention minigame, where you can tinker with materials. You get XP and the invention skilling outfit and materials bag.

The full outfit gives 4% bonus invention XP.

All materials have the same reward drop rate, however the Junk material will halve the XP you receive. All other materials provide the same amount of XP.

### Rewards

* Inventors' helmet
* Inventors' torso
* Inventors' legs
* Inventors' gloves
* Inventors' boots
* Inventors' backpack
* Materials Bag - +7 minutes to Invention max trip length


---

# 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://bso-wiki.oldschool.gg/minigames/tinkering-workshop.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.
