Tags
Creators
Details
1.21.x-1.1.2
Compatibility
Changes
[1.1.2] - 2025-12-23
🔒 Security Release
This release addresses critical security vulnerabilities in transitive dependencies and expands version compatibility.
Security
- Updated Netty to 4.1.125.Final - Fixes CVE-2025-58057 (BrotliDecoder DoS vulnerability, CVSS 7.5)
- Previous: 4.1.118.Final (CVE-2025-24970)
- Impact: Prevents denial of service attacks via crafted compressed input
- Updated Log4j Core to 2.25.3 - Fixes CVE-2025-68161 (TLS hostname verification, CVSS 5.4)
- New dependency forcing for both log4j-core and log4j-api
- Impact: Prevents man-in-the-middle attacks on log traffic
- Updated LZ4-Java to 1.10.1 - Fixes CVE-2025-66566 (buffer disclosure vulnerability, CVSS 7.5)
- Migrated from org.lz4:lz4-java to at.yawk.lz4:lz4-java (new official group ID)
- Previous: 1.8.0
- Impact: Prevents sensitive data disclosure via output buffer reuse
- Maintained Commons Lang3 3.18.0 - Continues protection against CVE-2025-48924 (CVSS 5.3)
Changed
- Version scheme updated from 1.21.1-1.1.1 to 1.21.x-1.1.2
- Reflects compatibility with all Minecraft 1.21.x versions (1.21.1, 1.21.2, ... 1.21.11+)
- Dependency range already configured as [1.21.1,) in neoforge.mods.toml
- Documentation updates:
- Updated README.md to clarify Minecraft 1.21.1+ compatibility
- Updated build output JAR name to LimitedSpectator-1.21.x-1.1.2.jar
Technical
- All dependency version forcing configured via build.gradle resolutionStrategy
- Build tested successfully with clean build (no warnings or errors)
- JAR output:
build/libs/LimitedSpectator-1.21.x-1.1.2.jar - Gradle configuration remains at 8.10 with NeoGradle 7.0.167
Migration Notes
Users on any 1.21.x Minecraft version can safely upgrade to this release. No configuration changes required. All existing configs from 1.1.1 remain fully compatible.
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:1h1Nfg72:1fqF7fiV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1h1Nfg72:1fqF7fiV"
}

