1.0.0-beta
Compatibility
Required content
Changes
v1.0.0-beta.1 — Initial release
First beta. Adds a Verity JE Extra tab to Verity's own config screen with three optional overrides — each behind its own toggle, off by default.
- Chat — point Verity's AI at any OpenAI-compatible endpoint (OpenRouter, a local server, etc.) instead of the built-in providers
- Cloud Voice — give Verity's cloud text-to-speech its own endpoint, key, model and voice, separate from chat
- Offline Voice — swap Verity's built-in CPU voice for your own Piper model, fully offline, no key needed
Requires: Verity JE 5.0+, YACL 3.6+ (already required by Verity, so nothing extra to grab)
Known limitations:
- Voice input (speech-to-text) isn't covered — still uses Verity's own settings
- Cloud Voice only kicks in when Verity's Native/Local TTS options are off
- Set Verity's own AI Provider to GROQ if you want Cloud Voice working — it refuses to run on OpenRouter
Beta release — please report anything odd!
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:wjhKNEct:ga4E7VMX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wjhKNEct:ga4E7VMX"
}

