Links
Tags
Creators
Details
10.2.3.463
Compatibility
Required content
Changes
b454a9a - Some further minor cleanup with switch statements and converting to expressions
f7cd147 - Synchronize transmitter shape cache to prevent random concurrent crashes #7499
df64d3c - Fix removed transmitters taking their share of the network away and fix redstone sensitivity on single length tubes releasing radiation
1bf5489 - Refactor and cleanup parts of the gradle buildscript to make more use of gradle's lazy configuration system
7f7b3b1 - Use a few gradle helper methods
6c514fa - Fix issues with launching into the world due to a capitalization issue
8164da7 - Update deps and bump min forge version to 40.1.27 and make use of forge's new pack specific format versions and switch those over to being declared in our gradle properties so that when vanilla changes pack format we only have to edit it in one place
e6427c3 - Adds comma to Hydrostatic Repulsor Unit description (#7501)
c73957e - Added a Dimensional Stabilizer (#7433)
Co-authored-by: Sara Freimer sara@freimer.com
38392ec - Make checking if a chemical is valid for a given validator easier
04a0530 - Bump min forge version to 40.1.36 to ensure forge's lighting pipeline is on by default
cc94a3e - Allow exclusive Modules to more accurately define what sorts of actions they are exclusive with (#7497)
6911c9b - Revert change to min forge version back to 40.1.27 due to the feature being reverted in a later forge build
b9bcd82 - Make factories persist sorting mode when broken #7505 and when upgraded via recipe. Also make fluid tanks persist their container edit mode
b0fea89 - Refactor backend of Jetpacks into an interface (#7493)
2b4f144 - Added fortune module (#7467)
57e3334 - Optimize image sizes
59159f1 - New Crowdin updates (#7495)
1e01609 - Bump version to 10.2.3
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:OFVYKsAk:N51JaiWT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:OFVYKsAk:N51JaiWT"
}

