Tags
Creators
Details
Licensed MIT
Published 4 months ago
Updated last week
All versions
1.2.2-neoforge-1.21.1
Release
Create: Factory Controller 1.2.2-neoforge-1.21.1last week 180
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Unavailable version
Changes
Features:
- Introduced redstone input/output functionalities for Arithmetic Tube.
- Added "Remote Controller Terminal", which can link up to 4 controllers and update controller settings remotely.
- Components support loop connection (self-connect) now.
- Number connection value update would play flash animation now.
- Allow Shift-Scroll to change connection type in connection mode.
- Added help button for Arithmetic Tube Screen.
- Added client config to adjust controller screen horizontal margin.
- Added transparent controller background.
- Added Enhanced controller component tooltip style (configurable).
Changes:
- Cut Amethyst is using stonecutter recipe now.
- Change connection button layout of arithmetic tube GUI.
- Downgrade neoforge version requirement to 227.
- Increase the maximum component cap to 8192 (but not recommended to use >1024 components).
- Added blueprint description to blueprint entry tooltip.
- Press ESC during connection/move mode in controller screen would exit the mode instead of close controller.
- Connection cannot be hover-selected when in component selection & blueprint placement state now.
Bugfixes:
- Fixed connection rendering may rarely render incorrect seam.
Create: Logistics Control
- Fluid product could carry filter label now.
- Fixed recipes which only consist of fluid ingredients cannot carry filter label.
- Added filter label to packages created by Create: Mobile Package and Create: Phantom's portable stock ticker.
Create: Higher Logistics Patch
- Fixed Create bug #10054
- Fixed Create bug #10634
Optional dependencies
Unavailable version
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:byvrDXed"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VR3MrvE2:byvrDXed"
}

