> For the complete documentation index, see [llms.txt](https://docs.perplay.io/perplay-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perplay.io/perplay-whitepaper/game-fi/nft/condition.md).

# Condition

<figure><img src="/files/jtRSBfNYkgCKHm7Dz6fV" alt=""><figcaption></figcaption></figure>

All Vehicle NFTs have a property called Condition, which initially starts at 100.

Each time you play a game and spend Power, the Condition of your Main Vehicle decreases.

The Vehicle’s Condition Status changes based on its current Condition value. The following penalties are incurred when the status changes.

<table><thead><tr><th width="161">Status</th><th>Effects</th></tr></thead><tbody><tr><td>Fine</td><td>No penalties and The vehicle is at full performance</td></tr><tr><td>Caution</td><td>Slightly reduced amount of XPER obtained through gameplay</td></tr><tr><td>Warning</td><td>Significantly reduced amount of XPER obtained through gameplay<br>Cannot earn PER through gameplay</td></tr><tr><td>Destroyed</td><td>Cannot earn XPER and PER through gameplay</td></tr></tbody></table>

Therefore, in order to always keep your Vehicle at full performance, you need to manage its Condition.

You can repair your Vehicle with an XPER fee to recover its Condition. A high Durability Stat lets you pay less XPER on Repair.


---

# 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.perplay.io/perplay-whitepaper/game-fi/nft/condition.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.