Tags
Creators
Details
1.0.2
Compatibility
Changes
Zipline v1.0.2 — Multi-Passenger Feature, Station Surcharges & Dynamic Distance Fares
This release introduces full group transit with multi-passenger trolleys, an overhaul to the economy engine with distance-based pricing and station surcharges, and comprehensive per-station customization.
Multi-Passenger Transit & Trolley Types
- 3 Trolley Modes: Configure trolley capacity with
/zipline edit <id> type <solo|tandem|cable_car>:- Solo (1 Player)
- Tandem (2 Players)
- Cable Car Gondola (4 Players)
- Group Boarding Countdown: When the first player boards a multi-seat trolley, an action bar departure countdown starts (default 10s, configurable via
motion.departure_countdowninconfig.yml), giving party members time to hop in before departure. - Per-Rider Destinations: Each rider on a shared trolley can select their own destination in the GUI.
- Smart Intermediate Station Drop-Offs: When pulling into a mid-route station, only passengers whose destination is that station will dismount—remaining riders stay seated and continue smoothly to their stops.
- Anti-Exploit Fare Protection: Riders who booked a farther destination are prevented from sneaking to dismount early at intermediate stations they did not pay for.
Dynamic Distance Fares & Station Surcharges
- Distance-Based Pricing:
/zipline edit <id> cost <rate>now sets the Rate per meter (Base Fare = Distance × Rate). - Station Surcharges: Stations can now have exclusive arrival fees (
/zipline edit <id> station <stationId> cost <amount>). Total fare is calculated asBase Distance Fare + Station Surcharge. - Configurable Decimal Rounding: Added
economy.fare_rounding_step(default:0.5) inconfig.ymlto round calculated fares to clean increments (e.g.1.37→1.50,66.77→67.00).
Station Management & Destination GUI
- All Stations in GUI: All available stations now appear in the Destination Selection GUI.
- Per-Station Customization Commands: Added the
/zipline edit <id> station <stationId>subcommand family:title <name>: Custom display name for station in GUI and action bar.icon <MATERIAL>: Set Station item icons in the GUI .cost <amount|default>: Per-station arrival surcharge.ticket <hand|MATERIAL|none|default> [amount]: Per-station ticket pass requirement.ticket_name <name|default|clear>: Custom ticket name override for this station.ticket_consume <true|false|default>: Single-use vs. reusable pass toggle per station.id <newId>: Renames the station internal identifier.
Other Config Additions & Patch works
- Added
/zipline cancelto discard an active wand session. - Added
wand.timeout_minutes(default 15m) to automatically clear abandoned wand sessions. - Safe Vault Decoupling: Vault is now a true soft-dependency. If Vault is not installed, the plugin gracefully treats all rides as free without throwing missing dependency errors or console warnings.
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:rOCKAz5M:wAhAuj94"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rOCKAz5M:wAhAuj94"
}

