> For the complete documentation index, see [llms.txt](https://docs.vikingsvalley.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vikingsvalley.app/readme/vikings-vision.md). # Vikings Vision Vikings Valley is designed to redefine the Play-to-Earn experience by combining strategic gameplay with a controlled and sustainable economic system. Our vision is to move away from short-term, unsustainable reward models and build an ecosystem where progression is driven by decision-making, resource management, and long-term strategy. In Vikings Valley, players are not rewarded for passive participation, but for how they build, manage, and evolve their Raid Parties over time. The integration of ODDIE ensures that the economic balance of the game is continuously maintained, preventing excessive inflation, controlling reward emissions, and adapting to the overall activity of the ecosystem. This allows Vikings Valley to provide a more stable and transparent environment, where both gameplay and economy evolve together. Our goal is not only to create a game, but to build a living system where players, resources, and mechanics interact in a balanced and sustainable way. --- # 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.vikingsvalley.app/readme/vikings-vision.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.