Tags
Creators
Details
Licensed MIT
Published 2 months ago
Updated last month
All versions
1.1.0-neoforge-1.21.1
Release
Create: Factory Controller 1.1.0-neoforge-1.21.1last month 487
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
Features:
- Network can set custom name and item icon now.
- Added toast notification for order status change.
- Ignore data ingredient is now allowed for batch crafting & large crafting, but each slot cannot have different data item.
- Added "Custom Arrangement" mode in gauge; you can customize which item needs to be in which slot, and packager can only unpackage items to correct slot in target inventory.
- Added "Request Multiplier" feature in gauge: by set the maximum request multiplier value, gauge would attempt to combine ingredients from multiple requests into one request if stock allows.
- Added per gauge "Request Interval" setting, player could also visualize gauge request progress in RecipeSettingScreen.
- Added blueprint system to allow save components & connections to file.
- Added tooltip warning and controller indicator for unloaded stock links.
Changes:
- Maximum batch crafting multiplier is 64 now, regardless recipe output count.
- Gauge ingredient slot need to use Shift-Click to remove now.
Optimization:
- Dashboard sync use much less bandwidth data now.
Bugfixes:
- Fixed gauge connection flow animation won't play without made at least one request attempt.
- Fixed a compatibility issue which could cause connections to render incorrectly.
- Fixed gauge request timer do not get reset when redstone powered state changes.
- Fixed click suggested address in Recipe Settings screen could activate the count box input below.
- Fixed controller screen view could move by WASD keys when typing in JEI/EMI search box.
- Fixed drag view while having selected components would clear the selections.
- Fixed FluidLogistics compat does not properly work in 1.20 port.
Optional dependencies
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:VR3MrvE2:JNxh0oGB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VR3MrvE2:JNxh0oGB"
}



