Links
Tags
Creators
Details
Licensed LGPL-3.0-only
Published 3 months ago
Updated 3 months ago
All versions
0.6.0
Release
Applied Smelting 0.6.03 months ago 39
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client and server
Changes
Applied Smelting 0.6.0
Added
- Added survival crafting recipes for every tier of the ME Blast Furnace, ME Smoker, and ME Crucible.
- Added matching recipe-book advancements.
- Added automated tests for lava consumption and output-target calculations.
Fixed
- Fixed Fuel Efficiency Cards over-consuming lava at fractional rates.
- Fixed completed jobs requiring additional fuel, lava, or AE power before inserting their output.
- Fixed completed jobs being cancelled when their queue selection changed.
- Fixed partially accepted outputs potentially being duplicated.
- Fixed active processing jobs briefly being omitted from output-target calculations after reloading.
- Added validation for invalid recipe amounts and processing times.
- Made output-target calculations overflow-safe.
Performance
- Machines now cache active recipe results instead of repeating recipe lookups every tick.
- Active machines checkpoint progress every 20 ticks instead of marking their chunk for saving every tick.
- Shared queue capacity is now cached until machines or upgrade cards change.
- Terminal statistics are aggregated once per machine family each server tick and shared between open terminals.
Internal Improvements
- Processing state is now persisted and preserved more reliably across saves and tier upgrades.
- Centralised the in-place upgrade workflow across all four machine families.
- Reduced duplicated machine code and improved future upgrade compatibility.
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:WF9YE7g7:mO3iDsvE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WF9YE7g7:mO3iDsvE"
}

