
Plasmo Voice Messages
Adds voice messages to the Minecraft chat with Plasmo Voice integration. Includes a custom chat widget, recording UI, global/local/private message types, permissions,chunked audio transfer. Requires both client mod and server plugin.
1.2.0
Compatibility
Required content
Changes
1.2.0 Changelog
New Features
- Recording indicator — a blinking REC icon appears on screen when recording continues with chat closed, so you never lose track of an active recording
- Nickname hover tooltip — hovering over a truncated player name in chat now shows the full nickname
- Server reload command — admins can now use
/voicemessages reloadto reload the config without restarting the server; updated settings are automatically sent to all connected players - Recording indicator toggle — new option in mod settings to enable or disable the on-screen REC indicator
Improvements
- Voice message preview widget now persists when chat is closed — reopen chat and your recording is still there, ready to send
- Recording that finishes while chat is closed (e.g. reaching the time limit) now correctly transitions to preview mode when chat is reopened
- Maximum recording duration is now synced from the server per player, respecting permission-based limits instead of a hardcoded 60 seconds
- Server configuration is now properly reset when disconnecting, preventing stale settings from carrying over to another server
- Audio playback and active recordings are now cleanly stopped on disconnect
Bug Fixes
- Fixed a bug where closing chat during recording would leave no visual feedback
- Fixed preview widget losing all recorded data when chat was closed and reopened
- Fixed a potential freeze caused by blocking the main thread during audio playback
- Fixed duplicate client command registration
Optional dependencies
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:Q1WO0zwt:IOHTOMqB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Q1WO0zwt:IOHTOMqB"
}
