> For the complete documentation index, see [llms.txt](https://litepaper.pixels.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://litepaper.pixels.xyz/core-pixels-and-gameplay.md).

# Core Pixels & Gameplay

Despite achieving leading Web3 DAU, Core Pixels revealed two fundamental challenges: (i) an incomplete core loop that recycled coins without sufficient sinks, and (ii) limited end-game activities leading to player withdrawal rather than reinvestment.

### Fixing the Core Loop

The immediate priority is addressing core economic issues to elevate Return on Reward Spend above 1. Key interventions include:

| Issue                   | Intervention                                                                                                               | Status                           |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------- | -------------------------------- |
| Infinite coin inflation | Progressive Speck Upgrades. Plots can expand indefinitely with escalating coin and resource costs.                         | Design finalized; art production |
| Lack of durable sinks   | Crafting Durability. Stations, tools, and consumables degrade over use, renewing resource demand.                          | Prototype in testing             |
| Resource oversupply     | Enhanced High-tier Recipes. Introduce T3/T4 recipes emphasizing long timers, higher XP, and significant coin requirements. | Balancing in progress            |
| Inventory hoarding      | Inventory Caps. Soft limits implemented with purchasable storage expansions.                                               | Specifications complete          |
| Limited earning paths   | VIP Gate. Daily tasks and withdrawals gated behind VIP status (accessible via fiat or $PIXEL).                             | Live                             |

These strategic adjustments complete the economic cycle (craft → earn → upgrade → craft), embedding sustainable coin sinks that dynamically scale.

### Chapter 3 — The End-Game Social Meta

In parallel, a significant update known as Chapter 3 aims to transform late-game balances into social engagement and meaningful player progression. Do note - a lot of this is subject to change as we develop and progress - but we want to give you an idea of where we are headed!

* Exploration Realms. Procedurally generated islands accessible via Voyage Contracts (purchased with $PIXEL), rewarding players with cosmetic blueprints and rare items.
* LiveOps Templates. Regularly scheduled, easily deployable events (e.g., Fishing Frenzy, Harvest Rush) designed to increase player engagement.
* Social Enhancements. Proximity chat, emote-based interactions, referral-based rewards, and share-to-earn mechanisms designed to organically grow player networks.

### Next First-Party Title — Pixels Pals

Alongside Core Pixels enhancements, development is underway for Pixels Pals, a synchronous, two-player digital pet game inspired by popular apps like Sush and Pengu.

Players raise, customize, and trade digital pets, contributing valuable interaction data back into the Smart-Reward Ad Network. A beta release is planned for June–July 2025, initially launching on Android and followed by web access. Pixels Pals targets mainstream adoption with a delayed wallet requirement (introduced after seven days of engagement), featuring integrated $vPIXEL micro-transactions from launch.


---

# 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://litepaper.pixels.xyz/core-pixels-and-gameplay.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.