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

Admin Commands

Administrative commands and examples.

Commands

Command
Description

/petadmin

Admin toolbox command (rename, exp, create, cleanup, …)

/petinventory

Open another player’s pet inventory

/petskill

View another player’s pet skill info


petadmin

Admin toolbox for managing pets.

Usage

/petadmin <option> [parameters...]

Permission

  • MyPet.admin

Options

name

Set the name of a pet for a specific player.

/petadmin name <ownername> <new petname>

exp

Set a pet’s XP for a specific player.

respawn

Set or display a pet’s respawn time.

Notes:

  • Only changes respawn time for dead pets.

reload

Reload selected config files.

skilltree

Change the skilltree of a pet.

build

Show the MyPet version and build number.

create

Create a new pet for a specific player.

Notes:

  • Not usable when the player already has an active pet.

  • Use -f to force creation even if the player has a pet.

  • Use TAB to see valid parameters for the selected pettype.

  • <pettype> is namespaced: vanilla types use minecraft: (minecraft:wolf), custom creatures defined in pet-config.yml use mypet: (mypet:capybara, mypet:frostdragon). The bare name (wolf) also works. TAB-completion lists every registered type in its full namespaced form.

  • Parameters that change the mob itself (baby, variant:, saddle, …) are skipped for MythicMobs custom creatures, because MythicMobs spawns the entity rather than MyPet. skilltree: and name: still apply, and the server log names anything that was skipped.

A mypet: type only exists once you have defined it as a custom creature — including MyPet's bundled Capybara and Chameleon models, which need a pet-config.yml section before they can be created.

clone

Clone a pet from one player and give it to another.

remove

Delete a specific player’s pet.

cleanup

Delete unused pets older than a certain amount of time.

Notes:

  • If no parameter is given, it cleans up pets unused since upgrading to MyPet 1.1.3.

ticket

Create a ZIP file with info needed for developer support.

info item

Show the item you’re holding, with two clipboard buttons for pasting it into a MyPet config:

  • [Copy] — the material name (SHEARS). Matches any item of that type, which is what you usually want for leash, food, ride and control items — a partly worn tool still counts.

  • [Copy with NBT] — the full component string (. minecraft:shears[minecraft:damage=6]). Use it when the item must match exactly, including custom name, lore, enchantments and damage.

Both formats can be pasted straight into config.yml, pet-config.yml, or a skilltree drop pool.


petinventory (admin)

Open another player’s pet inventory.

Usage

Permission

  • MyPet.admin

Aliases

  • /pi

  • /peti


petskill (admin)

View skill info for another player’s pet.

Usage

Notes

  • This requires admin permissions on most servers.


Permissions

Bundle node

MyPet.admin is an umbrella node that grants every granular admin node listed below. Grant MyPet.admin to give a player complete admin capability; grant individual nodes for least-privilege delegation.

/mypet admin subcommands

Permission node
Command / action

MyPet.admin.editor

/mypet editor — open the web editor

MyPet.admin.reload

/mypet reload

MyPet.admin.ticket

/mypet ticket

MyPet.admin.update

/mypet update

/mypetadmin subcommands

Permission node
Subcommand

MyPet.admin.clone

clone

MyPet.admin.create

create

MyPet.admin.exp

exp

MyPet.admin.exprate

exprate

MyPet.admin.info

info

MyPet.admin.name

name

MyPet.admin.npc

npc

MyPet.admin.purge

purge

MyPet.admin.remove

remove

MyPet.admin.respawn

respawn

MyPet.admin.skilltree

skilltree

MyPet.admin.switch

switch

Act on other players’ pets

These nodes allow a player to run standard pet commands targeting another player’s pet:

Permission node
Command

MyPet.command.info.other

/petinfo <player>

MyPet.command.list.other

/petlist <player>

MyPet.command.skill.other

/petskill <player>

MyPet.command.inventory.other

/petinventory <player>

MyPet.command.sendaway.other

/petsendaway <player>

MyPet.command.shop.other

/petshop <shopname> <player>

MyPet.command.shop.other is the odd one out: rather than acting on the target's pet, it opens a shop for them. It is also the only one of these that is usable from the console and from command blocks, which is what menu plugins need to run petshop <shopname> %player% on a button click.

Capability / bypass nodes

  • MyPet.admin — full admin capability: bypasses the stored-pet count limit and unlocks the admin sections of the pet menu.

  • MyPet.admin.notify — receive in-game notifications when a web-editor session applies changes.

Bypass permissions

These exempt a player from a normal gameplay restriction. All are default: op and are granted by the MyPet.admin bundle, so existing admins are unaffected.

Node
Effect

MyPet.bypass.skilltree

Skip automatic skilltree assignment and the choose-only-once lock.

MyPet.bypass.fee

Exempt from the skilltree switch fee (unless Skilltree.SwitchFeeAdmin is set).

MyPet.bypass.death

Exempt from release-on-death and backpack-drop-on-death.

MyPet.bypass.inventory

Open your own pet's backpack without MyPet.extended.inventory.

MyPet.bypass.creative

Use the pet backpack and pickup in Creative mode even when Backpack.OpenInCreative is disabled.

MyPet.petstorage.limit.*

Store the configured maximum number of pets (unlimited tier).

The isMyPetAdmin() API method was removed; these nodes replace it. No code path checks the bare MyPet.admin node anymore — it is purely a bundle.

Last updated

Was this helpful?