# Creating A quest

This is a TODO page

### The tree

A quest has a tree of objectives so called actions. the actions can be a lot and offer all the interactivity the plugin has to offer. for a list of actions possible visit the Actions page.

{% content-ref url="/pages/-MfwTLrDP\_UqSvpur6L8" %}
[Actions](/mcg-ultimate-quester/creating-a-quest/actions.md)
{% endcontent-ref %}

### The start Type

The start type is the TYPE setting in the quest file. it can be either sign. or NPC.\
Keep in mind the command overrules this section completely.\
if its set to NPC enter the NPCID in its npcid setting so the plugin knows which npc should trigger this one.\
the sign is setup like so:\
\[Quester]\
Questfilename

### Requirements

Every quest has requirements that needs to be meeted before the quest is triggered.\
this prevents doing a quest multiple times or makes the flow go like you want it to.

{% content-ref url="/pages/-MfwdQ1Cjw7cHqTLf3Nm" %}
[Requirements](/mcg-ultimate-quester/creating-a-quest/requirements.md)
{% endcontent-ref %}

### Finishactions

The end of a objective has a finish action as always it should be one of the following:

**GOTO**\
**EXIT**\
**FINISH**\
the **GOTO** must be put like so: **GOTO#objectivename** This starts an other objective in this quest.\
the **EXIT** must be put like so: **EXIT#Quest** this exits the current quest completely canceling out any progress.\
The **Finish** must be put like so: **FINISH#TAG** this exits and finishes the quest and gives the user TAG tag to his file. this tag can be used in requirements beside that the quest is marked as completed for the user also usable in the requirements


---

# Agent Instructions: 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:

```
GET https://docs.mcgsoft.eu/mcg-ultimate-quester/creating-a-quest.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.