Tags
Creators
Details
26.1.101
Compatibility
Changes
ORES CORE v26.1.101 - Precision Hosting Update
A precision update for Ores Core! Version v26.1.101 focuses on visual immersion and configuration polishing, ensuring ores perfectly match their environment.
๐ NEW: Host Block Parity (Facing & Translucency)
Ores now achieve full visual and physical parity with their host terrain:
- Directionality (Facing): Ores generated in oriented host blocks now inherit the
FACINGproperty. No more visual clipping: the ore follows the block's rotation. - Translucency Support: If a host block is semi-transparent or lets light through, the generated ore will now match that property for seamless integration.
โ๏ธ UPDATED: In-Game Configuration
Modernized the configuration system for the latest Minecraft standards.
- MC 26.1 Support: Internal configuration logic has been updated to the new Minecraft 26.1 method for better stability.
- UI Refinement: Improved the host block management screen with smarter real-time property detection.
โก Mod Menu Integration
Simplified access for Fabric players.
- Official Support: Ores Core is now fully integrated with Mod Menu.
- Quick Access: Access the entire configuration suite directly from your mod list.
๐ Core Features (Reminders)
- 90+ Materials Supported: From common Copper and Tin to exotic gems and chemicals.
- 5000+ Combinations: Procedural items, blocks, and variants for every registered material.
- Mekanism & Create Native Support: Automated processing chains (Dissolution, Milling, Crushing).
- Dynamic Asset Generation: Textures and models are created in memory, keeping the mod file size minimal.
Developed with โค๏ธ by __mathieu
Optional dependencies
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:qGOAsgoc:dOIDrUps"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qGOAsgoc:dOIDrUps"
}

