Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 4 years ago
Updated 11 months ago
All versions
0.4.6
Alpha
The Impossible Library11 months ago 609
Compatibility
Minecraft: Java Edition
1.21.1
1.20.6
1.20.4
1.20.1
1.19.4
1.19.2
1.18.2
1.16.5
1.12.2
Platforms
Fabric
Forge
NeoForge
Quilt
Supported environments
Client and server
Changes
commit history since 0.4.5 because I forgot to keep track of everything
- Lots of backend rewrites and refactoring:
- Java 25 (and Java 24 with -XX:+UseCompactObjectHeaders) should be able to load now
- All internal BurningWave calls are now routed through
Hacks - Consolidated and removed code smells from all
Wrappedimplementations - [Forge & Neoforge] Rewrote and standardized mod loading (this also fixes 1.20.4 & 1.20.6 Forge not being able to load)
- [Forge & Neoforge] Reorganized module layer hacks for proper (WIP) dev environment support
- [1.16.5+] Consolidated & standardized network implementations (this also fixes serverside triggers for Music Triggers not working in 1.20.4+ Forge & NeoForge)
- [1.20.6+ Neoforge] Replaced poorly implemented string-based early loading file path scanning that caused a crash with Linux
- Fixed the TOML parser ignoring leading '-' when parsing numbers (leading to negative numbers being parsed as positive)
- Partially (or maybe fully?) fixed a JVM shutdown crash caused by the BurningWave resource releaser
- Fixed mouse hover calculations for radial & scrollable GUI widgets
- [1.12.2] Fixed rendering compatibility issues with nothirium
- [1.16.5+] Implemented dimension-specific respawn position checks for players (Music Triggers home trigger)
- [1.19.2 - 1.20.1 Forge] Fixed CustomSuggester not being properly registered for the WrappedCommand implementations (Music Triggers decoder exception)
- [1.21.1 Forge] Added a fallback for the Minecraft version not being parsed on servers
Supplementary resources
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:ZyFWSztU:B3agwwjr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZyFWSztU:B3agwwjr"
}

