> For the complete documentation index, see [llms.txt](https://docs.visiongame.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.visiongame.io/visiongame-ecosystem/cryptoshowdown/targeting-the-right-audience.md). # Targeting the Right Audience While most web3 games aim to emulate traditional gaming experiences, they often overlook a key reality: the web3 audience is largely composed of traders, not conventional gamers. CryptoShowdown is designed with this in mind, focusing on elements that resonate specifically with the trading community. Rather than attempting to appeal to everyone, we’re creating a game that taps into the interests and daily experiences of traders, delivering an experience that feels familiar, engaging, and unique to their world. By centering CryptoShowdown around trading dynamics, industry humor, and competitive profit-making, we’re building a game that speaks directly to web3’s core audience. This focused approach ensures that CryptoShowdown offers meaningful engagement for traders, providing them with a game that reflects their interests and keeps them coming back for more. --- # 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://docs.visiongame.io/visiongame-ecosystem/cryptoshowdown/targeting-the-right-audience.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.