> 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/problems/problem-statement/decline-in-game-launches-and-developer-interests.md).

# Decline in Game Launches and Developer Interests

In 2022, over **500+ Web3 games** were launched. By mid-2024, that number has dropped by more than **70%**. The slowdown isn’t just about market cycles, it’s about misaligned incentives.

With **user pools drying up**, **user growth stagnating**, and complex integration hurdles, developers have little motivation to launch. Even talented teams are pausing or pivoting, waiting for better infrastructure and clearer upside.

Yes, quality is improving, but **quantity is collapsing much faster** due to lack of new creating minds. **The ecosystem is slowly bleeding its builders.**

*<mark style="color:red;">**Creating a zombie ecosystem kept alive by constant injections of short-term rewards. Driven by empty numbers, not real players.**</mark>*


---

# 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/problems/problem-statement/decline-in-game-launches-and-developer-interests.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.