> For the complete documentation index, see [llms.txt](https://docs.vampirewars.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vampirewars.io/the-story/the-thriving.md).
# The Thriving
For hundreds of thousands of years, the vampire species evolved serving the purpose of the Runes.
Vampires are the craftsmen of the world as we know it. They were the Khans, the Emperors, The Wizards and Witches, the Kings and Queens, the Gods, the important historical figures that contributed to our elevation as a species.
Hidden from human sight, infiltrated in the society, they were the architects of the great wars and expansions, the builders and the destroyers of empires. Heroes, Leaders, Dragons, Daemons & Angels, were all **Pure Blooded Vampires.**
All documented important historical events are linked to them, until 1910, when humans learned about their existence and discovered the Runes by accident during an earthquake in Japan. They tampered with the mystical stones and a chain of events led to the extinction of the vampires. They lost their cellular regeneration enhancement, became mortals, aged and went extinct.
---
# 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://docs.vampirewars.io/the-story/the-thriving.md?ask=&goal=
```
`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.