Tags
Creators
Details
Licensed LGPL-3.0-only
Published 6 months ago
Updated 2 months ago
All versions
1.2.1-1.21.11-Fabric
Release
[Fabric 1.21.11] 1.2.14 months ago 61
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
[1.2.1] - 2026-07-04
Known Bugs
- Relays do not update correctly when you change manually to the experimental Legacy Engine. Leave the default engine if you don't want this bug to happen. Working on.
- On NeoForge, you can't change the cobalt rails gamerules. Working on.
- Lithium and Alternate Current Mods are soft incompatible with Cobalt Age, causing Cobalt to Power Redstone. Working on.
Added
- MULTI-LOADER SUPPORT:
Neoforge and Fabric - NEW BLOCK → Cobalt Lamp: Cobalt lamp will emit the same signal as it receives from cobalt input.
- Cobalt Wires: Added support to Experimental Redstone Features for both Modern and Legacy signal engines.
- Signal Engines: Possibility to switch signal engine algorithms: optimized engine (aka Modern Signal Engine) and the neighbor updater one (aka Legacy / Vanilla). Use
/cobaltage onor/cobaltage offcommand to toggle. Default one is always modern and as long as it is an experimental you shouldn't change the engine.
Changed
- Modern Signal Engine has been revisited. It is now dynamic and uses bit masks all over
ServerLevel.class, making it RAM and CPU friendly. This has increased dramatically the performance. - Converter now inherits an
UPDATE_DELAY, which has been set to 1 redstone tick (2 real ticks). - Redstone Lamp will not take cobalt energy anymore.
Removed
- Internal Garbage: Some old textures that were no longer used have been removed.
Fixed
- Converter: Fixed update loop crash when chain conversion happens. Fixed a bug when the converter couldn't take the best external energy to set its flow direction priority
- Cobalt Wires: Fixed power loop when activated over a Redstone Block
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:pmieAiUD:ZMBFBA3O"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pmieAiUD:ZMBFBA3O"
}

