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

# What is Rig Wars?

**Rig Wars** is the competitive PvP mode inside Rig Rooms — a **Solana play-to-earn game** where you stake into pack battles, crack the same pack lineup, and race to build the highest hash rate.

If the main loop is a **crypto mining simulator**, Rig Wars is the head-to-head arena layered on top.

## The pitch

> Stake $COMPUTE at the store SP rate, crack packs, build the highest hashrate — winner takes the SP prize.

## How a battle works

1. **Create or join** a 1v1 lobby with a shared pack lineup (both players get the same packs)
2. **Pay entry** in $COMPUTE equal to the face SP value at the live store rate
3. **Open packs** on a timer (pace depends on lobby difficulty)
4. **Build** operational racks from the drops
5. **Reveal** — highest operational hash rate wins
6. **Winner claims 2× entry face as SP** (prize multiplier has no house cut on that 2×)

## Key rules

| Rule             | Detail                                                        |
| ---------------- | ------------------------------------------------------------- |
| Packs per battle | 3–8                                                           |
| Max entry face   | 40,000 SP                                                     |
| Pace options     | Easy \~75s / Medium \~55s / Hard \~35s per pack               |
| Scoring          | Incomplete / non-operational racks score **0**                |
| Tie-break        | Whoever marked Ready first; otherwise deterministic coin flip |
| Empty seat       | May auto-seat **Rig Bot** if no human joins in time           |
| Leave open lobby | Entry refunded                                                |
| Fog of war       | Opponent board hidden until settle; replays after             |

Build rules match the main game: motherboard, CPU, GPUs, PSU headroom, fans, cables — same operational checklist as [Building Mining Rigs](/rig-rooms-docs/play-and-earn/building-mining-rigs.md).

## Battle packs vs normal packs

Rig Wars uses battle-specific pack pools. They **do not** drop room skins. Treat Wars loot as competitive fuel, not a substitute for every cosmetics chase.

## Why Rig Wars matters for SEO / discovery players

Players hunting a **Solana play-to-earn game** often want more than idle accrual. Rig Wars adds skill, timing, and pack-crafting under pressure — while still settling value through $COMPUTE / SP, the same economy as the wider **crypto mining simulator**.

Entry cost is market-linked because $COMPUTE converts at the live SP rate. When $COMPUTE trades as a **low market cap P2E coin**, battle stakes can feel cheap or expensive quickly — size entries you can afford.

## Strategy notes

* Prioritize **any complete operational rack** over a partial dream build
* Watch PSU wattage under time pressure
* Prefer stable MH/s over gambling every slot on one legendary if the clock is tight
* Learn pace settings before jumping into Hard lobbies
* Review replays after settle to see where hash was left on the table

## Where to play

Open Rig Wars from the Play app on [rigrooms.com](https://rigrooms.com) after you are comfortable with basic rig assembly. Public leaderboard history uses a release cutoff for older matches — live rankings reflect the current competitive season rules.

## Related pages

* [Building Mining Rigs](/rig-rooms-docs/play-and-earn/building-mining-rigs.md)
* [Packs, SP & Progression](/rig-rooms-docs/game-systems/packs-sp-and-progression.md)
* [How to Earn $COMPUTE](/rig-rooms-docs/play-and-earn/how-to-earn-compute.md)


---

# 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://rig-rooms.gitbook.io/rig-rooms-docs/game-systems/what-is-rig-wars.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.