> For the complete documentation index, see [llms.txt](https://docs.archerhunter.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archerhunter.io/the-archer-hunter/core-game-concept.md). # Core Game Concept Archer Hunter is an **action-packed role-playing game (ARPG)** that blends fast-paced combat, strategic progression, and on-chain asset ownership into a seamless gaming experience. Players step into the role of elite archers, each uniquely skilled and equipped to face relentless waves of enemies in dynamic battle environments. The game’s design philosophy focuses on creating **short-session, high-intensity gameplay** that can be enjoyed on-the-go, while also offering long-term depth through progression systems, competitive challenges, and collaborative events. Unlike traditional RPGs, Archer Hunter is designed from the ground up with a **Proof-of-Web2 (PoW2)** approach, allowing Web2 gamers to play instantly without requiring wallets or blockchain knowledge, while giving Web3-native players the ability to fully own, trade, and upgrade their assets on-chain. This hybrid model ensures a **massive accessible audience** while retaining the benefits of decentralization, transparency, and digital asset value preservation. The game’s aesthetic blends **fantasy medieval themes** with vibrant, stylized art, designed to appeal to a broad demographic while maintaining distinct hero designs, enemy archetypes, and stage environments. Combat is intuitive yet challenging that relying on **player skill, tactical positioning, and timely use of special abilities** rather than simple auto-play mechanics. --- # 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.archerhunter.io/the-archer-hunter/core-game-concept.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.