> For the complete documentation index, see [llms.txt](https://voyage-trilogy.gitbook.io/tvt/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://voyage-trilogy.gitbook.io/tvt/welcome.md).
# Welcome
{% hint style="info" %}
The Voyage Trilogy is the result of genuine passion, deep expertise, and a true love for technology.
{% endhint %}
### **About Our Documentation**
As the lines between the virtual and the real continue to blur, *The Voyage Trilogy* is shaped as a project that expands what a game can be. This is a living digital world where every action has meaning, every decision changes the path ahead, and every player takes part in an evolving story.
The early chapters focus entirely on story, atmosphere and survival. Core infrastructure for persistence and player identity is embedded from the start. It functions invisibly, requiring no action or awareness from the player.
From the frozen landscapes of Northern Norway, *The Voyage Trilogy* unfolds through richly detailed survival gameplay, dynamic faction systems and a branching narrative shaped by player choices. Powered by Unreal Engine 5.6 and advanced AI, the game creates a persistent world where decisions carry forward and stories evolve over time.
Each player account stores character progress, collected items, relationships and completed missions. It is designed to preserve everything the player builds, and to remain ready for new layers of interaction and meaning as the world grows.
---
# 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://voyage-trilogy.gitbook.io/tvt/welcome.md?ask=&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.
