> 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-content-library/content-library.md).

# Content Library Overview

The content library is the game data that powers Gyrinx. It contains all the fighter types, equipment, weapons, skills, rules, and other definitions from Necromunda that users draw from when building their lists. Everything in the content library is managed through the Django admin interface.

When a user creates a list and adds fighters to it, they're selecting from templates defined in the content library. The content library defines *what's available*; users create their own instances of that content in their lists.

## How this section is organised

Each document covers a distinct area of the content library, including the models involved, how they appear in the admin, how they affect the user-facing application, and common administrative tasks.

| Document                                                                                                                  | What it covers                                                                                           |
| ------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| [Houses & Factions](/gyrinx/n23-content-library/houses-and-factions.md)                                                   | Gang factions, the `generic` and `legacy` flags, house-specific cost overrides                           |
| [Fighters & Fighter Types](/gyrinx/n23-content-library/fighters.md)                                                       | Fighter archetypes, categories, default equipment loadouts, category terminology                         |
| [Stats & Statlines](/gyrinx/n23-content-library/stats-and-statlines.md)                                                   | Stat definitions, statline types, the legacy vs custom statline system                                   |
| [Skills, Rules & Psyker Powers](/gyrinx/n23-content-library/skills-rules-and-psyker-powers.md)                            | Skill trees, special rules, psyker disciplines and powers                                                |
| [Equipment & Weapons](/gyrinx/n23-content-library/equipment-and-weapons.md)                                               | Equipment items, weapon profiles, traits, accessories, upgrades, rarity                                  |
| [Equipment Availability & Restrictions](/gyrinx/n23-content-library/equipment-availability.md)                            | Fighter-specific equipment lists, category restrictions, availability presets                            |
| [Equipment List Expansions](/gyrinx/n23-content-library/equipment-list-expansions.md)                                     | Conditional equipment unlocked by attributes, house, or fighter category                                 |
| [Modifiers](/gyrinx/n23-content-library/modifiers.md)                                                                     | The polymorphic modifier system that changes stats, traits, rules, and skills                            |
| [Injuries](/gyrinx/n23-content-library/injuries.md)                                                                       | Injury groups, outcomes, and how injuries affect fighters during campaigns                               |
| [Gang Attributes](/gyrinx/n23-content-library/gang-attributes.md)                                                         | List-level attributes (Alignment, Alliance, Affiliation) and their effects                               |
| [Advancements](/gyrinx/n23-content-library/advancements.md)                                                               | Equipment advancements fighters can purchase with XP during campaigns                                    |
| [Promotions](/gyrinx/n23-content-library/promotions.md)                                                                   | Promotion paths — category relabels and type changes (Ganger → Specialist, Prospect → Champion)          |
| [Counters & Roll Tables](https://github.com/gyrinx-app/gyrinx/tree/main/docs/content-library/counters-and-roll-tables.md) | Fighter-level tallies (e.g. Kill Count), dice tables, and "spend and roll" flows like Spyrer Power Boost |
| [Content Packs](/gyrinx/n23-content-library/content-packs.md)                                                             | User-created custom content collections and the pack filtering system                                    |
| [Reference Library](/gyrinx/n23-content-library/reference-library.md)                                                     | Book and page references used for in-app tooltips                                                        |

## Key ideas

**Content vs user data.** The content library (`ContentFighter`, `ContentEquipment`, etc.) defines templates. User data (`ListFighter`, `ListFighterEquipmentAssignment`, etc.) holds the instances users create from those templates. Content is managed by admins; user data is created by users through the application.

**Cost propagation.** When you change a cost in the content library, the system automatically marks affected user data for recalculation. See [Equipment & Weapons](/gyrinx/n23-content-library/equipment-and-weapons.md) for details on how this works.

**Modifiers.** Equipment, upgrades, accessories, and injuries can all carry modifiers that change fighter stats, weapon stats, traits, rules, skills, and more. The [Modifiers](/gyrinx/n23-content-library/modifiers.md) documentation explains the full system.

**Pack filtering.** Content that belongs to a custom content pack is hidden from normal queries by default. The [Content Packs](/gyrinx/n23-content-library/content-packs.md) documentation explains how this works.


---

# 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-content-library/content-library.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.