All versions
Updated at 2023-07-30 07:35.
-Enhanced Progress class
-Added IFactoryDrawableType.DrawableStatic and IFactoryDrawableType.DrawableStaticProgress for using to store IFactoryDrawable relative position in screen
-Fixed extraction and insertion of fluid and energy in fabric using item stack
-Ported from 1.19.4-0.1.6.12
1.20.1-1.0+fabric
Release
Factory API [Fabric] 1.20.1-1.03 years ago 732
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Fabric
Quilt
Supported environments
Client and server
Required content
Changes
Release 1.20.1-1.0
Updated at 2023-07-30 07:35.
Changelog
Release 1.0
-Enhanced Progress class
-Added to IFactoryDrawableType.DrawableProgress drawProgress method with Progress as argument instead of percentage
-Removed methods addTanks and addProgresses from IFactoryStorage and IFactoryProcessableStorage
-Changed ICraftyEnergyStorage.EnergyTransaction static class to CraftyTransaction
-and much more minor changes...
Beta 0.1.9
-Added IFactoryDrawableType.DrawableStatic and IFactoryDrawableType.DrawableStaticProgress for using to store IFactoryDrawable relative position in screen
-Fixed ForgeItemFluidHandler.isFluidValid incorrectly overrided
-Inverted FactoryCapacityTiers.supportTier method to make more sense
-Fixed not being able to add non-vanilla fluids to SimpleFluidLoggedBlock.BLOCK_LOGGABLE_FLUIDS in Forge, because of the order of the registration event, changing its to a Supplier<Fluid>
-and much other minor changes and bug fixes...
Beta 0.1.8
-Fixed extraction and insertion of fluid and energy in fabric using item stack
-Fixed insert method of ItemCOntainerUtilImpl of fabric with value write and subtraction instead of only value write of inserted energy
Beta 0.1.7
-Ported from 1.19.4-0.1.6.12
Beta 0.1.6.1
-Ported from 1.19.3-0.1.6.1
Click here for complete changelog
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:nkTZHOLD:uumIQfwk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nkTZHOLD:uumIQfwk"
}


