# World size

### Why does world size matter?

Positions and livequeries in the world are compressed, and the compression is defined by maximum scale and bit count. Larger scale at the same bit count means lower precision, and vice-versa.

### Defining world size

A default maximum world size of `2400` means that only values from `[-2400, 2400]` will be supported for all spatial axes. 

![Settings window](/files/-MdvHbulSddbDD7ozFF_)

If our game scenes are larger than `2400 x 2` (`4800`) units across, we can increase this value in the Settings window or in the schema as illustrated below.

Don't forget to extend the LiveQuery scale to match the world position scale.

```
# Default world positions:

component WorldPosition
  value Vector3 [bits "24", scale "5000"]
  

# LiveQuery:

component WorldPositionQuery
  position Vector3 [bits "24", scale "5000"]
  radius Float [bits "24", scale "5000"]
```


---

# Agent Instructions: 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:

```
GET https://docs.coherence.io/0.5.2/optimization/world-size.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.