> 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/faq.md).

# FAQ

<details>

<summary>What is BlockOps?</summary>

**BlockOps** is a voxel FPS with play-to-earn mechanics. Players enter city-based rooms, fight in free-for-all combat, and eligible token holders can earn SOL rewards from valid real-player kills.

</details>

<details>

<summary>Is BlockOps a soccer game?</summary>

No. BlockOps uses voxel maps and characters from the broader project lineage, but the game itself is a first-person shooter.

</details>

<details>

<summary>How many players can join a room?</summary>

Each room supports up to **8 real players**.

</details>

<details>

<summary>Are there teams?</summary>

No. The current game mode is free-for-all.

</details>

<details>

<summary>What happens if I am alone in a room?</summary>

A training bot can appear so you can practice movement and aim.

</details>

<details>

<summary>Do bot kills earn rewards?</summary>

No. **Bot kills do not count for SOL rewards.** Only valid kills against real players can create reward credits.

</details>

<details>

<summary>Can free players play?</summary>

Yes. Free players can enter rooms and compete, but they are not eligible for SOL rewards.

</details>

<details>

<summary>Who can earn SOL rewards?</summary>

SOL rewards are planned for eligible token holders. Reward eligibility should be checked server-side.

</details>

<details>

<summary>How are rewards calculated?</summary>

Rewards are distributed proportionally from the daily reward pool.

```
player_reward = daily_pool * (player_eligible_kills / total_eligible_kills)
```

</details>

<details>

<summary>Why is there a 24-hour claim delay?</summary>

The 24-hour window gives the system time to calculate the daily pool, count eligible kills, detect suspicious activity, and prevent invalid claims.

</details>

<details>

<summary>What weapons are available?</summary>

The current core loadout is:

* **1:** Rifle
* **2:** AWP-style sniper
* **3:** Handgun

</details>

<details>

<summary>Does BlockOps have low gravity?</summary>

Yes. BlockOps uses low gravity, higher jumps, and longer airtime to make vertical movement part of the game.

</details>

<details>

<summary>Can players climb terrain?</summary>

Yes. Trees, mountains, rocks, and selected voxel objects are intended to be climbable. Large climbable terrain should also be solid so players cannot walk or shoot through it.

</details>

<details>

<summary>Can I customize my character?</summary>

Yes. Players can build a voxel character with a name, hair style, shirt style, shirt color, pants color, skin color, and hair color.

</details>

<details>

<summary>Is the character linked to my wallet?</summary>

Yes. The intended account model links the player's character and stats to their wallet.

</details>

<details>

<summary>Can I use third-person mode?</summary>

Yes. BlockOps includes a third-person player perspective in addition to the main first-person FPS view.

</details>

<details>

<summary>How does BlockOps prevent cheating?</summary>

Reward-eligible kills should be validated by the server. The server should check position, aim direction, weapon timing, line of sight, hitboxes, and kill attribution before credits become claimable.

</details>

<details>

<summary>Where can I play?</summary>

The current public website is:

```
https://block-ops.fun
```

</details>


---

# 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/faq.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.