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

# Quest Creation

Quests should offer the player as many choices as possible. Prefer quests that can be solved in more than one way. Examples of solutions to quests:

* The player gains gold at the expense of the well-being of NPCs.
* The player gains stats, but some NPC dies.
* The player helps an NPC by sacrificing a piece of equipment.
* The player gains trust from some NPCs, but has to travel to many places and put in a lot of effort to earn it.
* The player chooses to side with the main monster boss and gains equipment, but also distrust from other NPCs.
* The player chooses a conversation option stating that they have no intention of performing the quest.

### **Level Recommendations**

* **Early Game** (Levels 1-15): Crossglen and Fallhaven area quests.
* **Mid Game** (Levels 16-35): Vilegard, Remgard, and mountain conflicts.
* **Late Game** (Levels 36-50+): Lodar questlines.
* **Endgame** (Level 50+): Hira'zinn confrontation and endgame content.


---

# 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://andorstrail.gitbook.io/docs/contributor-section/quests.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.