> For the complete documentation index, see [llms.txt](https://ss3d.gitbook.io/systems/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ss3d.gitbook.io/systems/chat/channels.md).
# Channels
Channels allow a player to communicate with a specific group of other players only, or to listen to only specific messages.
Channels have many properties associated with them to differentiate them. You can find a description for them in the tooltip on Unity. We only describe some important properties of channel in the following.
A channel with all its properties as of march 2024
### Distance based channels
When entering messages in some channels such as "shouts" or "whispers", only player in a given radius receive those messages.
### Headset required
Some channels such as engineer, science, medical, all require to wear specific headset to emit and listen to messages coming on them.
### Role required
Some channels ask for some specific rights, such as admins right, to be used. This is necessary so only admins can use channels sending visible messages to everyone.
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://ss3d.gitbook.io/systems/chat/channels.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.
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.
