Links
Tags
Creators
Details
1.0.3
Compatibility
Required content
Changes
๐ Version 1.0.3 โ The Great 1.21.11 Rewrite!
Extra Concrete has been completely rewritten and optimized from scratch! In this monumental update, we have placed the entire mod structure on a modern, future-proof foundation. It is now fully compatible with Minecraft 1.21.11, runs smoother than ever on both Fabric and NeoForge, and supports many new languages! ๐ ๏ธ Complete Code Rewrite
Extremely Optimized: The codebase has been completely streamlined. Blocks and items now register dynamically and lightning-fast in the background, noticeably reducing game loading times.
Multi-Loader Architecture: Full support for both Fabric and NeoForge from a single, highly optimized codebase.
Clean Code: No more unused dependencies or outdated methods. The mod is now as lean and resource-efficient as possible.
๐ Bugfixes & Minecraft 1.21.11 Adjustments
Since Minecraft 1.21.11 fundamentally changed the resource and registration system, we have permanently fixed the following issues:
Crash Fix (NPE): The dreaded Block id not set error during game startup has been completely resolved.
1.21.11 Item Model Fix: All items now utilize the new, data-driven item definition system. No more purple-and-black missing textures in your inventory!
Translation Fix: Corrected broken item translation keys in the inventoryโitems are now named exactly as they should be in every language.
Recipe Correction: All recipes have been rewritten to the latest 1.21.11 JSON syntax to eliminate errors in both server and client logs.
๐ Now in 8 Languages!
We have massively expanded our language support! The mod is now fully playable in the following languages:
๐ฉ๐ช German
๐บ๐ธ English
๐ช๐ธ Spanish
๐ซ๐ท French
๐ฎ๐น Italian
๐ณ๐ฑ Dutch
๐ต๐ฑ Polish
๐ง๐ท Brazilian Portuguese
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:gzCTQ7oy:6cbnoCnn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gzCTQ7oy:6cbnoCnn"
}

