Tags
Creators
Details
2.0.2
Compatibility
Required content
Changes
Modrinth Changelog :
Reactor:
- Reactor outputs now only spin while the reactor is assembled, and stop properly when it is disassembled. Before, they could keep turning at an old, outdated speed.
- Fixed reactor outputs adding their stress capacity twice to the network after reloading a world.
- Fixed a possible crash when updating the reactor outputs.
- A Reactor Blueprint without any rods in it can no longer be placed in the Reactor Controller.
- You can now fill Reactor Fluid Inputs by right-clicking them with a fluid container in Survival. This used to work only in Creative.
Reactor Display & Interface:
- When a reactor isn't assembled or can't be found, Display Links showing the reactor summary now say "No value for this Reactor, the reactor structure is not valid" instead of showing old values.
- The Reactor Blueprint tooltip now shows your own key bindings instead of always saying "Shift + Right Click", and a typo in it is fixed.
Sound & Ambience:
- New sounds for reactor activation, running and shut-off, and for motor assembly and disassembly.
Radiation & Anti-Radiation Armor:
- Fixed display problems with the Anti-Radiation Armor model. Each armor piece now has its own model.
- Air from an Encased Fan doing enriched processing now shows radiation particles instead of water particles.
Technical / Codebase:
- The project is now licensed under GPL-3.0 instead of MIT.
- Regenerated the language files. The upside-down English translation also gets a text that was missing.
- Added internal tools for writing release notes.
If you want to help us translate to other languages: https://crowdin.com/project/createnuclear
Some translations were verified/completed using AI, if you find any issues let us know on our Discord!
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:z611fdf7:w5YuGu86"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:z611fdf7:w5YuGu86"
}

