> 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/supported-mobs/overview.md).

# Overview

List of supported pets and the MyPet version where each pet was added.

Use this page as the index for all pet pages.

In this docs section:

* A **mob** is a vanilla Minecraft entity type (e.g. Wolf, Zombie).
* A **Pet** is a mob that MyPet can tame and manage.

{% hint style="info" %}
Versions listed here refer to **MyPet** versions. Not Minecraft versions.
{% endhint %}

<details>

<summary>Supported Pets (by vanilla mob type)</summary>

These are vanilla mob types that MyPet supports as Pets.

| Mob type (vanilla) | Supported since (MyPet) | Notes        |
| ------------------ | ----------------------- | ------------ |
| `<Mob type>`       | `<e.g. 3.12.0>`         | `<optional>` |

</details>

### Unsupported mobs

These vanilla mob types are not available as MyPet Pets. This may change in future releases.

| Mob type (vanilla) | Reason / status                       | Notes        |
| ------------------ | ------------------------------------- | ------------ |
| `<Mob type>`       | `<not supported / planned / unknown>` | `<optional>` |

### Add a new Pet

1. Duplicate **Pet Page Template**.
2. Rename it to the Pet’s name.
3. Add the mob type to the supported Pets table.
4. Fill in the version where support was added.


---

# 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/supported-mobs/overview.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.