Links
Tags
Creators
Details
Licensed MIT
Published 4 months ago
Updated 3 weeks ago
All versions
NeoForge-1.21.1-2.4.17
Release
NeoForge-1.21.1-2.4.173 weeks ago 2,577
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client-side
Changes
Fixed
- The "kicked right after joining" disconnect is fixed (all platforms): a system chat message sent by a server or proxy plugin at join time could arrive before the client's local player exists, and previous versions dereferenced it without a null check — NeoForge treats that as a fatal packet error and disconnects. Such messages now show up as ordinary gray system lines and the connection survives. The bug is racy and only fired when a message happened to land in that window (the field report was a proxy plugin's
Sent server list), which is why it did not reproduce every time. 2.4.14 and 2.4.16 are both affected.
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:onBSJreQ:pQFJf3Q1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:onBSJreQ:pQFJf3Q1"
}

