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

# Welcome

### What's Traveling Merchant?

**Traveling Merchant** is a dynamic NPC plugin for Minecraft servers. It introduces a mysterious trader who appears at random locations for a short time, offering rare loot, collectibles, and event-based items.

***

### ✨ Features

* 🔀 **Randomized Spawning**\
  Merchant appears every X minutes in one of your configured locations.
* 🕒 **Limited-Time Visits**\
  He stays for a short period (e.g. 15 minutes) before disappearing again.
* 🎁 **Unique Loot Pool**\
  Rare items, custom recipes, decorative blocks, and event-based loot.
* 🧭 **Location System**\
  Define specific named locations where the merchant can spawn.
* 💬 **Chat & Visual Effects**\
  Spawn announcements, particle effects, and immersive trader quotes.
* 🛠️ **Admin Tools**\
  Full control via commands for spawning, teleporting, setting locations, and reloading config.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://optimals-plugins.gitbook.io/travelingmerchant/welcome.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.