> For the complete documentation index, see [llms.txt](https://game-changer.gitbook.io/game-changer-whitepaper-v0.1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://game-changer.gitbook.io/game-changer-whitepaper-v0.1/game-changer/why-game-changer-2.md).

# Why Game changer 2

The existing point systems in traditional games and platforms operate within closed structures, making it impossible to transfer these points to other games or platforms. This difficulty in transferring or monetizing points for other economic activities poses a challenge for users. Game changer bridges the gap between games and platforms, addressing this issue and creating a scalable ecosystem.

Game changer's initial target market is Asia, where an estimated 81% of users have experienced web3 games, accounting for approximately 800,000 users. The Asian gaming market is substantial, with a total worth of 174 trillion won. Within this market, the indie game sector stands out, with indie game developers constituting a significant 17% of the total game industry workforce, highlighting the challenges they face in user acquisition and retention.


---

# 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://game-changer.gitbook.io/game-changer-whitepaper-v0.1/game-changer/why-game-changer-2.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.