> For the complete documentation index, see [llms.txt](https://tera-arise.gitbook.io/tera-arise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tera-arise.gitbook.io/tera-arise/game-systems/main-story-and-questing.md).

# Main Story and Questing

The main story mostly proceeds as it did in TERA, but it ends around the beginning of the Exodor storyline, as we repurpose Exodor for [overworld events](/tera-arise/game-systems/overworld-and-events.md) and cut the vast majority of its story quests. Story quests proceed linearly rather than the original mess at level 65+ where you can get a mountain of story quests dropped on you all at once.

The vast majority of side quests in the game are cut; only those that add meaningful context to the story are kept. As a rule of thumb, when completing all quests in a province, the player should only spend half as much time on side quests as they do on story quests - ideally less.

Guardian Mission quests are repurposed for overworld events.

Repeatable side quests and faction quests are cut entirely.

Due to the tighter [power scaling during leveling](/tera-arise/game-systems/leveling-and-power-scaling.md), all level requirements for quests are removed.


---

# 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://tera-arise.gitbook.io/tera-arise/game-systems/main-story-and-questing.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.