Tags
Creators
Details
0.2.9-beta.12
Compatibility
Changes
Bedrock Simple Voice 0.2.9 Beta 12
This update introduces Velocity support, improved voice connection recovery, and several stability improvements for Bedrock and Java players.
New Features
Velocity Support
- Added optional Velocity proxy support.
- Voice chat now supports automatic handoff between compatible Bukkit-based backend servers.
- Players can switch between backend servers without manually creating a new voice connection.
- Improved reconnection when leaving and rejoining a Minecraft network within two minutes.
- Added support for backend servers without connected players.
- Secure communication between Velocity and backend servers.
Bedrock Improvements
- Bedrock players can now open the voice menu using a Minecraft emote when Geyser is installed on Velocity.
- The
/voicecommand remains available. - Improved browser connection status messages when switching servers or reconnecting.
Bug Fixes & Stability
- Fixed microphone permission requests getting stuck in certain situations.
- Improved recovery of saved browser voice sessions.
- Fixed outdated sessions causing connection problems.
- Improved cleanup of audio resources after failed connections.
- Improved relay connection stability and error handling.
- Improved automatic reconnection after temporary connection interruptions.
Server Improvements
- Added in-game update notifications for server administrators with the required permissions.
- Improved plugin data organization. Internal files are now stored in the
BedrockSimpleVoice/data/directory. - Existing plugin data is automatically migrated.
config.ymlandmessages.ymlremain in their original location.
Installation & Compatibility
Available platforms:
- Paper / Purpur / Spigot / Folia
- Velocity (optional proxy plugin)
For Velocity networks, install the Velocity plugin on your proxy and the Bukkit plugin on each supported backend.
Note: This is still a beta release. Back up your configuration before updating.
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:i50KuqaA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:29nX8CUQ:i50KuqaA"
}

