Links
Tags
Creators
Details
21.1.09-neoforge+1.21.1
Compatibility
Changes
Update incompatible mod list;
Fix custom payload aggregation disconnects #26 ;
- flush aggregation buffers synchronously and clear queued packets before sending to avoid recursive duplicate flushes
- keep aggregation encoding valid during splitter probes and fix compressed size/stat accounting
- release retained decode/probe buffers correctly
- fix namespace/path index lookup for custom payload ids
- respect maxPacketSize for discarded clientbound custom payloads
- correct Zstd context opt-out handling
The configuration file may become corrupted due to multithreaded operations;
To improve compatibility, DCC is now only enabled on dedicated servers;
Added support for ReplayMod's recording and playback features in both single-player and multiplayer games.
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:VdO1hTrG:zO9fve6s"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VdO1hTrG:zO9fve6s"
}

