# Community We learn from previous and current successful games that inspire us regarding target audiences, idle games, idle token income, etc. We understand the importance of what crypto games, which present NFTs, should provide: * Actual ownership * Play-to-Earn real value * Implementing the marketplace for NFTs ZipClash is a global game that can be played on any platform, with favor to mobile devices – the game is for everyone. However, the game is expected at least to bring fun to most fans of the Idle Games, Food Theme, and simulation genre, specifically young players from 15 to under 35 with a mobile device that could connect to the internet. No prior knowledge about cryptocurrencies is needed. The value and uniqueness of the ZipClash are protected. Before applying to the game, every change or new design would be discussed with the community. We will meet you on Discord, Twitter, Telegram, and Reddit in the first stage, but we will soon be actively available on all social networks. In addition, we will bring together fans and players of ZipClash from all over the world by holding face-to-face events and competitions to build a large, dynamic, and growing community. **Write, read & follow us** ![So](/files/Z6gsfFZGYEdVDylv3O8L) **Important Links & Support**\ Join our Discord; our community will answer any questions you have!\ ZipClash Website: [https://ZipClash.io](https://zipclash.io/)\ ZipClash Twitter: \ ZipClash Telegram: \ ZipClash Discord: \ ZipClash Reddit: \ As always, send your questions and feedback to --- # 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://docs-old.zipclash.io/community.md?ask= ``` 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.