# Game Information ## Gameplay Mechanics: ● Players can hold up to 5 cards at any given time, with deploying a champion or item consuming mana. ● After a short debuff time, another card is added to the player's hand, ensuring continuous strategic options throughout the battle. ● Defeated champions or items are added to the bottom of the deck, allowing players to strategize and adapt until a victor emerges. ## Game Interactions: ● Dynamic weather systems, interactive battlegrounds, and seasonal changes provide immersive and ever-changing environments. ● Characters evolve over time, reflecting their journey and growth within the game world. ● OnPC:Utilizes traditional controls similar to other competitive WEB-GL-based games, utilizing left & right mouse functionality. ● OnMobile: Played with simple tapping, holding, and drag interactions, ensuring accessibility and intuitive gameplay. ### Heroes: ● Total of 4 battle commanders, each with unique active spells to turn the tide of battle. ### Champions: ● Total of 17 deployable entities on the battlefield, each with three base stats: Mana, Damage, and Health. ### Items: ● Represent spells and weapons, enhancing champion abilities or targeting enemy champions with their own mana cost. ### Abilities: ● Passive abilities are always active, providing additional stats or powered attacks to allied units. ● Active abilities consume mana and have a debuff counter, adding depth and strategy to combat. ### Cosmetic Options: ● Players can customize their visual experience with skins, unique battlegrounds, and emotes, adding personal flair to their battles and interactions within the game. --- # 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://mystic-reign.gitbook.io/whitepaper/mystic-battle-game/game-information.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.