Links
Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated 6 months ago
All versions
0.5+forge-mc1.20.1
Beta
Create: Blazing Hot v0.5 for Forge 1.20.12 years ago 254
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Forge
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
Pre-release version. Back up your worlds before updating.
Added:
- ⚒ Forge support
- Regular mixing recipe for melting Blaze Gold Rods
- Configuration options for toggling effect tooltips for custom food
- Toggleable effect tooltips for vanilla Golden Apples
- New configuration options for blaze mixing
Changed:
- Reduced melting time with Blaze Mixer
- Reduces fuel costs for melting with Blaze Mixer
- Extended processing time of Molten Blaze Gold mixing and blaze mixing recipe
- Melting with Mechanical Mixer is now 3 times longer compared to Blaze Mixer (previously 5)
- Renamed
fuelproperty in Blaze Mixing recipes toblazinghot:fuel - Nether Sprouts can now be used when crafting Nether Compound
- Updated textures for Blaze Gold Ingot, Nugget, Sheet and Block
- Modern Lamp crafting recipe now returns 2 lamps instead of 1
- Blaze Arrow crafting recipe now returns 4 arrows instead of 2
- Reduced the amount of Nether Essence required to obtain Molten Blaze Gold from 4 to 2
- Reduced the amount of fluid when filling Metal Carrots and Apples from 8 nuggets or ingots to 6
- Adjusted sequenced assembly recipes for Enchanted Metal Apples:
- Increased the amount of loops from 4 to 6
- Reduced amount of fluid required per loop from 9 ingots to 6
Fixed:
- Blaze mixing recipes now consume the correct amount of fuel
- Blaze mixing recipes' speed is no longer affected by the fuel
- This only applies to recipes exclusive to the Blaze Mixer
- Melting time no longer caps at 512 ticks (25.6 seconds)
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:LmT6oZrX:kO0bQP2t"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LmT6oZrX:kO0bQP2t"
}

