Tags
Creators
Details
Licensed MIT
Published last month
Updated last week
All versions
1.0.14
Release
Flashback Neoforge Fixed 1.0.143 weeks ago 736
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client-side
Changes
Fixes:
- Preserve recorded modded custom-payload bytes exactly until the viewing client decodes them.
- Fix Cobblemon replay disconnects such as
Invalid species: cobblemon:totodileafter a lazyspecies_syncpacket was re-encoded as an empty registry. - Keep NeoForge advanced entity spawn handling and legacy replay safety checks intact.
- Apply the lossless forwarding path generically so other lazy or one-shot mod packet codecs do not suffer the same decode/re-encode corruption.
- Support affected existing recordings whose payload bytes were captured by earlier Flashback NeoForge Fixed releases.
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:9XdDHJvq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QaOcZcLU:9XdDHJvq"
}

