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

# Radio

Tune in and game on! Learn how to set up EasyFortniteStats' radio feature, bringing Fortnite's in-game radio straight to your server.

The radio function allows you to listen to the radio stations from the game, which are usually only available when driving a car.

To start a radio session, simply join a voice channel where the bot also has access to. The `/radio` command makes the bot join and starts playback.

## <img src="https://933076529-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LjpXsmo7aeUKmSF7KVz%2Fuploads%2FzmnwuparrX7KQkk1Qwfz%2Fpremium.png?alt=media&amp;token=23b4cef5-d511-431f-be0e-4b43c96c8c6d" alt="" data-size="line"> Premium Features

<details>

<summary>24/7 Radio Playback</summary>

Keep your radio playing continuously, even when all users leave the channel. The bot will also automatically reconnect after restarts to ensure uninterrupted playback.

</details>

<details>

<summary>Radio Volume Control</summary>

Customize the radio volume, with the ability to increase it up to 200%. The default setting is 50% to conserve bandwidth.

</details>

## Permissions and DJ Role

By default, the currently active player is owned by the user who started it. Additionally all users with `Administrator` or `Manage Server` permission can also interact with the player. Furthermore a role named `Fortnite Radio` (name isn't case sensitive) is also able to control the player at any time.

{% hint style="info" %}
If only team members should be able to access the radio, for example, because it runs in 24/7 mode, all users should have their permissions removed for the `/radio slash` command.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.easyfnstats.com/features/radio.md?ask=<question>&goal=<user_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 `automate deployments from our CI pipeline` 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.