Tags
Creators
Details
Licensed MIT
Published 2 months ago
Updated last month
All versions
0.2.1-beta
Beta
Create: Factory Controller 0.2.1-beta2 months ago 541
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
Features:
- Allow to type number to set gauge request amount
- Allow to change controller background texture (client setting)
- When Controller block breaks, it will now store the virtual board data in dropped item (configurable)
- Provide material list to Stock Keeper can now create production order for missing items (configurable)
- Controller GUI saves last view position & zoom, and restore when re-open controller GUI.
- Redstone Link is now an allowed component in Factory Controller
- Added Ignore Data setting to gauge:
- Once enabled, the gauge monitor all items for given type, ignore NBT data.
- The setting cannot be changed after output item been decided.
- When use "Ignore Data" item as ingredient of a gauge, the gauge could use any item as input (ignore data).
- Batch Crafting and Large Crafting Grid feature will be DISABLED when ingredient contains ignore data item.
- Warning: the feature does have performance cost, so only enable Ignore Data when needed.
Changes:
- Default background texture is plain_cardboard now
- Increase the hardness of Factory Controller block
- Add Summary to Factory Controller item
- Fluid System Compatibility: Bucket Unit can set request up to 1000B fluid now
- Deployer API is now a soft-dependency (but recommended)
- Updated gauge bulb texture
Bugfixes:
- Fixed orderable items are not show up in Stock Keeper immediately when open GUI
- Fixed network selector tooltip list items incorrectly when network count > 7
- Fixed Large Crafting may not work when missing dependency
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:4FIlusov"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VR3MrvE2:4FIlusov"
}



