
CC:LiftLink
CC:LiftLink provides ComputerCraft integration for Create elevators, allowing full control through a single redstone contact. Instead of wiring every floor or connecting to the pulley, you can manage floor calls, track real-time movement, and query elevato
Tags
Creators
Details
1.0.2
Compatibility
Required content
Changes
CC:LiftLink adds ComputerCraft support for Create elevators
using just one connected redstone contact from the elevator column.
Built for Create 1.20.1-6.0.8 and CC: Tweaked 1.20.1 Forge 1.116.1.
Setup
- Build and test your Create elevator normally.
- Connect a ComputerCraft computer to any one redstone contact from that elevator column.
- Get the peripheral with: peripheral.find("create_elevator")
Functions
listFloors() Returns all floors in the column.
callToFloor(name) Calls the elevator to a named floor.
callToY(y) Calls the elevator to a floor by Y level.
getState() Returns the main elevator state table.
getFloors() Returns floor names mapped to Y levels.
getCurrentLevel() Returns current elevator Y level.
getTargetLevel() Returns target Y level.
getTargetY() Returns target Y level.
isMoving() Returns true if the elevator is moving.
isActive() Returns true if the elevator is active.
getCabY() Returns cab Y position.
getSpeed() Returns current speed.
getDirection() Returns "up", "down", or "idle".
getColumnInfo() Returns combined floor and state info.
getCurrentFloor() Returns the exact current floor name and Y.
getNearestFloor() Returns the nearest floor name and Y.
hasFloor(name) Checks if a floor exists.
isAtFloor(name) Checks if the elevator is at that floor.
Notes
You do not need to connect to the pulley. One redstone contact is enough. Github
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:2u32IDgn:dFgeEzsT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2u32IDgn:dFgeEzsT"
}
