Tags
Creators
Details
1.0.5
Compatibility
Changes
Fixes replay startup on older NeoForge 21.1 builds, including 21.1.172, where the later AttachmentSync login call does not exist. The attachment hook is now conditional, and replay registry restoration supports both RegistryManager API signatures used across the NeoForge 21.1 lifecycle. Clean builds were verified against NeoForge 21.1.172 and 21.1.248 with the Flashback 0.39.7 compile target.
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:QaOcZcLU:RQHEFDwa"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QaOcZcLU:RQHEFDwa"
}

