1.1.1
Compatibility
Changes
1.1.1:
Fixed (hopefully) vanilla music engine playing tracks at the same time as the mod's engine when coexistence mode is on.
1.1.0:
1.21.1 Neo Forge port:
Issues are expected, if you're experiencing them make sure to report bugs, or anything that seems to not be working correctly.
Added:
option to allow the vanilla music engine to play music. By default it's off.
Added:
a vanilla music cooldown slider in the Music & Sound options screens. This options will be useful for those who don't want to build a whole ambience soundtrack from scrath, and just want to setup combat, boss or context specific soundtracks. But this just gives room to the vanilla music engine, and it's not possible to control the engine itself for it to play music in a more sophisticated manner, like adding muffling effects, playing while paused, remembering track, resume from timestamp, etc.
Added:
min_hitbox_width parameter for the mobs event: it's the minimum bounding box width a mob must have to be able to trigger this event. Useful to leave out small mob variants like tiny slimes or magma cubes: min_hitbox_width = 0.53 < Filters out tiny slimes since their hitbox width is 52.
Added:
count: prefix to the Inventory event resource_name parameter. Let's you match based on how many of an item the player must carry for the event to trigger:
count:>=16|minecraft:arrow < 16 or more arrows anywhere in inventory
count:<=5|minecraft:bread < 5 or fewer bread
count:32-64|minecraft:dirt < between 32 and 64 dirt
count:20|minecraft:nether_star < exactly 20 nether stars
slot:mainhand|count:>=6|minecraft:egg < Needs to have 6 eggs in the mainhand for the event to go active.
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:wILS5LVr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rIWYstjd:wILS5LVr"
}

