# War

All actions in *Battle For Blockchain* revolve around a singular purpose: winning the war—the grand conflict that has drawn the finest warriors to the lands of **Culinaris**. Through strategic movement across the map, players conquer territory and accumulate **Victory Points**. Once a player asserts enough dominance, a **Siege** is triggered, marking the final chapter of the war.

<figure><img src="/files/2dLBUGqVGMfbqlyYSTrf" alt=""><figcaption></figcaption></figure>

### Zones

Players battle for control over the region of **Culinaris**, which is divided into 24 distinct Zones. They can launch attacks to capture these Zones or defend them against incoming assaults from the opposing kingdom.

Each successful attack reduces a Zone’s **HP**. When a Zone’s HP reaches zero, control shifts to the opposing kingdom, and the Zone’s HP is fully restored.

Zones can be of two sizes:

* **Small** - Battlefields size is 8x4 (split into a 4x4), and Zone HP equals to 16000.
* **Large** - Battlefields size is 8x5 (split into a 4x5), and Zone HP equals to 20000.&#x20;

Each Zone also favors a specific resource. Battling in that Zone grants increased rewards of its favored resource after the battle.

### The Goal - Victory Points

The primary objective of each war is to accumulate a set amount of **Victory Points (VP)**. The first kingdom to reach this target is declared the winner, triggering the **Siege** and bringing the war to its final stage.

Each Zone generates a fixed amount of Victory Points over time. Some Zones yield more, while others produce less. However, Victory Points must be **claimed** from each Zone to count toward the victory condition. When a Zone changes hands, its unclaimed VP is automatically awarded to the new controlling kingdom.

Additionally, a few special Zones generate different amounts of Victory Points depending on which kingdom controls them, adding an extra layer of strategic depth to the war.

* Forktown Perimeter (Picklestadt, Avocadia, Ovenburg, Radish Mine) will produce double VP, if Spooncity holds these Zones.
* Spooncity Perimeter (Frogwise Summit, Sweetly, Citrus Sanctum, Teaton) will produce double VP, if Forktown holds these Zones.

### Repairing

The defense of a Zone can be extended through **repairs**, allowing players to restore its HP by spending resources. The type of resource required depends on the Zone’s favored resource.

If the Zones favors:

* Wood, then you will need Stone to repair it
* Stone, then you will need Iron to repair it
* Iron, then you will need Wood to repair it

The first repair costs **100** of the relevant resource. Each subsequent repair increases the cost by **100**. However, when control of the Zone changes, the repair cost resets back to **100**.

<figure><img src="/files/ZWQqvCu2jtnU0Lp7wys1" alt="" width="401"><figcaption></figcaption></figure>

### Siege

Siege specific are written in its own [section](/battle-for-blockchain/war/siege.md).

### Grand Reset

When one war ends, another begins. Between them lies **The Grand Reset**—a moment of renewal where much of the world is wiped clean to ensure a fair start for the next great conflict.

#### **What will be reset:**

* Players’ **unit inventory**
* Players’ **resources**
* Players’ **teams** *(yes, you can switch sides—and betray your kingdom!)*
* **Unit prices**
* **Kingdom upgrades**
* **Zone health**
* **Zone ownership**

#### **What remains permanent:**

* Players’ **item inventory** and **bentoboxes**
* Players’ **$BFB**
* Players’ **quest progress**


---

# Agent Instructions: 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:

```
GET https://battle-for-blockchain.gitbook.io/battle-for-blockchain/war.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
