Tags
Creators
Details
Licensed MIT
Published 4 months ago
Updated yesterday
All versions
1.5.1
Release
Create: Stats & Power 1.5.1yesterday 142
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
From 1.5.0_Alpha Fixed
- Cables and Power Distribution Units crashes the game on certain configs (studiovoyage)
- The PDU screen flickers as you moved The Battery Controller and Capacitor Bank had it too, and are fixed as well
- The PDU's bottom line was hidden behind its own breakers
- Added
- Boards can chain a Power Distribution Unit can now be a device on another board's branch. Feed a board from a controller, run its leg to the next room's board, and keep going. Power leaving the back boss is counted properly, and two controllers can feed one board
- A Chain page on the PDU screen it shows what is upstream, what is downstream, and where along a chain things are starving
- Indoor Cable turns corners all twelve of them. A run down a door frame and away along the floor just works, instead of floating eight pixels off the wall. Sneak and right-click clips a whole run at once instead of one block at a time
- Power Outlets and a Smart Home Panel that knows about them. Whatever is plugged into an outlet now gets its own row and its own switch, instead of being invisible
- Rename your devices straight from the Smart Home Panel
- The Bread Slicer is rebuilt a serrated blade rises out of the deck, opens the loaf, and drops back out of sight. Parked, there is no knife in the machine at all. The loaf has a real shape now, with a crust and a proper cut face. Thin slices cost real power: 20 FE/t at Thick, 40 at Medium, 80 at Thin
- The Toaster takes slices, not whole loaves the chain is bread, slicer, toaster
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:inKFQSzo:pFmjFOtq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:inKFQSzo:pFmjFOtq"
}

