Tags
Creators
Details
2.0
Compatibility
Required content
Changes
Different from pre-release:
- Fix: removed a variable to allow multiple mods to save the same audio;
- saveAudio: return boolean to indicate whether audio was saved;
- Optimized audio reading and writing.
2.0 Changes
A big rework with lots of breaking changes, meaning mods that use versions from before 2.0 will no longer work with 2.0
For players
The commands have changed, and are now mostly for debugging and checking if things are working. Each audio is now represented by the UUID of the player it comes from, and an UUID specific to that audio.
Commands
To be able to play audios using /playVoice, you will now need to use /rememberAudios before saying whatever it is you want to play. After, you can use /saveAudio to save that audio to disk, meaning it will be saved after you leave the server, and next time, use /rememberAudios followed by /loadAudio so that it is added to the list of playable audios. Remember to use /rememberAudios after you're done, as leaving it on for too long may lead to running out of memory for remembering too many audios. You can also do /listAudios to see the audios that have been saved by mods: audios saved by voicechat_recording were likely saved through commands, not by any mod
/playVoice now has an extra argument to add audio effects to the audio, such as reverb, changing pitch, and a robotic voice.
Configs
There are now more configs to control how audios are saved to disk. If you wish to, you can change things like how long to wait after a mod requests to save an audio to actually write it to disk (to have a period for other mods to save other audios at the same time), how long a loaded audio stays loaded in the API's internal cache, etc... You shouldn't need to do this, as the defaults are (hopefully) acceptable, but the option is there.
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:NdyEsNQU:iCj9wGoC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NdyEsNQU:iCj9wGoC"
}

