> 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.md).

# Quests

The Quests plugin adds a full quest system to your game. Define quests with objectives, acceptance requirements, and rewards (both guaranteed and player-selectable). Quests progress through states from acceptance to turn-in, integrate with NPCs for giving and turning in quests, and persist automatically through the save system. Other plugins extend the quest system with their own objective and reward types.

In the Spark Editor, the Quests plugin is organized into these categories:

| Category                                                             | What it contains                                                                                                                                                  |
| -------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Quests](/documentation/user-guide/plugins/quests/quests.md)         | Quest entries with objectives, requirements, and rewards; quest states; quest triggers and requirements; NPC quest integration with state indicators; persistence |
| [Categories](/documentation/user-guide/plugins/quests/categories.md) | Category entries for organizing quests in the Quest Journal with colors and display order                                                                         |


---

# 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/quests.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.