> For the complete documentation index, see [llms.txt](https://tidal-flats.gitbook.io/tidal-flats-whitepaper-en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tidal-flats.gitbook.io/tidal-flats-whitepaper-en/whitepaper/eol-mega-road/base-information.md). # Base Information **Roguelike** * The player's character starts at level 1 in every battle, regardless of the outcome of the previous game. The types and order of skills will also change, requiring players to think of new combinations and strategies each time. **Survival** * Defend your character against various types of mutants, monsters, mechs, and harriers, and defeat powerful bosses to earn a variety of rewards for upgrading your character. **Equipment** * Enhance and merge equipable items from all six sections to create more powerful gear to survive against fearsome enemies. **Skill** * To combat the numerous enemies, players will need to choose their skills carefully, as there are active skills that deal direct damage, as well as passive skills that support the player's character's abilities, and the two can be combined to create even more powerful skills. --- # 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://tidal-flats.gitbook.io/tidal-flats-whitepaper-en/whitepaper/eol-mega-road/base-information.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.