> For the complete documentation index, see [llms.txt](https://telgather.gitbook.io/web3pvz-deadpaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://telgather.gitbook.io/web3pvz-deadpaper/the-zombies-game-basics.md).

# THE ZOMBIES: Game Basics

<figure><img src="/files/wLAcZJxVP5AVhKpJPzoj" alt=""><figcaption></figcaption></figure>

## Classic Tower Defense

A Web3-enhanced evolution of the proven Plants vs. Zombies game mechanism, integrating blockchain-driven assets to enable true player ownership.&#x20;

* Merge Flower to Upgrade Defense
* Defeat Zombies to Progress

<figure><img src="/files/JTSmcEGkBaU08N67lJaK" alt="" width="563"><figcaption></figcaption></figure>

## Zombie-to-Earn

This model incentivizes player spending through strategic IAP investments in Zombie Miners. The compelling gameplay loop of merging and upgrading miners maximizes player earnings in both mining and PvP battles, driving long-term player retention and revenue growth.

* Unlock a Zombie Miner Box every time you complet 5 levels
* Mine In-Game Coins with your Zombie Miners
* Level up your Zombie Miners mint exclusive SBT Miners and begin your trilling $ZP mining adventure

<figure><img src="/files/3VYS7zGq0IQAGj2q0d0r" alt=""><figcaption></figcaption></figure>

## PK-to-Earn

Web3PvZ's PK-to-Earn mode delivers a thrilling, high-stakes Player vs. Player (PvP) experience designed to drive player engagement and offer significant rewards. This competitive mode provides players with the opportunity to double their earnings, incentivizing participation and contributing to a dynamic in-game economy. The strategic depth of PK battles promotes long-term player retention and cultivates a thriving community.

<figure><img src="/files/YBuQGcOmxvvkY6WNUnLQ" alt="" width="254"><figcaption></figcaption></figure>

1. **PvP Challenge Score: Tracks PvP performance.**
2. **Ranking Badge = Mining Speed Booster.**
3. **PvP Challenge:**
   1. **Entry:** 1 PvP Ticket, join via empty Grave.
   2. **Start:** 4 players = instant start;
      * **Countdown**: 1 player = ticket refund; <4 players = auto-start.
   3. **Match:** Two groups, auto-paired.
4. **Victory:**
   1. One group wins, the other ties → Full win.
   2. Both groups tie → Split rewards.
   3. Winners tie → Split rewards.
   4. Winners battle, one wins → Full rewards.
5. **PvP Challenge Modes:**
   1. **Casual Challenge:**
      * Play for fun! NFTs unaffected.
      * Cost: 1 Ticket
      * Rewards: Shards, Challenge Score
      * Miners: Any SBT/NFT (8 STAR1, 3 STAR2, or 1 STAR3)
      * Participants: 2-4
   2. **NFT Arena:**
      * Winner takes all NFT Points.
      * Cost: 3 Tickets + 8 NFT Points
      * Rewards: Shards, NFT Points, Challenge Score
      * Miners: NFTs Only (8 STAR1, 3 STAR2, or 1 STAR3)
      * Participants: 2-4
   3. **Zombie Cup:**
      * One ticket, all rewards!
      * Cost: 1 Ticket
      * Rewards: Shards, Challenge Score
      * Miners: Any 1 SBT/NFT
      * Participants: Unlimited

<figure><img src="/files/UmxOoBrIkPGXj7H05R2p" alt="" width="323"><figcaption></figcaption></figure>


---

# 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://telgather.gitbook.io/web3pvz-deadpaper/the-zombies-game-basics.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.