All versions
2.3.0.0.0
Beta
Colossal Reactors 2.3.0.0.02 months ago 16
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Turbine Update
Some features, such as the turbine, are working properly but may require some tweaks; please let me know..
Removed mandatory dependency of Iskandert's Utilities
Tweaks:
- Power Port reduced to an integer value buffer & transmission, but a High Conductivity Port has been added.
- Reduced the default capacity of Rods from 10,000 to 1,000; it was really too large.
- Expanded and improved some datpacks.
Integrations:
- Added various coolants, heat sinks and fuels to the reactor.
- Changed Ender Goo tag to allow for greater compatibility from c:ender to c:ender_molten.
- Added integration for ores with Mekansim
Features:
- Added Turbine and related components.
- High Conductivity Port, Long Value Buffer & Transmission with direct integration with Draconic Evolution.
- The power factor of fuels is now displayed in JEI.
- Added Chromium Ore
Balancing:
- Made ores less rare
Bug Fixes:
- GuideME was not loading.
- Redstone Heating Coils & Melter buttons now have the back function on the right button.
- Reactor Builder: no longer shows 100% complete if it lacks sufficient liquids; it now waits for liquids.
- Fixed some text that was too long and overflowed the JEI GUI.
- Fixed rendering misalignment by a few pixels for liquid slots and items in some GUIs.
- Fixed compressed rendering at the bottom for liquids.
- Fixed an issue where GuideME would not load in certain contexts.
- Fixed failed loading of startup datapacks.
- Added automatic exclusion of invalid entries in datapacks.
- Fixed minor bugs in some GUIs.
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:YRQVw41b"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:x18RjbsF:YRQVw41b"
}

