> For the complete documentation index, see [llms.txt](https://tim-18.gitbook.io/tezotrooperz-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tim-18.gitbook.io/tezotrooperz-guide/collection-concept/additional-statistics.md).

# Additional Statistics

In the NFT’s metadata, you will be able to find three fields that are not made from the Layers nor the Rarity Score. 

Those fields are:

* Intelligence 
* Agility 
* Force

Intelligence score defines the % chance to get your $REBL stolen by Titan while doing the ‘Claim’ action.

Agility score defines the % chance that your NFT is getting captured by Titan and his army while doing the ‘Unstake’ action.

Force score defines the % chance that your NFT is getting killed (=burn) by Titan and his army while doing the ‘Unstake’ action.

The higher the score, the lower the chance of the event is to happen.

*For example, a Warrior has 95 Force, meaning that he has (100-95) 5 % of getting killed after unstacking.*

Those scores are affected by NFT according to their rank:

**Warrior:**

* Intelligence = 60 
* Agility = 90 
* Force = 95 

Long Range

* Intelligence = 70 
* Agility = 85 
* Force = 90 

**Troop Leader** 

* Intelligence = 80 
* Agility = 80 
* Force = 90 

**King & Queen** 

* Intelligence = 85 
* Agility = 75 
* Force = 90

*Examples to better understand those concepts:* 

* *After claiming his accumulated $REBL, a Warrior NFT has a 40% chance to get robbed of his $REBL token* 
* *After unstacking his NFT, a Troop Leader NFT has a 20% chance of being captured by Titan and his army.* 
* *After unstacking his NFT, a King NFT has a 10% chance of getting killed by Titan and his army.*

Along with the game developments of new features, those stats are willing to change, in a good or a bad way...


---

# 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:

```
GET https://tim-18.gitbook.io/tezotrooperz-guide/collection-concept/additional-statistics.md?ask=<question>
```

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.