> For the complete documentation index, see [llms.txt](https://unfetteredecosystem.gitbook.io/linea-guild-games-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://unfetteredecosystem.gitbook.io/linea-guild-games-guide/linea-guild-games/linea-guild-games-overview.md). # Linea Guild Games Overview The **Linea Guild Games (LGG)** is an exciting 9-day Web3 gaming event starting on **September 18, 2024**, designed to bring together the Linea community through gaming and competition. {% embed url="" %} LGG Teaser from LineaBuild {% endembed %} Players can join one of four guilds, mint a companion for their Game7 avatar, and compete in the Unfettered Awakening game. The event features both individual and guild-based competitions with great rewards. **Key Event Details:** * **Start Date**: September 18, 2024 * **Duration**: 9 days * **Game**: Unfettered Awakening * **Prize Pool**: over $120,000, with $100,000 in ETH from Linea and +$20,000 from LGG’s partners The event is designed to be fun and accessible for all players. No prior experience in Web3 is needed, and entry is free, but players who buy tickets unlock additional advantages, increasing their chances of winning. --- # 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://unfetteredecosystem.gitbook.io/linea-guild-games-guide/linea-guild-games/linea-guild-games-overview.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.