> For the complete documentation index, see [llms.txt](https://mavenverse.gitbook.io/mavenverse-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mavenverse.gitbook.io/mavenverse-docs/stations-and-call-buttons.md).

# Stations & Call Buttons

Multi-station routes, station bells, and anti-suffocation dismount

How to set up multi-station routes, manage station stops, and configure automated summon buttons.

## Route Types

When mapping a zipline with `/zipline wand`, you can combine three types of points:

1. **Start Station**: Where the ride begins (set with **Left-Click**).
2. **Curve Waypoints**: Smooth curves around trees, hills, or buildings without stopping the trolley (added with **Right-Click**).
3. **Station Stops**: Passenger platforms where the trolley pauses so riders can board or exit (added with **Sneak + Right-Click**).
4. **End Station**: The final terminus (set with **Sneak + Left-Click**).

***

## Station Dwell Time & Getting Off

When a trolley pulls into an intermediate station stop:

* It comes to a gentle stop and pauses for a few seconds (default: 4 seconds).
* Riders see a countdown on their Action Bar:

  ```
  Station Stop ▪ Sneak to exit (3.5s)
  ```
* **To Dismount**: The player presses **Shift (Sneak)** during the pause to safely exit onto the platform.
* **To Keep Going**: If the player stays seated, a chime plays when the countdown ends and the trolley continues along the line.

To adjust the pause duration on any line:

```bash
/zipline edit <id> stop_time <seconds>
```

***

## Safe Platform Step-Off

Stations often have canopies, low rafters, or roof beams overhead. Zipline protects riders on dismount:

* **Walkway Landing**: Riders automatically land safely on the station walkway beside the trolley instead of getting stuck inside the seat.
* **No Suffocation**: Checks that the landing spot has solid footing and clear headroom so players never spawn inside ceiling blocks.
* **In-Flight Lock**: Players cannot accidentally dismount mid-air while the trolley is traveling between stations.

***

## Station Call Buttons

Call buttons allow waiting players to summon an idle trolley parked at another station.

### How to Set Up:

1. Make sure two-way travel is enabled on your line:

   ```bash
   /zipline edit <id> twoway true
   ```
2. Look at any button, lever, or bell on your station platform and run:

   ```bash
   /zipline edit <id> add_button
   ```

   *The plugin automatically figures out which station the button belongs to.*

### How It Works:

* When a player clicks the button, a bell chimes and the trolley travels down the cable to their station.
* If the trolley is already at the caller's station, it lets them know.
* If someone is currently riding the line, it prevents accidental disruption until the ride is finished.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://mavenverse.gitbook.io/mavenverse-docs/stations-and-call-buttons.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.