> For the complete documentation index, see [llms.txt](https://hypocraft.gitbook.io/wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hypocraft.gitbook.io/wiki/hypocraft/vychytavky/vytahy.md).

# Výtahy

Pro hru nesmí chybět výtahy, které tě rychle dopraví nahoru či dolů. Na serveru máme výtahy, které umí rozpoznat také patra.

Výtah vytvoříš jednoduše tak, že na první patro položíš iron blok a přímo nad něj položíš další iron blok. Můžeš si vytvořit neomezeně pater.

Ve výtahu se pohybuješ tak, že pro jízdu nahoru si stoupneš na iron blok a zmáčkneš mezerník. Pro jízdu dolů si stoupneš na iron blok a dáš levý shift.

{% hint style="warning" %}
Maximální výška mezi dvěmi patry je zhruba 32 bloků. Pokud se potřebuješ dostat výš, musíš vytvořit mezi-patro pomocí dalšího iron bloku.
{% endhint %}


---

# 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://hypocraft.gitbook.io/wiki/hypocraft/vychytavky/vytahy.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.