# The Problem with Web3 Gaming

It's no secret that lack of education is one of the biggest challenges in this space. More so, the lack of targeted education & opportunities for each individual.

Web3 gaming is still in its infancy. While the overall traditional gaming space boasts over 3 billion gamers worldwide, the industry currently barely has 2M+ gamers in web3 identified through connected wallets, which can often be inflated due to multiple wallets per user.

GAM3S.GG aims to break down the barriers that separate web2 gamers from the limitless possibilities of blockchain-powered games and *speak the language* of gamers to foster genuine interest and an appetite to explore the web3 gaming space.

However, this is no easy task. Today, 4 main stakeholders are facing distinct individual problems: 

{% hint style="danger" %}
**Gamers**

*Struggle to find fun games with easy onboarding.*
{% endhint %}

{% hint style="danger" %}
**Games**

*Struggle with launching & acquiring players given overall industry sentiment & lack of users.*
{% endhint %}

{% hint style="danger" %}
**Content Creators**

*Forced to amplify paying customers to survive, regardless of quality.*
{% endhint %}

{% hint style="danger" %}
**Investors**

*Get overwhelmed with hype, daily launches & often FOMO into poor decisions.*
{% endhint %}

There is a clear gap between games and gamers exploring this space, particularly as traditional gaming media, launchers, and creators remain skeptical of the overall blockchain gaming niche. This represents a great opportunity for GAM3S.GG to dominate and fill that gap, acquiring invaluable marketshare.


---

# Agent Instructions: 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:

```
GET https://greenpaper.games.gg/introduction/the-problem-with-web3-gaming.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.