> For the complete documentation index, see [llms.txt](https://xcs-plugin.gitbook.io/cursorcs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xcs-plugin.gitbook.io/cursorcs/guides/fov-and-personal-distance.md).

# fov and personal distance

CursorCs includes a player command that lets each player adjust hologram distance based on their own FOV preference.

Command:

```bash
/cursor fov <value|reset>
```

***

## What this command does

This command changes the player's personal hologram distance so the UI feels more comfortable for their camera FOV.

This is useful when:

* one player uses a very high FOV
* another player uses a low FOV
* the same HUD feels too close for some players
* the same HUD feels too far for some players

Instead of changing the global config for everyone, each player can adjust their own distance.

***

## Basic usage

Set a personal FOV-based distance:

```bash
/cursor fov 110
```

Another example:

```bash
/cursor fov 80
```

Reset back to the global distance:

```bash
/cursor fov reset
```

***

## Supported range

The supported FOV range is:

* `30`
* to
* `170`

If the player enters a value outside that range, CursorCs clamps it automatically.

Example:

```bash
/cursor fov 200
```

This will be treated as:

```
170
```

***

## What happens after changing it

When the player runs the command:

* their personal FOV override is saved
* their personal hologram distance is recalculated
* if they already have an active cursor session, the distance is refreshed immediately

That means the player does not need to rebuild the whole menu manually just to feel the difference.

***

## When to use this

This command is especially useful for:

* players who prefer very high FOV
* players who use low-FOV cinematic setups
* testing HUD readability
* comparing menu spacing during setup

***

## Example workflow

{% stepper %}
{% step %}

### Start the cursor

```bash
/cursor start
```

{% endstep %}

{% step %}

### Try a high-FOV feel

```bash
/cursor fov 110
```

{% endstep %}

{% step %}

### Try a lower-FOV feel

```bash
/cursor fov 80
```

{% endstep %}

{% step %}

### Return to the normal shared distance

```bash
/cursor fov reset
```

{% endstep %}
{% endstepper %}

***

## Recommended values

Common values to test:

* `110`
* `100`
* `90`
* `80`
* `70`
* `60`

If you are not sure where to start, `90` or `100` are good first tests.

***

## Good use cases for server owners

You can recommend `/cursor fov` to players when they say:

* "the menu looks too close"
* "the HUD feels too far"
* "the cursor UI feels weird with my FOV"

This is often easier than changing the menu layout for every player.

***

## Resetting to default

If a player wants to go back to the server default:

```bash
/cursor fov reset
```

This removes the personal override and uses the normal global hologram distance again.


---

# 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://xcs-plugin.gitbook.io/cursorcs/guides/fov-and-personal-distance.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.