Tags
Creators
Details
1.0.6
Compatibility
Changes
MUSIC EVENTS V1.0.6 CHANGELOG
Major overhaul to the Audios section of the GUI.
New audio parameters:
end_time: Stops the track and triggers the next event cycle when playback reaches this timestamp.
biomes: Restricts the audio to specific biomes or biome tags, independently of the event's resource_name. Works on any event type.
Biomes event no longer requires a resource_name:
When resource_name is omitted, the biomes event stays permanently active across all biomes and dimensions. Individual audio tracks can still be filtered per-biome using their own biomes parameter.
Example: audio that plays everywhere but is more likely in a specific biome:
[[events.biomes]]
event_name = "biomes"
priority = 1
# Plays in all biomes
[[audios."minecraft:sounds/music/game/hal1"]]
target_events = ["biomes"]
# Also plays in all biomes, but gets extra weight in plains
# (the unfiltered copy above ensures it still plays everywhere)
[[audios."minecraft:sounds/music/game/hal1"]]
weight = 200
biomes = ["minecraft:plains"]
target_events = ["biomes"]
# Plays in all biomes
[[audios."minecraft:sounds/music/game/hal2"]]
target_events = ["biomes"]
In plains, hal1 has a combined weight of 300 vs hal2's 100 (75% vs 25%). Everywhere else, both have equal weight (50/50).
=================================================================
require_all_events parameter behavior updated:
1: Locked Until: The track is part of the event's audio pool but will only enter rotation once all events listed under target_events are simultaneously active.
2: Takes Over: The track is not part of the event's standard pool. When all listed target_events become active, it takes over playback entirely and prevents any tracks that don't share the same require_all_events and target_events values from playing. (Previous behavior.)
Randomized time ranges for cooldown parameters:
cooldown_group_time and time_between_audio now support randomized ranges using the format M:SS-M:SS.
Examples: 0:00-10:00 (random between 0 and 10 minutes), 5:00-15:00 (random between 5 and 15 minutes).
Biome tag support: resource_name (biomes event) and the audio-level biomes parameter now accept biome tags in addition to biome IDs. Tags must be prefixed with # (e.g. #minecraft:is_forest).
New event parameters:
event_delay: How long the event's conditions must be continuously met before audio begins playing.
join_delay: On world join, rolls against a configurable chance. If triggered, prevents the event from activating for a random duration within a set range.
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:rIWYstjd:UXEfT94M"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rIWYstjd:UXEfT94M"
}

