> For the complete documentation index, see [llms.txt](https://docs.wlos.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wlos.dev/roadmap/upcoming-features.md).

# Upcoming Features

### Planned Releases

**📅 May 2025 – Marketplace Launch**

* Trade farmers and assets with other players
* View farmer stats and history
* Purchase limited edition drops

<br>

**📅 June 2025 – Heroes Update**

* Hero NFTs with unique boost abilities
* Leveling system and traits
* Heroes will amplify farmer yield and compete in events

<br>

**📅 July 2025 – Battle Arena Alpha**

* PvP battle system with seasonal rewards
* Strategy-based power and trait mechanics
* Staked battles and leaderboard for the top warriors

<br>

**📅 August 2025 – Item System**

* Equip heroes with powerful items
* Marketplace item trading
* Limited seasonal gear drops

<br>

**📅 Q3 2025 – Guilds & Community Raids**

* Group-based play and rewards
* Competitive leaderboard between guilds
* Raid bosses for high-tier loot

***

### System expansions

* Full in-game economy dashboard
* More staking options (flexible vs. locked)
* Mobile app planning
* Governance system for community votes


---

# 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://docs.wlos.dev/roadmap/upcoming-features.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.