0.1.3.1-beta-neoforge
Compatibility
Changes
0.1.2 Fixed a compatibility issue with cables & machines form other mods. I have cleaned and consolidated some of the code to remove any duplication in the code to make it cleaner and easier on the worlds 0.1.3.1 Enhancements and New Features: Fuel Handling Per Slot: o Introduced a fuelPool property for shared fuel distribution across input slots. o Added a fuelTicksBySlot map to track remaining fuel ticks for individual input slots. o Implemented the allocateFuelTicks method to dynamically assign fuel ticks to active input slots based on cooking progress. Cooking Efficiency Improvements: o Input slots now only consume allocated fuel ticks when actively cooking. o Updated fuel consumption logic to share fuel more efficiently between input slots. Dynamic Efficiency Scaling: o Fuel burn durations now properly scale based on the machines tier, ensuring correct values are respected. Bug Fixes: Fixed Efficiency Scaling via Config: o Resolved an issue where tier-specific multipliers were not properly applied to fuel burn times. o Ensured that the updated configuration is fully respected during block entity initialization and cooking. Fuel Mismanagement Fixes: o Resolved issues where inputs could continue progressing without sufficient fuel ticks allocated. o Fixed edge cases where inactive slots improperly consumed remaining fuel ticks. Cooking Progress Reset Fix: o Adjusted logic to reset progress on empty or inactive slots without affecting the ongoing cooking process in other slots. Code Refactoring and Maintenance: Persistent State Updates: o Updated litTime and litDuration to maintain consistency with the new fuel handling logic. Resource Management Enhancements: o Updated cooking logic to avoid resetting progress unnecessarily for slots lacking fuel. 0.1.3.1 hot fix: Bug Fixes: fuel was being lost do to a miss use of the visuals on the machine but now is fixed!
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:So5bK0mE:EwO0yxfT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:So5bK0mE:EwO0yxfT"
}

