> For the complete documentation index, see [llms.txt](https://emberlore.gitbook.io/emberlore-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://emberlore.gitbook.io/emberlore-whitepaper/introduction-to-emberlore.md). # Introduction to EmberLore Welcome to the world of **EmberLore**, a groundbreaking massive open world multiplayer game designed for both mobile and PC platforms. EmberLore offers an unparalleled gaming experience that seamlessly integrates the mobility of handheld devices with the power and precision of desktop gaming. EmberLore transports players into a richly detailed fantasy universe, where magic and mystery rule. Players can explore vast landscapes, from enchanted forests and treacherous mountains to bustling cities and hidden dungeons. Each corner of the world is meticulously crafted to provide a sense of wonder and discovery, inviting players to embark on epic quests, forge alliances, and engage in strategic battles. What sets EmberLore apart is its commitment to accessibility and inclusivity. Whether you're playing on a high-end gaming rig or a mobile device, EmberLore offers a consistent and optimized experience. This cross-device compatibility ensures that players can dive into the world of EmberLore anytime, anywhere. {% embed url="" %} --- # 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://emberlore.gitbook.io/emberlore-whitepaper/introduction-to-emberlore.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.