All versions
0.3.2
Release
Forgotten Flames 0.3.23 months ago 15
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Client and server
Changes
Forgotten Flames 0.3.2
This update adds a full configuration system and expands campfires with new fuel and cooking mechanics.
Added config support
- Added a generated config file for Forgotten Flames.
- Most major features can now be enabled, disabled, or adjusted.
- Torch, lantern, smoldering, Forgotten Places, campfire fuel, and campfire cooking settings are now configurable.
- In singleplayer, the config is created automatically for the world.
- Server owners can adjust the config for multiplayer worlds.
Campfire fuel
- Campfires can now burn for a limited time when the fuel system is enabled.
- Players can add fuel by right-clicking a campfire with sticks, planks, logs, coal, charcoal, or coal blocks.
- Different fuel items add different burn times.
- Campfires go out when they run out of fuel.
- Soul campfires are infinite by default, making them a natural permanent fire option.
- Fuel values, limits, relighting behavior, and infinite campfires can be changed in the config.
Campfire cooking
- Food cooked on a campfire no longer instantly drops when ready.
- Cooked food stays on the campfire and can be taken with an empty hand.
- If left too long, cooked food becomes burnt.
- If left even longer, burnt food becomes charred remains.
- Added burnt versions of all vanilla campfire foods.
- Burnt food can still be eaten, but it may cause nausea, hunger, and poison.
- Charred remains are not edible and are mostly just the result of leaving food in the flames too long.
Notes
- Cooking and burning pause when the campfire goes out.
- Refueling and relighting the campfire lets cooking continue from where it stopped.
- Modded campfire recipes are not changed for now and should keep vanilla behavior.
- No GUI was added.
- No rain or weather behavior was added.
- The new systems do not depend on random tick speed.
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:izoNMft9:LYMBzM0D"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:izoNMft9:LYMBzM0D"
}

