All versions
rv11-d
Release
rv11-d2 years ago 41
Compatibility
Minecraft: Java Edition
1.5.x
Platform
Forge
Supported environments
Client and server
Changes
- Added Null Check for potentially bad items.
- Powered Screens are now 'brighter'
- Level Emitter torch appears to glow
- The MAC Opens to last open page on first open.
- Fixed minor oddity with cable model being inconsistent.
- Vibration Catalyst can now only 'smelt' fully smelt-able blocks. ( no partially smelt-able blocks )
- Fixed localization of the word "OF"
- Updated For better power API
- Fix for strange chunk loading / unloading behavior.
- Fixed a bug with the gui not updating as a storage cell is used to generate items in the Condenser.
- Fixed "Sort By Priority"
- Level Emitter can now save its settings.
- Hit boxes now work on individual parts of cables and buses.
- Fixed potential issue with T-Planes Black / White lists.
- Added Link and Unlinked Localization.
- Fixed an issue with crafting when processing the output from one cpu into another.
- Corrected and issue that could result in unloaded chunks reloading.
- Fixed a bug in the handling of block placement.
- Placing a colored cable on a bus, will change the color of the bus. ( in addition to placing the bus on the colored cable. )
- Fixed crash when editing a mac and opening the GUI very quickly
- Fixed a bug with ridding entities and using the matter cannon.
- ME Colored Blocks can now be painted with IC2 and GT Painters
- Facades on the Bus side of the various bus Blocks now render better.
- Added a small clear button on the Crafting Terminal Gui ( Space clicking still works )
- Interface -> Interfaces transactions now no longer use the Interfaces internal storage.
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:AlDk2AVa:tbKhQmRE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AlDk2AVa:tbKhQmRE"
}

