Links
Tags
Creators
Details
0.3.2
Compatibility
Required content
Changes
Fix the 0.3.0 export bug + re-enable H8
0.3.0's H8 Mixin had an invalid @At("THROW") annotation which caused the entire ExportJobProgressMixin to fail to apply with InvalidInjectionException. The error was at Mixin parse time, before our code could even run, and broke the export pipeline.
This release:
- Removes the invalid
@At("THROW")and uses@At("TAIL")for cleanup (covers normal returns; if export throws, the screen stays — minor cosmetic, will close on next user interaction). - Sets
setScreen()synchronously instead of viamc.execute()to avoid timing issues with Flashback's internalsetScreen(null)calls. - Re-enables
showExportProgressOverlayby default.
The overlay should now display correctly during exports without breaking them. If you still hit issues, toggle showExportProgressOverlay = false in config/flashbackturbo.json to revert to vanilla behavior.
Apologies again for the 0.3.0 regression.
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:6o9zaNB9:tDMzj7b4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6o9zaNB9:tDMzj7b4"
}

