> For the complete documentation index, see [llms.txt](https://docs.sparkframework.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sparkframework.dev/documentation/user-guide/plugins/crafting/categories.md).

# Categories

Crafting categories organize recipes into groups for the crafting UI.

## Creating a Category Entry

Open the Spark Editor, go to **Crafting > Categories** and click **Create New**.

Each category entry uses the standard database entry fields:

| Field        | Description                                                                            |
| ------------ | -------------------------------------------------------------------------------------- |
| Display Name | Category label shown in the crafting UI (e.g., "Weapons", "Potions", "Armor", "Food"). |
| Description  | Optional description for the category.                                                 |
| Icon         | Sprite displayed in the category selection sidebar.                                    |

## How Categories Are Used

Each recipe references a single category through its **Recipe Category** field. In the crafting UI, categories appear as filter buttons in the sidebar. Players can click a category to show only recipes in that group, or select "All" to see every unlocked recipe.

The crafting UI automatically counts how many recipes belong to each category and displays the count alongside the category name.

## Organization Tips

Create categories that match how players think about crafting. Common category structures include organizing by item type (Weapons, Armor, Potions, Food, Materials), by profession (Blacksmithing, Alchemy, Cooking, Tailoring), or by tier (Beginner Recipes, Advanced Recipes, Master Recipes).

Every recipe should have a category assigned. Recipes without a category will still appear in the "All" view but will not show under any specific category filter.


---

# 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://docs.sparkframework.dev/documentation/user-guide/plugins/crafting/categories.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.
