> For the complete documentation index, see [llms.txt](https://disrupter.rvgames.company/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://disrupter.rvgames.company/game_modes/campaign.md).

# Campaign

For Disrupter, a campaign is defined as a series of games played amongst the same players. The simplest option is to declare a winning number of games and to play your campaign until someone has won that many games.

## **Reserves**

You can give each side a Reserve force with the same number of Units as their Platoon.

Whenever a Unit is removed from the Board, roll a d100. If you roll under 50, the Unit is incapacitated, and if you roll 50 or more, the unit is dead. In between matches, a Platoon may replenish dead Units with Units from the Reserve force. Incapcitated Units are able to return to fight in the next game.

Play games in your campaign until one side's forces are eliminated or a side surrenders.

## **Debt**

A Debt economy will be developed in a future release (See [TODO](/todo.md)). This will allow each Force to be more customized and provides a method for upgrading Platoons over time.


---

# 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://disrupter.rvgames.company/game_modes/campaign.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.