> 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/player-guide/commands/admin-commands.md).

# Admin Commands

Administrative commands and examples.

### Commands

| Command                                | Description                                             |
| -------------------------------------- | ------------------------------------------------------- |
| [`/petadmin`](#petadmin)               | Admin toolbox command (rename, exp, create, cleanup, …) |
| [`/petinventory`](#petinventory-admin) | Open another player’s pet inventory                     |
| [`/petskill`](#petskill-admin)         | 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.

```
/petadmin exp <ownername> <new exp of the pet> [add|set|remove]
```

**respawn**

Set or display a pet’s respawn time.

Notes:

* Only changes respawn time for **dead** pets.

```
/petadmin respawn <ownername> [new respawntime]
/petadmin respawn <ownername> [show]
```

**reload**

Reload selected config files.

```
/petadmin reload all
/petadmin reload config
/petadmin reload skilltrees
```

**skilltree**

Change the skilltree of a pet.

```
/petadmin skilltree <pet ownername> <skilltree>
```

**build**

Show the MyPet version and build number.

```
/petadmin build
```

**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](https://github.com/MyPetORG/MyPet-Wiki/tree/4.0/setup-guide/getting-started/systems/custom-pet-models.md), because MythicMobs spawns the entity rather than MyPet. `skilltree:` and `name:` still apply, and the server log names anything that was skipped.

```
/petadmin create [-f] <ownername> <pettype> [parameter]
/petadmin create Notch minecraft:wolf
/petadmin create Notch mypet:capybara
```

A `mypet:` type only exists once you have defined it as a [custom creature](https://github.com/MyPetORG/MyPet-Wiki/tree/4.0/setup-guide/getting-started/systems/custom-pet-models.md) — including MyPet's [bundled Capybara and Chameleon models](https://github.com/MyPetORG/MyPet-Wiki/tree/4.0/setup-guide/getting-started/systems/bundled-pet-models.md), which need a `pet-config.yml` section before they can be created.

**clone**

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

```
/petadmin clone <pet ownername> <new pet ownername>
```

**remove**

Delete a specific player’s pet.

```
/petadmin remove <ownername>
```

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

```
/petadmin cleanup [1Y] [1D] [1H] [1M]
```

**ticket**

Create a ZIP file with info needed for developer support.

```
/petadmin ticket
```

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

```
/petadmin info item
```

***

### petinventory (admin)

Open another player’s pet inventory.

{% hint style="warning" %}
This command is **player-only**. You cannot run it from the console.
{% endhint %}

#### Usage

```
/petinventory <playername>
```

#### Permission

* `MyPet.admin`

#### Aliases

* `/pi`
* `/peti`

***

### petskill (admin)

View skill info for another player’s pet.

#### Usage

```
/petskill <playername>
```

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


---

# 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/player-guide/commands/admin-commands.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.