> 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/mypet-3/tutorials/how_to_get_a_mypet.md).

# How to get a pet

## Step 1 - Find the mob you want

Find a mob that is tameable is the easiest step. All mobtypes are tamable except Shulkers because they can't move.

## Step 2 - Meeting the Requirements

This can be the hardest part but how hard it really will depends on the configuration of the Server. Every pet-Type has a [setting](/mypet-3/setup/configurations/pet-config.yml.md) called [LeashFlags](/mypet-3/systems/leashflag.md) that sets the requirements needed for the pet-Type to become a pet.

## Step 3 - Taking mob on a lead

When Step 1 & 2 are done you just have to hit (attack) your target with the LeashItem (`Lead` by default). After hitting your target it will convert from a normal mob into a pet and you will see a message like this:

You took a pet on a lead, it will be a good pet.

{% hint style="info" %}
Using the Lead as a weapon is required to perform the actual act of taming.\
Putting the mob on the lead/rope will do nothing towards taming your new pet.
{% endhint %}


---

# 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/mypet-3/tutorials/how_to_get_a_mypet.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.