Tags
Creators
Details
All versions
1.0.0
Release
CobbleAPI 1.0.03 months ago 47
Compatibility
Minecraft: Java Edition
1.21.11
Platform
NeoForge
Supported environments
Client and server
Changes
🔄 Compatibility Extension — CobbleAPI
**Takeaway: Added full compatibility for several NeoForge and Fabric versions, with no gameplay changes. **
🧱 NeoForge Compatibility
- Extended support from 1.21.4 to 1.21.11
- Internal adjustments to ensure stability across the entire 1.21.x branch
- Module synchronization to prevent cross-version crashes
🧵 Fabric Compatibility
Added support for:
- 1.21.4 Fabric
- 1.21.8 Fabric
- 1.21.1 Fabric
- 1.21.11 Fabric Updated mappings and adapted Fabric hooks Improved handling of multiple loaders
⚙️ Technical Adjustments
- Harmonized dependencies across different platforms
- Fixed minor conflicts related to cross-version environments
- Optimized loading to reduce silent errors
🐛 Minor Fixes
- Fixed some Fabric boot warnings
- Stabilized dynamic modules on NeoForge
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:LbTPV4IK:1SJaV17v"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LbTPV4IK:1SJaV17v"
}

