> For the complete documentation index, see [llms.txt](https://docs.blockchaincuties.com/blockchain-cuties-universe-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blockchaincuties.com/blockchain-cuties-universe-knowledge-base/bcu-mechanics/game-mechanics/battle-types/round-based-battles.md). # Round Based Battles #### Round based battles The Round based battles are the first variation of the combat mechanic in the game. It is fully automatic. This means, that whenever a Cutie is going on an adventure, the battle will be automatically rolled and the player will only get a report back of what has happened during the battle. In this type of battle, the winner is decided by winning 2 rounds in total. Rounds that end up in a draw do not count towards the overall score. There are 2 phases in combat. Attack and Defense. During the attack phase of the Cutie, its attack value is derived from the following: `Power + Attack + Element (if applicable) + 20 sided dice roll (further d20)` Whenever one Cutie attacks their opponent is in the defense stage, which is calculated as so: `Power + Defense + Element (if applicable) + d20` Whoever has the higher value wins the turn. One round consists of 2 turns, meaning, both Cuties have an Attack and a Defense phase. Whoever wins more turns wins the round. It can be 2:0, 1:0 (whenever there is a draw for one round).\ \ If both Cuties win 1 turn each, the round is considered a draw, and no points are allocated towards the total battle score. Here is an example of an RB battle: ![Round 1 of the Fight](/files/nZTLTTTIYwpRcsra3cqM) In the first round, our Cutie Won. \ It rolled a 16 on a d20 and the power rating of the Cutie (12) has been added to the attack. \ The defending opponent rolled a 5 and its element, which is a negative value, took away from its defense. The turn goes to our Cutie as 28>3. Next turn, the opponent is attacking. They rolled a 13 and the negative element also hindered their attack, lowering their score to 11. However, our Cutie lucked out and evaded the attack altogether, which automatically makes the round a win for us. The whole round goes to us here with a score of 2:0. The total score now is 1:0 in our favor. Let's take a look at the second round: ![2nd round of the same battle](/files/6Xfi2jOcvLFy92aeNajG) In the first turn of the round, we attack again. Our Cutie ends up with a score of 27, while the defending Cutie fumbled the defense completely, losing the turn. The round score is 1:0 The opponent attacks now. Rolling a score of 14, but our Cutie ended up with 27. 14<27 so our Cutie wins this turn as well. The round score becomes 2:0 in our favor, we gain another Round point. This, in turn, makes the overall score also 2:0. As the win condition is 2 points, we win the battle and gain [experience](/blockchain-cuties-universe-knowledge-base/bcu-mechanics/game-mechanics/experience.md) and the game rolls our [drop](/blockchain-cuties-universe-knowledge-base/bcu-mechanics/game-mechanics/adventures/level-difference-drop-rate-modifier.md). ![Victory!](/files/TzHO2YFmE9GOjHZIYAhG) This type of combat is used in [Adventures](/blockchain-cuties-universe-knowledge-base/bcu-mechanics/game-mechanics/adventures.md) and [Raid Bosses](/blockchain-cuties-universe-knowledge-base/bcu-mechanics/game-mechanics/raid-bosses.md). --- # 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.blockchaincuties.com/blockchain-cuties-universe-knowledge-base/bcu-mechanics/game-mechanics/battle-types/round-based-battles.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.