Links
Tags
Creators
Details
3.12.4
Compatibility
Required content
Changes
Continuum Construct 26.1.2-3.12.4
This release keeps other mods' tank colors, brings thrown tools back, heats a smeltery from a second fuel tank, stops the part builder from freezing when a chest is beside it, and no longer crashes when tool damage math goes below zero.
Fixes
- Tanks tint from the fluid model, so other mods keep their color (#27).
- Returning brings a thrown tool back, and a higher level is visibly faster (#28).
- A smeltery keeps heating from a second fuel tank when the first is empty. Liquid fuel recipes are no longer wiped by the shared fallback id during world load.
- Shift-clicking the part builder result no longer freezes when a chest is beside it, and the client no longer shows a ghost stack after the material runs out (#29).
- Being hit no longer crashes the server when modifier or armor math would set damage below zero. NeoForge 26.1.2.112 rejects a negative amount, so incoming and final damage are clamped to zero.
Compatibility
- Requires Continuum Core 1.12.1.
- Built against Minecraft 26.1.2 / NeoForge 26.1.2.112.
Continuum Construct 26.1.2-3.12.3
This release keeps players moving in custom fluids, lets channels pour into tanks and casting tables, and shows fluid particles.
Fixes
- Joining a world with a tool table no longer crashes. Inventory updates use the world registry, so enchantments on stored items can be written. Requires the Continuum Core build that includes that registry lookup; the Core version number stays 1.12.0.
- Channels pour into tanks and casting tables as well as other channels.
- Molten fluids show surface, drip, faucet, and step-in particles, and standing in a full source block no longer freezes movement.
- Area-harvest tools draw the break crack on the extra blocks, not only the block in the crosshair.
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:e0tUZE5Y:HvoiaQPX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:e0tUZE5Y:HvoiaQPX"
}

