> For the complete documentation index, see [llms.txt](https://docs.skullco.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skullco.in/strike.md). # Strike ### Game Design The design traces back to the ancient Chinese hand game *shoushiling* (the ancestor of rock–paper–scissors), but extends it with asymmetric payoffs, gear, and transparent logs. The Nash equilibrium remains intact - no dominant strategy exists, but depth emerges through equipment stats, durability mechanics, and psychological pattern reading. ### Core Mechanics **Simultaneous choice combat:** Readable, mind-game combat. Players select attack and defense zones each round. **Soul NFT activation:** Each Soul NFT enables one raid per day. Players can own multiple Souls for multiple daily raids. This caps total activity and creates natural scarcity. **Gear durability:** All equipment degrades during PvE raids. Repairs are mandatory to continue playing - the primary economic sink. ### Game Modes **PvE Raids (4 players):** * Daily limit: n raids (scales with active base) * Access: 50% earned via Find2Earn, 50% purchasable * Mob encounters (66%): One NFT drop (25% chance per player) * Boss encounters (33%): Damage-based payouts, higher NFT drop rate **PvP Duels:** * Optional entry fees create prize pools * No durability loss (encourages practice) * Ranked ladder with seasonal rewards **Tournaments:** * Scheduled brackets with fixed entry costs * Prize distribution: 50% winner, 30% top 4, 20% top 8 --- # 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.skullco.in/strike.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.