> For the complete documentation index, see [llms.txt](https://pallette-wars.gitbook.io/pallette-wars-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pallette-wars.gitbook.io/pallette-wars-docs/how-a-war-works.md).

# How a war works

2h creative, 4h open war, then a 1h jury in parallel with the next war.

An epoch is one full war on a fresh canvas. Wars never wait on voting.

```mermaid
flowchart LR
    C[0-2h Creative] --> O[2-6h Open war]
    O --> F[Freeze]
    F --> N[War N+1 starts]
    F --> J[1h jury on War N]
    J --> R[resolveEpoch 50/25/15/10]
```

## 1. Creative phase — first 2 hours

Home turf only: Pixel, Roller, and Washer. Sabotage tools are locked. This is the guaranteed build window so both sides can paint the theme before nukes land.

## 2. Open warfare — hours 2 to 6

Full arsenal. Fog of war on the enemy half. Radar, Smoke, Supply, Bombs, Nukes, Orbitals all live. The last stretch is the climax — Share Points still count, but late spend is weighted less.

## 3. Freeze + next war

At 6 hours the board locks. Anyone can call `advanceEpoch()`. War N+1 starts immediately so painters are never idle. The frozen War N board stays on `/voting`.

Leftover ink in your tank stays yours. It is not taken when the war freezes.

## 4. Jury — 1 hour in parallel

When an X poll is up, the community decides who painted the theme better. If no tally is submitted before `juryEndsAt`, the hub resolves by **on-chain pixel-count** (`auto-pixels-epoch-N`). Overnight wars do not wait for a human.

After resolve the vault splits 50/25/15/10. Winners claim the war jackpot. 15% accrues to the UTC monthly pool (winning-epoch Share Points only).

{% hint style="success" %}
You can paint the new war while the previous war is still being judged.
{% endhint %}

{% hint style="info" %}
Do not promise a live X vote on every epoch. Pixel-count is the unattended default.
{% endhint %}

## Theme

Each war has one topic plus a reference image. Both factions reinterpret it — not a pixel-perfect copy.

* Home turf: shared theme palette (color indices 8-19)
* Sabotage: faction colors only (Blaze 0-3, Frost 4-7)
* Theme colors require a locked faction and home turf

Jury question: Who painted the theme better?

## Where to go in the app

| Route     | When                                   |
| --------- | -------------------------------------- |
| `/play`   | Paint during War                       |
| `/voting` | Frozen board, poll (if posted), claims |
| `/`       | Theme, live window, gallery            |


---

# 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://pallette-wars.gitbook.io/pallette-wars-docs/how-a-war-works.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.