> For the complete documentation index, see [llms.txt](https://docs.asphodel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.asphodel.io/whitepaper/close/what-comes-next.md).
# What Comes Next
This whitepaper is being published (12th June 2026) shortly before the release of the Asphodel Prologue, our first World on mainnet. More details on Prologue's gameplay and specific economics will be added to this Gitbook as a new section before the launch.
We have not included a roadmap with this whitepaper because we believe development roadmaps for a crypto project are usually either dishonest or a waste of time. In practice, our focus for the next year is on releasing and upgrading the Prologue while we continue to expand Kamigotchi World in parallel. We work hard and ship regularly, and have done so for several years now; we will continue to do so.
You can expect to see a 'Dungeon Mode' added to Prologue after release, as well as new systems in Kamigotchi to extend the game's lifespan. You can also expect to see the Kamigotchi in Asphodel, and perhaps the Taruchi in Kamigotchi. You will also see in-game factions and the development of organized faction PVP that stretches across both games. You will see player guilds. With that said, we don't know in what order these features will be added - we don't plan development more than 2-3 months ahead of time.
We also think it's more fun for you this way.
Our ultimate goal is to release the main Asphodel world as the first true example of a fully decentralized MMORPG. We have now been dedicated to this goal for the last 4 years; it will probably take at least 4 more.
Thank you for reading. Near-daily updates on this project are posted at .
From the original Asphodel playtest in 2023... We'll be back one day...
---
# 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.asphodel.io/whitepaper/close/what-comes-next.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.