Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated 3 months ago
All versions
0.0.7-C.5.1-1.20.1
Beta
Create Metallurgy 0.0.7-C.5.1-1.20.1last year 5,084
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Changes
Changes
- Update langs files (Chinese, Spanish, German).
- Added missing Gear/Rod mold recipes.
- Fixed recipes registrations warnings spam in console.
- Fixed Casting recipes goes away when unloading while processing.
- Change Wolframite tags to Tungsten tags. (Not display name changed).
- Added Dutch translation (By BramVerkuijlen).
- Fixed Alloying recipe won't start when multiple item input or any item ouput.
- Foundry recipes can now process continuously.
- Fixed Casting Recipes produces wrong output.
- Recipes can now be used in Assembly recipes (Grinding, ).
- Fixed melting netherite ingot wrong heat condition.
- Added Industrial Crucible & Foundry Unit (Texture made by Janko).
- Added Obdurium Alloy.
- Update Forge version (43.2.21 to 43.2.4 for 1.19.2) & (47.2.6 to 47.4.0 for 1.20.1)
- Molten Fluids Buckets from compatibility no longer appear when no mod adds the corresponding metal.
- Removed Thermometer gauge on Foundry Lid.
- Update wolframite tags name to tungsten (Forge:dusts/wolframite -> Forge:dusts/tungsten).
- Molten Fluids have lava like effect (Lava pops sounds / particles and fire).
- Overhaul existing recipes for better compatibility.
- Reduced Foundry Melting sound volume and rate.
- Fixed Belt Grinder throwing items off the belt when full.
- Ajusted Foundry Basin texture.
- Fixed Close/Open sound inverted.
- Fixed Foundry Basin small spout can fill Fluid tank directly.
- Changed Creative Tab icon
- No more tadpole burning recipes :)
- Added Croatian localization (by Janko)
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:Soft45xC:DuZgAlA5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Soft45xC:DuZgAlA5"
}



