1.1.0
Compatibility
Changes
Eternal Furnace 1.1.0
Eternal Furnace is now available for Minecraft 26.2 on NeoForge.
This is a full port from the original Minecraft 1.20.1 Forge version, with several fixes and improvements to furnace behavior.
Changes
- Added support for Minecraft 26.2
- Migrated from Forge to NeoForge
- Updated to Java 25
- Reworked Furnace integration for Minecraft 26.2
- Hellfire now activates only when a valid smelting recipe can actually be processed
- Empty or invalid input no longer keeps the Furnace lit
- Existing normal fuel finishes burning before Hellfire takes over
- Fuel waiting in the fuel slot is no longer consumed while Hellfire is powering the Furnace
- Smelting progress is preserved proportionally when switching between normal fuel and Hellfire
- Improved support for recipes with custom cooking times
- Changed Hellfire Netherrack crafting: Flint and Steel now loses 1 durability instead of being consumed entirely
- Improved performance for ordinary Furnaces without Hellfire
- Updated block, item, recipe, and model resources for Minecraft 26.2
- Various internal cleanup and compatibility improvements
Note for players upgrading from 1.20.1
In Eternal Furnace 1.0.x for Forge 1.20.1, crafting Hellfire Netherrack consumes the Flint and Steel.
Starting with 1.1.0 for NeoForge 26.2, the Flint and Steel remains in the crafting grid and loses only 1 durability.
Testing
The 26.2 port was tested with 18 automated GameTests, dedicated-server startup, client startup, and a clean production build without Mixin injection errors.
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:aVzeqtyP:NXv2XZ8H"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aVzeqtyP:NXv2XZ8H"
}

