> For the complete documentation index, see [llms.txt](https://wiki.mypet-plugin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.mypet-plugin.com/setup-guide/getting-started/configuration/pet-shops.yml.md).

# pet-shops.yml

Contains options for pet shops.

The `pet-shops.yml` file contains the shops where players can buy pets.

You can create as many shops as you want, but all of them need different IDs (`<shop-id>`). Each shop can be opened by its id with the `/petshop <shop-id>` command. Every item in the shop needs a unique ID too (`<id>`).

{% hint style="info" %}
`<shop-id>` can be chosen freely but must be unique for every shop.\
This corresponds to `<shop-name>` in the shop permission node.
{% endhint %}

## Settings

Below is the structure and types for entries in `pet-shops.yml`.

* Shops:
  * `<shop-id>`:
    * Name (string): The name that will be shown in the shop overview
    * Balance (string): Wallet type. Default is `Private`.
    * Pets:
      * `<id>`:
        * Name (string): The name the pet will have
        * Description (list of strings): The description that will be shown when hovering the shop item
        * Position (integer): The slot in the inventory the pet item will have in the shop
        * Exp (double): The XP the pet will have
        * Price (double): The price the player has to pay in order to get the pet
        * Skilltree (string): The skilltree the pet will have
        * PetType (string): The mob type of the pet
        * Options (list of strings): These work exactly like the parameters for the `pet create` admin command. Options that change the mob itself (`baby`, `variant:`, `saddle`, …) are skipped for [source-driven custom creatures](/setup-guide/getting-started/systems/custom-pet-models.md) such as MythicMobs pets — see the note below.

## Example template

```yaml
# pet-shops.yml

shops:
  <shop-id>:
    Name: "<Shop Display Name>"
    Balance: "<wallet>"
    Pets:
      <id>:
        Name: "<Pet Name>"
        Description:
          - "First line of description"
          - "Second line"
        Position: 10
        Exp: 0.0
        Price: 100.0
        Skilltree: "<skilltree-id>"
        PetType: "<mob-type>"
        Options:
          - "option1:value"
          - "option2:value"
```

## Notes

* Each shop must have a unique `<shop-id>`.
* Each pet item inside a shop must have a unique `<id>`.
* Open a shop with: `/petshop <shop-id>`.
* Open a shop **for someone else** with: `/petshop <shop-id> <player>` — the form to use from the console, a command block, or a menu plugin button (`petshop <shop-id> %player%`). It requires `mypet.command.shop.other` for player senders, and does not require the target to hold `mypet.shop.access.<shop-id>`.
* `Options:` entries that change the mob (`baby`, `variant:`, `saddle`, `tamed`, …) do nothing when `PetType` is a [MythicMobs custom creature](/setup-guide/getting-started/systems/custom-pet-models.md), because MythicMobs spawns the entity rather than MyPet. `Skilltree:` and `Name:` still apply. The server log names any option that was skipped at checkout.


---

# 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://wiki.mypet-plugin.com/setup-guide/getting-started/configuration/pet-shops.yml.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.