All versions
0.1.2+runtime
Release
cyanspeech 0.1.2 (runtime companion)2 months ago 447
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
Platforms
Fabric
NeoForge
Quilt
Supported environments
Client-side
Changes
cyanspeech 0.1.2
- cyancore:
0.1.3 - loader:
runtime - Minecraft:
multi-loader - artifact:
cyanspeech-runtime-0.1.2-0.1.3.jar
cyanspeech Features
- Speak text from client commands with
/cyanspeech say <text>or by passing text directly to/cyanspeech <text>. - Enable, disable, and select a catalog voice with
/cyanspeech enable,/cyanspeech disable, and/cyanspeech voice <voice>. - Render speech through the
cyanspeech-runtimecompanion jar, which provides Piper JNI and the LibriTTS-R voice model in the Minecraft client. - Play rendered speech through Simple Voice Chat when available, with optional local desktop fallback.
- Keep the main cyanspeech loader jars small by shipping the heavy model/native runtime as a separate loader-neutral companion mod jar.
- Verify and repair the extracted local model cache from the companion jar when the cache is missing or corrupted.
- Optionally speak every outgoing non-command chat message with
/cyanspeech settings chat on. - Persist voice, starred voice colors, Simple Voice Chat routing, local playback, chat, keybind, and voice effect settings to
cyanspeech/settings.jsonin the client config directory. - Open the Voice settings screen on Fabric 1.21.11, Fabric 26.1.2, Quilt 1.21.11, and NeoForge 26.1.2 for collapsible sections, a license grid, a sortable starred voice selector, playback toggles, selected-voice preview phrases, and tiled effect sliders.
- Include ModMenu in real-client dev runs for the supported loader adapters.
- Keep product logic independent of loader APIs so the same speech core ships across Fabric, Quilt, NeoForge, and JavaAgent targets.
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:bxKeisRX:HjCUPx3n"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bxKeisRX:HjCUPx3n"
}

