> For the complete documentation index, see [llms.txt](https://docs.metalordz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.metalordz.com/meta-lordz-whitepaper/getting-started.md).
# Getting Started
***
***
Meta Lordz offers a free-to-play gaming experience, accessible through a simple download from[ www.metalordz.com](http://www.metalordz.com/). The PC version is available today, with Mac and mobile versions set to launch in 2024!
**Upon launching the app, players will encounter three convenient options to commence their adventure:**
* **Login with Google Account**: Streamline your access by signing in with your Google account.
* **Login with Wallet:** Use your MetaMask wallet to access the game.
* **Login with Email:** Opt for the traditional method by registering with your email address.
As you start the game, head over to the Warriors tab to explore the available warriors. Own the warriors to customise them to your liking. When you're ready, just hit the "**Find Match**" button to dive into the exciting battles of Meta Lordz.
Be sure not to miss the Battle Pass, as it provides numerous quests and exclusive rewards to elevate your gaming experience!
***
---
# 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.metalordz.com/meta-lordz-whitepaper/getting-started.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.