> For the complete documentation index, see [llms.txt](https://chubby-troops.gitbook.io/chubby-troops/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chubby-troops.gitbook.io/chubby-troops/chubby-troops-nft/battle-mechanics.md).

# Battle Mechanics

### What will actually happen in a fight ?

Each NFT will be made up of unique traits. Each trait will have some value for **Health**, **Punch**, **Kick**, **AOD**, **AAA**.

What will a NFT do it in a particular round will be decided by **2 Attributes 1st AOD and 2nd AAA**.

For the **First Round** Battle Mechanics will look at NFT’s **AOD**. Let suppose NFT has a **45 AOD** that means NFT has a 45% chance of doing an attack, 45% chance of pulling of a defensive stance and 10% chance of just being Idle.

If NFT chooses to attack, it will have to choose which attack to perform. Punch and Kick both carries 40% weightage and 20% is reserved of Dooms day canon. Each and every species will have the capability to shoot Dooms day canon.

Another case will be if NFT chooses to defend, in this case it will nullify opponents Punch and Kick damage but it won’t be able to nullify dooms day canon.

So when does **AAA** come into picture. Alright lemme explain, Once your NFT has chosen to attack, for the next round battle mechanics will look at the value of **AAA** to choose between Attack, Defend or Idle. 

**AAA** Value is lower than **AOD** so that battles are fair. We don't want a NFT with higher Punch and Kick damage just go on an attacking spree and win every match.

**All in all if you have defended or you were idle in your previous chance battle mechanics will take AOD in consideration, otherwise it will look at AAA.**

Punch and Kick damage will be associated with the NFT, but Dooms day canon damage is fixed. Dooms day canon will deal 1000 damage to health.


---

# 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://chubby-troops.gitbook.io/chubby-troops/chubby-troops-nft/battle-mechanics.md?ask=<question>&goal=<endgoal>
```

`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.