> 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/systems/pet-storage.md).

# Pet Storage

The MyPet storage is way to have more than one MyPet.

Pet Storage allows you to store additional pets and activate them later as needed. Only one pet can be active at a time.

### What uses the storage?

* The pet [shop](https://wiki.mypet-plugin.com/misc/premium).
* The `/petstore` and `/petswitch` [commands](https://wiki.mypet-plugin.com/setup/commands).
* The `mypet-storage`-Citizens trait of [MyPet-NPC](https://wiki.mypet-plugin.com/hooks/npc).
* All pets obtained by ways other than taming them.

### How can I limit the amount of pets a player can store?

The amount of pets a player can store is limited by the following permission:

* `MyPet.petstorage.limit.X`
  * `X` needs to be replaced by the amount of pets a player should be able to store.
  * `X` needs to be smaller or equal than the `MyPet.Max-Stored-Pet-Count` in the [config.yml](/setup-guide/getting-started/configuration/config.yml.md#max-stored-pet-count).

### What is the \`Max-Stored-Pet-Count\` config setting for?

Because the server needs to check a lot of permissions in order to check if the player is allowed to store more than his currently stored pets, this config setting jumps in and limits these checks.


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.mypet-plugin.com/setup-guide/getting-started/systems/pet-storage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.