# Battles Battles are the **heart of Spellborne**, combining strategic decision-making with monster growth and player choice. The system takes inspiration from classic turn-based RPGs, while adding modern layers of depth through attributes, trust, and mutation mechanics. *** ### **Battle Overview** * **Turn-Based Combat**: Players and monsters act in turns, selecting attacks, items, or switches. * **Strategic Depth**: Success depends on planning, resource management, and understanding both your monster’s attributes and your opponent’s tactics. * **Capture Opportunity**: Wild monsters can be captured mid-battle, expanding your collection and shaping your adventure. *** ### **Core Mechanics** * **Actions per Turn**: * **Attack** – Use a monster’s learned move. * **Item** – Heal, buff, or influence the battle. * **Switch** – Swap an active monster with one from the squad. * **Capture** – Attempt to trap a wild monster with crystals. * **Attributes & Stats**: Each monster has base stats such as **HP, Stamina, Attack, Defense, Special Attack, Special Defense, and Speed**. These influence damage, survivability, and turn order. * **Trust Influence**: High-trust monsters perform better, respond reliably, and may unlock unique interactions. Low-trust monsters can misbehave or underperform. *** ### **Battle Types** * **PvE Battles** – Encounter wild monsters or NPC-controlled opponents across the world. * **PvP Battles** – Face other players in structured or casual formats. Competitive battles test mastery of stats, team composition, and strategic depth. * **Boss Encounters** – Larger, narrative-driven fights that often require teamwork, preparation, and resource investment. --- # 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://whitepaper.spellborne.gg/main-section/gameplay/battles.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.