> For the complete documentation index, see [llms.txt](https://planetary-defense-guide.gitbook.io/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://planetary-defense-guide.gitbook.io/guide/getting-started/readme/web-game-v3.md).

# Web Game

A closer look at the Web Game, Planetary Defense's browser-based strategy game.

The Web Game is Planetary Defense's browser-based game, the interface where you manage your account, craft NFTs, track your progress, compose your Divisions and start missions. It's still in beta and actively developed: new features are added over time.

### What's live right now

The main gameplay is doing missions through various planets to gain TLM, DEF and Quantum Chests.

At this stage, the Web Game is focused on crafting: opening Quantum Chests and Quantum Keys to gather Materials, and using them to craft Planetary Defense NFTs. You can also Sacrifice and Ascend your NFTs.

### Quantum Chests and Quantum Keys

Quantum Chests and Quantum Keys are the two items you'll use to gather crafting Materials. Opening a Quantum Chest by itself gives you a chance at Common, Uncommon, and Rare Materials. Combine a Quantum Chest with a Quantum Key, and the odds shift toward the higher tiers, Epic, Legendary, and Mythic Materials. The rarer the Materials, the stronger the NFTs you can craft from them.

### What's not live yet

Some features you may have heard about are not available in the Web Game yet: land management, defense missions, and PvP battles.

### NFTs and future integrations

Every NFT you craft in the Web Game is a Planetary Defense NFT, with a rarity tier that reflects the quality of Materials used to craft it. Support for additional NFT collections connecting into your stats is planned for a future update.

### A quick walkthrough, step by step

The in-game guide breaks the whole loop down into a few steps, condensed here:

* Connect a WAX wallet (Cloud Wallet, Anchor, or Wombat) to log in; your account name and WAX, TLM, and DEF balances then show in the top corner.
* Stake your NFTs, Warlords, Mercenaries, weapons, Supplies, Creatures, Lava Lux, and land, so they become usable in-game.
* Create a division led by a staked Warlord, then fill it with Mercenaries and equip weapons, Supplies, Lava Lux, and Creatures to boost its stats.
* Level up your Forge to unlock more division, Equipment, Supply, and Lava Lux slots, using TLM and DEF to pay for each upgrade.
* Launch missions, picking a planet and a mission your division's power can handle, and paying any TLM entry fee.
* Claim your rewards once a mission wraps up, and track your standing on the Leaderboard.

Along the way, TLM covers mission entry fees, forge upgrades, and rewards, while DEF is spent specifically on forge slots and upgrades. The guide also frames PvP raids on rival lands as one of the game's three core pillars, alongside NFT staking and PvE missions, though as covered above, PvP is not live yet.

## Learn more about the Web Game 👇

{% content-ref url="/pages/Cb35Rlpmkb9m85YfV55u" %}
[Web Game](/guide/web-game/introduction.md)
{% endcontent-ref %}

{% hint style="info" %}
Note: The information on this page reflects the current state of Planetary Defense's development. As new features are actually released and the game evolves, some details here may change, and this page will be updated to stay accurate.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://planetary-defense-guide.gitbook.io/guide/getting-started/readme/web-game-v3.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
