All versions
2.3.0.1.0
Beta
Colossal Reactors 2.3.0.1.0last month 10
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
Bug fixes:
- Fixed a bug with gases where buckets were not recognised as containing liquids in certain contexts.
- Changed the output of the fissile fuel processing from spent nuclear waste to standard nuclear waste.
- The turbine port in the GUI no longer has a solid part.
- The reactor no longer consumes fuel when it shouldnât.
- Fixed an issue where the coolant was no longer functioning correctly.
- Fixed rendering of the area where builders will construct; it is now well synchronised between the interface and reality, and builders no longer hide each otherâs renders.
- Fixed incorrect counting in the builder simulator for turbines; it now calculates and displays the blades correctly.
- Dump button disabled for radioactive gases in ports
Tweaks:
- Default steam processing quantity increased from 250 to 1000 per blade
- Ports modified; see Features for details.
Features:
- Added more electromagnetic coils
- Reactor ports: added a button to clearly distinguish whether the port is for fuel/waste or coolant
- Reactor and turbine ports now adapt based on their consumption; this feature may not be applied immediately to the ports as it may require the reactor/turbine to be revalidated; clicking the reboot button in the control panel initiates a manual validation or you can wait for the periodic one.
- Ports containing radioactive gas now emit radiation upon rupture.
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:x18RjbsF:nvwacmeC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:x18RjbsF:nvwacmeC"
}



