This wiki is currently under active development.
For the complete documentation index, see llms.txt. This page is also available as Markdown.

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>).

<shop-id> can be chosen freely but must be unique for every shop. This corresponds to <shop-name> in the shop permission node.

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 such as MythicMobs pets — see the note below.

Example template

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, because MythicMobs spawns the entity rather than MyPet. Skilltree: and Name: still apply. The server log names any option that was skipped at checkout.

Last updated

Was this helpful?