1.21.x+1.5.0
Compatibility
Changes
In this version, the mod underwent a major rewrite. Resource replacement is now fully handled through a Mixin on the vanilla backend (NamespaceResourceManager). This removes the need for per-mod compatibility and, in theory, enables replacement support for all mods. It also completely fixes the FTB Quests bugs present in previous versions!
Fixes
- Adding an image in FTB Quests edit mode would cause the image path in the config file to become a hard-coded, localized path
- FTB Quest images without corresponding localized resources would appear as purple-and-black missing textures
Code
- Rewrote the replacement logic
- Removed the dedicated FTB Quests compatibility code
- Removed the Mixin plugin (Conditional Mixin)
- Optimized the GitHub Actions build workflow, significantly reducing run time
- Updated dependencies
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:oXy2xYgU:XYESM9yd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:oXy2xYgU:XYESM9yd"
}

