> For the complete documentation index, see [llms.txt](https://whitepaper.cryptofights.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.cryptofights.com/world/fighters/ability-points.md).
# Ability Points
Determine the efficiency of attack, defense, evasion, and spellcraft. Strength, Dexterity and Intelligence are measured as Ability Point, Ability Score and Ability Modifier.
### **💪 Ability: Point, Score and Modifier**
1. **Ability Point:** Individual Points of Strength, Dexterity & Intelligence.
2. **Ability Score:** The total tally of your Ability Points ranging from 7 to 23+
3. **Ability Modifier (AM):** Applied bonus or penalty to rolls, making or breaking a battles outcome.
* **Bonus Modifier (BM)** for each Ability Point higher than +11 Ability Score.
* **Penalty Modifier (PM)** for each Ability Point lower than -11 Ability Score.
Fighter Stat Example with Ability Score vs. Ability Modifier Chart
---
# 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://whitepaper.cryptofights.com/world/fighters/ability-points.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.
