Links
Tags
Creators
Details
1.3.0
Compatibility
Required content
Changes
Note: This build supports Create 6.0.6. For Create 6.0.7, please use version 1.4.0 or later.
Added
-
Restockers now have an Additional Items field that can be used to request additional items whenever the monitored inventory falls below its minimum stock level and a restock is triggered.
-
Train Network Monitor, a new CC: Tweaked peripheral that can be used to discover the state of all stations and associated postboxes on a rail network, and receive events when trains arrive at or depart from stations.
-
Cash Registers now support automatic currency conversion. This means that, as an example, if something costs a single Diamond and you only have a Diamond Block in your inventory, it will take the Diamond Block and give you eight Diamonds in change. This feature automatically discovers crafting 2x2 or 3x3 crafting recipes for converting items up, and also supports a data asset for adding other currencies, such as the cogs from Numismatics.
-
Chinese translation. Thanks to yision1 on GitHub!
-
An API is now exposed to CC: Tweaked computers for processing package addresses, available via
require("createadditionallogistics.package_addresses"). It can be used to convert Create's glob syntax to regular expressions, and to determine if two provided addresses match.
Changed
-
The Cash Register, when used as a CC: Tweaked peripheral, now emits a
saleevent when a sale happens. -
The Package Editor, when used as a CC: Tweaked peripheral, now emits a
package_readdressedevent when a package is processed. -
The address input field for Package Filters, Stock Keepers, Factory Gauges, and Redstone Requesters have had their length limit increased to 100 to match the change made to Frogport and Postboxes.
-
When changing the rotation of a Flexible Lazy Shaft, particles can now appear to show which direction the side is rotating.
Fixed
-
Encased Lazy Shafts causing an error when used in schematics due to a missing block property.
-
Encasing / unencasing Lazy Shafts causing a network update that can, in some circumstances, cause a lazy shaft to power itself.
-
Flexible Shafts not being placed with correct side configurations by schematics.
Changes Since 1.3.0-alpha.2
Added
-
Chinese translation. Thanks to yision1 on GitHub!
-
An API is exposed to CC: Tweaked computers for processing package addresses, available by requiring
createadditionallogistics.package_addresses. It can be used to convert Create's glob syntax into regular expressions, and to check if one address matches another.
Changed
-
When a Cash Register receives a payment, it will attempt to reconcile any contained currencies into the least items. For example, if a Cash Register contains 9 Diamonds, it will convert them to 1 Diamond Block.
-
The tool-tip when viewing a Cash Register's contents is now currency-aware.
-
The tool-tip when hovering over a Stock Keeper to complete a purchase is now currency-aware.
-
When changing the rotation of a Flexible Lazy Shaft, particles can now appear to show which direction the side is rotating.
-
The Train Network Monitor now has a custom appearance.
-
The Train Network Monitor now emits
train_arrivalandtrain_departureevents to connected computers.
Fixed
-
Clients being unable to connect to a server with a placed Train Network Monitor if they haven't first opened a singleplayer world and placed one.
-
The Train Network Monitor not having an accessible recipe.
-
Issue where events would not be emitted to all computers correctly in some situations.
-
Issue where a Restocker's input widget for Additional Stock would scroll incorrectly when the maximum stack size for the item being requested is 1.
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:CZaz7aje:SUP9Q546"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:CZaz7aje:SUP9Q546"
}

