BDS Server Pack Installation

Bedrock Voice Chat requires a server-side behavior pack to relay player positioning data to the BVC Server. Operators must install and configure this pack before any client can connect.

Installation

1. Download the latest .mcaddon from the Github Releases page (`.mcaddon') or from Curseforge/mcpedl
2. Extract the pack and copy the resource_packs and behavior_packs to your servers resource_packs / behavior_packs folders

Never upload the pack to your worlds/ folder — doing so can leak your BVC server URL and access token if the world is shared.

3. Create or edit config/default/variables.json:

{
    "bvc_access_token": "<MUST_MATCH_server.minecraft.access_token_FROM_config.hcl>",
    "bvc_server": "https://your.bvc-server.tld",
    "bvc_minimum_players": 1
}

Key	Description
bvc_access_token	Must match server.minecraft.access_token in your BVC server's config.hcl.
bvc_server	Public URL of your BVC server (no trailing slash, include port if non-443).
bvc_minimum_players	Sets the minimum number of players BVC must see to broadcast data. Defaults to 1

4. Update config/default/permissions.json to grant the modules the pack uses:

{
    "allowed_modules": [
        "@minecraft/server",
        "@minecraft/server-admin",
        "@minecraft/server-net",
        "@minecraft/server-ui"
    ]
}

5. Enable Beta APIs for your world.
6. Add the pack to your world's behavior pack list, and the resource pack to the resource pack list. Use the UUID for the variant you installed:

Variant	Behavior pack UUID	Use when
Full	6fb24263-357a-407c-aebe-681f50b2de50	Bedrock Dedicated Server — @minecraft/server-net is available.
No-Net	508a43ed-b95e-40cf-98eb-d78f2d72caa4	Realms, Aternos, and other hosts where @minecraft/server-net cannot be enabled.

Use the version from the manifest.json inside the pack you downloaded — it changes every release, so copying a version out of this page will eventually mismatch.

7. Start (or restart) BDS.

Troubleshooting

• Set content-log-console-output-enabled=true in server.properties. You should see [BVC] Connecting to: <host> on world load — if not, the pack isn't running or bvc_server is unset.
• Whitelist players in BVC before they try to log in (see the CLI guide).
• As a bandwidth-saving measure, BVC suppresses position relays until bvc_minimum_players are online. That defaults to 1, so solo testing works — but if you raised it, lower it back to 1 to test alone.
• GET /api/config should return JSON — confirms the BVC server is reachable.
• GET /api/position with header X-MC-Access-Token: <your_token> shows current player positions. An empty response means BDS isn't relaying.