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

# Statlines

Statlines represent the statistical characteristics of fighters and vehicles (Movement, Weapon Skill, Ballistic Skill, etc.).

## Two Systems

Gyrinx uses two statline systems:

1. **Legacy System** - Simple stat fields on `ContentFighter` with `_override` fields on `ListFighter`
2. **New System** - Flexible custom statline types with separate override storage

The new system supports vehicles and crew with different stat requirements (e.g., Toughness Front/Side/Rear for vehicles).

## Calculation Flow

Both systems follow this pattern:

1. Get the statline from the underlying `ContentFighter`
2. Apply any overrides from the `ListFighter`
3. Apply any mods from equipment or advancements

## Performance

The new system requires careful query optimisation to avoid N+1 queries. See the models diagram below for the relationship complexity.

## Visual Examples

Custom statlines for vehicles:

<figure><img src="https://cdn.gyrinx.app/98619d14-566f-434c-9553-a3b3c2b55203.png" alt="Vehicle statline showing Front/Side/Rear toughness"><figcaption></figcaption></figure>

## Model Relationships

<figure><img src="/files/GlwtW38yrIv0v3c7hl7X" alt="Statline model relationships diagram"><figcaption></figcaption></figure>


---

# 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://gyrinx.gitbook.io/gyrinx/n23-edition/statlines.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.