> For the complete documentation index, see [llms.txt](https://mixmob.gitbook.io/mixmob-player-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mixmob.gitbook.io/mixmob-player-guide/new-player-guide/quickstart.md).
# 1. Create Your Identity
#### **Welcome to Racer 1**
The **first-ever card battle racer**—where high-speed action meets tactical gameplay. Take control of your MixBot, master your deck, and outsmart your opponents on the track.
This guide will help you get started, from setting up your username to building your deck and joining the community.
***
**Step 1: Create Your Identity**
Your journey begins with your **username**—your identity in Racer 1.
🔹 **Enter Your Username** – When prompted on the welcome screen, type your name or hit the refresh button for a randomly generated one.
🔹 **Make It Yours** – Your username is how other players will recognize you. Pick something personal and representative of your style. No pressure—you can always change it later.
💡 **Need help?** Check out the GIF below to see how to select or generate your name.
***
**Step 2: Navigate the Game**
Now that your identity is set, let's explore the key action screens that will guide you through Racer 1.
Ready to race? Let’s dive in. 🚀
---
# 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://mixmob.gitbook.io/mixmob-player-guide/new-player-guide/quickstart.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.