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

# Roadmap

This roadmap is a working plan and may change as the game, token, and community develop.

## Phase 1: Core Game Prototype

**Goal:** Make BlockOps playable as a voxel FPS.

| Area                         | Status      |
| ---------------------------- | ----------- |
| City map rooms               | In progress |
| FPS controls                 | In progress |
| Rifle, AWP, handgun          | In progress |
| Low gravity                  | In progress |
| Climbing trees and mountains | In progress |
| Training bot                 | In progress |
| Multiplayer sessions         | In progress |
| Player count room list       | In progress |

## Phase 2: Multiplayer Polish

**Goal:** Make PvP feel fair, fast, and readable.

Planned work:

* Improve network smoothing.
* Tighten server-side hit validation.
* Improve weapon precision and recoil behavior.
* Improve first-person and third-person weapon visibility.
* Improve animation for arms, legs, heads, and weapon holding.
* Improve bullet tracers and impact effects.
* Keep hitboxes aligned with the actual voxel body.

## Phase 3: Character Identity

**Goal:** Make each wallet feel like a persistent in-game identity.

Planned work:

* Wallet-linked character saves.
* Player name creation.
* Hair styles.
* Shirt styles.
* Shirt colors.
* Pants colors.
* Skin colors.
* Hair colors.
* Full landing-page voxel character preview.

## Phase 4: Economy And Rewards

**Goal:** Connect gameplay to the reward economy.

Planned work:

* Token-holder eligibility checks.
* In-game credit tracking.
* 24-hour claim window.
* Daily reward pool display.
* Claimable SOL calculations.
* Server-side payout records.
* Anti-farming checks.
* Treasury claim flow.

## Phase 5: Public Launch

**Goal:** Open BlockOps to broader public play.

Planned work:

* Public game website.
* Token launch details.
* Public tokenomics page.
* Final reward rules.
* Leaderboards.
* Daily prize pool metrics.
* Community clips and trailer assets.
* Clear crypto disclaimer.

## Longer-Term Ideas

Potential future features:

* More city rooms.
* Seasonal leaderboards.
* Community tournaments.
* Cosmetic unlocks.
* Spectator mode.
* Private rooms.
* Mobile-friendly support where practical.
* More weapon tuning and movement options.

These ideas are not required for the first version. The priority is a simple, fun FPS with fair rewards.


---

# 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://documentation.block-ops.fun/block-ops-mechanics/roadmap.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.