All versions
2.3.5
Release
Murmora 2.3.52 months ago 14
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
📦 Murmora - v2.3.5
English
⚡ Performance & Optimization
- Smart Resource Caching: Players will no longer experience resource pack reloading or screen freezing when joining the server. Sound files are now synchronized silently in the background and stored in local cache.
- On-Demand Pack Reloading: Resource pack reloads (
minecraft.reloadResourcePacks()) are now strictly reserved for administrative commands (e.g.,/murmora reloador/murmora custom reload). - Non-Destructive Sync: The client no longer wipes the resource pack folder upon connecting, preventing unnecessary I/O overhead and disk writes.
🛠️ Fixes & Refinements
- Improved network packet handling during custom sound synchronization.
- Updated
FinishCustomSoundSyncPacketto support conditional resource pack reloads.
Español
⚡ Rendimiento y Optimización
- Caché Inteligente de Recursos: Los jugadores ya no experimentarán recargas del paquete de recursos ni pantallas congeladas al entrar al servidor. Los archivos de sonido ahora se sincronizan en segundo plano de manera silenciosa y se guardan en la caché local.
- Recarga de Recursos Bajo Demanda: Las recargas pesadas del resource pack (
minecraft.reloadResourcePacks()) ahora se reservan exclusivamente para comandos administrativos (ej./murmora reloado/murmora custom reload). - Sincronización No Destructiva: El cliente ya no borra la carpeta del paquete de recursos al conectar, reduciendo el impacto en el disco y tiempos de carga.
🛠️ Correcciones y Mejoras
- Manejo optimizado de paquetes de red durante la sincronización de sonidos personalizados.
- Actualizado
FinishCustomSoundSyncPacketpara permitir recargas condicionales del resource pack.
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:X96ynsfi:8STFPXzf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:X96ynsfi:8STFPXzf"
}

