> For the complete documentation index, see [llms.txt](https://kazarhq.gitbook.io/kazarhq-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kazarhq.gitbook.io/kazarhq-docs/use-cases/unified-player-onboarding.md).

# Unified Player Onboarding

Most Web3 games still expect players to install wallets, understand chain switching, sign transactions, and manage tokens—**just to press play.** It’s a broken loop that keeps 90% of real gamers out.

Kazar fixes this with **frictionless onboarding built into the core**:

* 🧾 **Login with email, social, or wallet**\
  Players can jump in without needing a wallet at all—progress and rewards are synced invisibly.
* 🔄 **Unified identity across all games**\
  One profile, one wallet, one inventory—usable across every Kazar-powered title.
* ⚙️ **Abstracted transactions & gas**\
  No more scary MetaMask popups. Players transact with a simple click. Gas fees? Covered or abstracted in most flows.
* 📱 **Mobile-first UX**\
  Fully optimized for mobile WebGL and native experiences—because real gamers don’t live in Chrome wallets.

Kazar removes every hurdle between **"I found this game"** and **"I’m having fun"**.


---

# 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://kazarhq.gitbook.io/kazarhq-docs/use-cases/unified-player-onboarding.md?ask=<question>&goal=<endgoal>
```

`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.