2.2.0-beta.1
Compatibility
Changes
Version 2.2.0-beta.1
This is a beta release. The config system has been rebuilt, so please back up your voicecommand_words.txt before updating if you have a custom setup. Your existing config should be migrated automatically the first time you load this version, but as with any beta there may be rough edges. Please report anything that breaks in my discord.
New Features
- Brand new in game Mob Browser config screen. Open it from the Config button on the Mods screen. It lists every living mob in the game, both vanilla and modded, discovered automatically.
- Mob names are detected automatically for any mod. You no longer need to know a modded mob's name. The browser reads it straight from the game.
- Each mob shows its full summon style id (for example the_wonderland:eyeless or minecraft:creeper) so you always know exactly what you are assigning words to.
- Assign trigger words to any mob by typign them into that mob's word box. Separate words with commas. A mob spawns when any of its assigned words is said
- Search bar to find mobs by name, mod, or assigned word.
- Filter popup to narrow the list by base Minecraft mobs, modded mobs, enabled mobs, or disabled mobs.
- Toggle all button to enable or disable every current mob at once.
- Settings popup for show swear count, show streak, cooldown, and lottery frequency, all adjustable in game.
- Per mob enable and disable. Disabled mobs keep their words but never spawn until enabled.
Changes
- The config is now organized per mob instead of per word. Each mob has its own set of trigger words, an enabled state, and on top setting.
- The config file formate changed to support the new system. Old config files are migrated automatically on first load.
- The word list is controlled by the server. On multiplater servers the server config is the shared list for everyone.
Bug Fixes
- Fixed the config menu freezing when filtering to enabled mobs while everything was disabled
- Fixed long mob ids being cut off in the config list
- Fixed adding and removing entries not saving correctly in the older config menu
Known Notes
- This is a beta. If you find a bug, please report it in my discord so it can be fixed before the stable 2.2.0 release
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:2nBsiZ0z:conwUeCC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2nBsiZ0z:conwUeCC"
}

