> 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/quests/categories.md).

# Categories

Quest categories organize quests into groups in the Quest Journal UI.

## Creating a Category Entry

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

Each category entry defines:

| Field          | Description                                                                             |
| -------------- | --------------------------------------------------------------------------------------- |
| Display Name   | Category label shown in the quest journal (e.g., "Main Story", "Side Quests", "Daily"). |
| Category Color | Display color for quests in this category in the journal (default: yellow).             |
| Order          | Display order in the quest journal — lower values appear first (default: 100).          |

## How Categories Are Used

Each quest references a single category through its **Quest Category** field. In the Quest Journal UI, categories organize quests so players can quickly find what they're looking for.

Use the **Order** field to control category sorting. For example, set "Main Story" to order 1, "Side Quests" to order 10, and "Daily" to order 20 so they appear in that sequence.

The **Category Color** is used in the journal UI to visually distinguish quest types — for example, gold for main quests, silver for side quests, blue for daily quests.


---

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