Tags
Creators
Details
Licensed ARR
Published 4 years ago
Updated last week
All versions
1.4.5-forge-mc1.19
Release
Moving Elevators 1.4.53 years ago 435
Compatibility
Minecraft: Java Edition
1.19–1.19.2
Platforms
Forge
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Moving Elevators 1.4.5
- Created a separate sound entry for when the elevator arrives, so it can be changed by resource packs
Moving Elevators 1.4.4
- Added additional checks for the remote elevator panel
Moving Elevators 1.4.3a
- Fixed crash with some Mekanism blocks
- Fixed crash with Oculus
Moving Elevators 1.4.3
- Fixed crash when breaking the block a remote elevator panel is bound to
Moving Elevators 1.4.2
- Fixed neighboring blocks not properly getting updated when an elevator arrives
Moving Elevators 1.4.1
- Fixed error when trying to move block entities on a dedicated server
Moving Elevators 1.4.0a
- Added separate mixins for Rubidium
Moving Elevators 1.4.0
- Elevator cabins can now contain block entities
- Remote elevators panels can be used inside elevator cabins
- Fixed double faces getting rendered for blocks like glass
Moving Elevators 1.3.12a
- Fixed crash when rendering certain blocks inside the elevator controller's gui
Moving Elevators 1.3.12
- Fixed rare crash when updating from older versions
Moving Elevators 1.3.11b
- Accommodate for changes to LevelTickEvent in Forge 43.2.4
Moving Elevators 1.3.11a
- Fixed rendering offsets inside the elevator controller's gui
Moving Elevators 1.3.11
- Fixed rare crash with Cracker's Wither Storm Mod
- Update Russian translations (thanks to vanja-san!)
Moving Elevators 1.3.10
- Updated to core library 1.1
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:9KZOe6HD:rWCTdFDr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9KZOe6HD:rWCTdFDr"
}

