> For the complete documentation index, see [llms.txt](https://avania.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://avania.gitbook.io/whitepaper/problem-and-solution/meta.md). # META ### Problem "Meta" in gaming terminology is a generally agreed-upon strategy by the community. Said strategy is considered to be the most optimal way to win/ have the best performance at a specific task. Some people have defined meta as an acronym meaning “most effective tactics available”. That made most of the players play “Meta” in order to take the best chance to “WIN” Let's imagine, you are doing the same work every day, seeing the same person every week. Then you come home and play the game that you and your opponent play the same way in every match. It is boring, isn't it? Therefore, “Meta” can make players get bored with the game and quit the game quite fast because they always have to play the same way with their opponents, again and again… and not only blockchain games, but most of the games have “Meta” in their game. ### Solution In Avania, nexus is certainly unique. Each nexus contain 5 different Guardian that cannot be altered or duplicated. In the very first generation, We can create more than 7 million unique nexus by combining 5 guardians out of 64 first-generation guardians. By doing it, players will not be able to duplicate other players playing styles. Moreover, each player will have to find the best way to play with each nexus because it is one of a kind. Therefore, there is an extremely higher chance that players will encounter different playstyles in each match. --- # 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://avania.gitbook.io/whitepaper/problem-and-solution/meta.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.