> For the complete documentation index, see [llms.txt](https://castleoverlord.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://castleoverlord.gitbook.io/whitepaper/about-the-game/target-audience.md). # Target Audience The strategy genre has grown in popularity thanks to groundbreaking mid-core games such as Clash of Clans and Plants vs. Zombies. We expect Castle Overlord to occupy the similar market space as these games. This market space is characterized below.


Age	Wide appeal, primarily 18 to 40 years old.
Geography	Majority player base is expected to spread across North America, Europe, and Southeast Asia.
Gender	75% Male, 25% Female
Player Type	Casual 5% / Core 80% / Hardcore 15%
Class	Wide appeal, primarily upper middle class and above due to the in-game economy system.
Lifestyle	Adults with indoor lifestyles who are familiar with the internet culture.
Taste	Strategy games enthusiasts, people who like to min-max their actions for optimal benefit.
Age Rating	PEGI12 for animated violence and the use of cryptocurrency.

--- # 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://castleoverlord.gitbook.io/whitepaper/about-the-game/target-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.