Tags
Creators
Details
0.2.9-beta.12
Compatibility
Changes
Bedrock Simple Voice 0.2.9 Beta 12 ā Velocity
This release introduces the first public beta of Bedrock Simple Voice for Velocity, enabling seamless voice chat across Minecraft proxy networks.
New Features
Velocity Proxy Support
Added support for Velocity proxy networks.
Automatic voice connection handoff between compatible Bukkit-based backend servers.
Players can switch between servers without manually reconnecting their browser voice chat.
Voice connections automatically follow players when switching backend servers.
Supports backend servers even when no players are connected.
Connection & Reconnection
Improved voice session recovery when switching servers.
Saved browser sessions can reconnect automatically when players leave and rejoin the network within two minutes.
Improved handling of temporary connection interruptions.
Better connection status messages during server switches and reconnections.
Bedrock Integration
Bedrock players can open the voice chat menu using a Minecraft emote when Geyser is installed on Velocity.
The /voice command remains available as an alternative.
Security & Stability
Secure, authenticated communication between Velocity and backend servers.
Encrypted and signed backend handoff data.
Improved handling of backend connections and server switching.
Installation
Install the Velocity JAR on your Velocity proxy.
Install the Bedrock Simple Voice Bukkit plugin on each supported backend server.
Configure the shared network settings and secrets.
Restart your proxy and backend servers.
Important:
Requires the matching Bedrock Simple Voice backend plugin.
Automatic server handoff currently supports Bukkit-based backends (Paper, Purpur, Spigot, Folia).
Fabric, BungeeCord, and Waterfall are not supported by this Velocity integration.
Voice audio continues to use the backend and relay. Velocity only coordinates server switching.
Website & Documentation: https://voice.byterider.xyz
Note: This is the first public Velocity beta. Testing on a non-production network is recommended before deployment.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:29nX8CUQ:WPRl5qh8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:29nX8CUQ:WPRl5qh8"
}

