> 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/hracske-obchody.md).

# Hráčské obchody

Na serveru máš možnost vytvořit si vlastní obchod pro prodej libovolných itemů.

### Nastavení obchodu

{% stepper %}
{% step %}

### 1. krok

* Polož truhlu na libovolné místo
  {% endstep %}

{% step %}

### 2. krok

* Vezmi si do ruky item, který chceš, aby se v dané truhle prodával.
  {% endstep %}

{% step %}

### 3. krok

* Klikni levým tlačítkem myši na truhlu zvoleným itemem.
  {% endstep %}

{% step %}

### 4. krok

* V herním chatu se ti objeví hláška abys zadal, za kolik chceš daný item prodávat.
  {% endstep %}

{% step %}

### 5. krok

* Po zadání ceny (například 50) do chatu a stisknutím enter, se obchod založí.
  {% endstep %}
  {% endstepper %}

### Správa obchodu

* Obchod můžeš spravovat tak, že klikneš pravým tlačítkem myši na cedulku a v chatu se ti objeví možné editace (změna ceny, odstranění obchodu apod.)

### Doplnění obchodu

* Pokud se ti stane, že v obchodu dojdou suroviny, jednoduše je doplníš otevřením truhly a vložením.


---

# 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/hracske-obchody.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.