> 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/welcome-to-block-ops.md).
# Welcome to Block Ops
**BlockOps** is a voxel first-person shooter with play-to-earn mechanics, built around fast arena combat, low-gravity movement, wallet-linked characters, and SOL rewards for eligible players.
The game takes the block-built city arenas from the existing world map system and turns them into FPS battlegrounds. Players create their own voxel fighter, enter a city room, fight in free-for-all combat, and earn in-game credits for server-validated frags against real players.
## What BlockOps Is
| Area | Description |
| ---------------- | ------------------------------------------------------------------- |
| **Genre** | Voxel FPS |
| **Core Mode** | Free-for-all last-man-standing style arena combat |
| **Player Count** | Up to **8 real players per room** |
| **Maps** | City-based voxel rooms |
| **Movement** | Low gravity, higher jumps, crouching, climbing, third-person toggle |
| **Weapons** | Rifle, AWP-style sniper, handgun |
| **Rewards** | Token holders earn claimable SOL from eligible real-player frags |
| **Identity** | Wallet-linked player name and voxel character |
## Project Vision
BlockOps is designed to be simple, readable, and competitive.
The goal is not to recreate every feature from classic tactical shooters. Instead, BlockOps focuses on the parts that matter most for a browser-based voxel FPS:
* **Fast entry:** choose a character, pick a room, play.
* **Readable combat:** simple weapon set, clear hit validation, visible bullets and impacts.
* **Vertical movement:** low gravity, climbable objects, rooftop fights, mountain control.
* **Real player rewards:** only kills against real players can generate reward credits.
* **Fair economy:** token holders share the daily reward pool based on eligible activity.
## Core Game Loop
1. Connect a wallet or enter test mode.
2. Build a wallet-linked voxel character.
3. Choose a city room.
4. Fight in free-for-all FPS combat.
5. Earn in-game credits for valid real-player frags.
6. End the session.
7. Wait for the 24-hour claim window.
8. Eligible token holders claim their share of the daily SOL reward pool.
## Why Voxel FPS?
Voxel graphics give BlockOps a clear identity:
* Characters are easy to customize.
* Maps are readable at a glance.
* Climbable objects and vertical routes are visually obvious.
* Combat can stay lightweight enough for browser play.
* The style fits crypto-native gaming without needing heavy downloads.
## Current Status
BlockOps is currently in active development.
The current build focuses on:
* Browser-based FPS gameplay.
* City room selection.
* Multiplayer sessions.
* Server-side kill validation.
* Wallet-linked character creation.
* In-game credits.
* Token-holder reward logic.
* Daily pool metrics and leaderboard UI.
## Useful Links
---
# 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/welcome-to-block-ops.md?ask=&goal=
```
`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.