> For the complete documentation index, see [llms.txt](https://docs.realmtoken.vip/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmtoken.vip/2.-features/spatial-audio.md).

# Spatial Audio

In most games, voice chat is a flat, chaotic channel where everyone speaks at the same volume. In REALM.AI, audio is treated as a physical object.

#### 3D Proximity Voice

* Distance Attenuation: If someone is standing 20 meters away, they sound quiet. If they walk up to your ear, they sound loud.
* Directional Audio: Hear exactly where a voice is coming from—left, right, above, or behind.

#### Environmental Acoustics

Our audio engine calculates how sound interacts with the architecture around you.

* Occlusion: If a user walks behind a thick concrete wall, their voice becomes muffled.
* Reverb & Echo: Shouting in a small tiled bathroom sounds different than shouting in an open park. Boardrooms feel intimate; stadiums feel massive.

#### Social Dynamics

This technology completely changes how communities interact:

* Private Conversations: Step into a corner to have a private whisper without leaving the server.
* Natural Networking: Walk through a crowded digital bar and hear snippets of conversations as you pass by, just like a real mixer.
* No "Mute All": The chaos of traditional voice lobbies is replaced by the natural order of physical distance.


---

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

```
GET https://docs.realmtoken.vip/2.-features/spatial-audio.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.