> 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/setup/update-to-3.0.md).

# Update to 3.0

This page describes what you need to do in order to upgrade to MyPet 3.0

### Step 1 - Put the new JAR file in place

If you are running [MyPet-NPC](/mypet-3/hooks/npc.md) too you can delete that now as it is included into MyPet itself.

### Step 2 - Convert the skilltrees

{% hint style="info" %}
**If you never touched the skilltrees you can skip this step!**
{% endhint %}

If you made your own skilltrees or edited the default ones you need to convert them to the new format using the following steps:

1. open up the new SkilltreeCreator
2. select the folder you want to save your new skilltrees in
3. your browser will open and you will see the new [Skilltree Creator](/mypet-3/systems/skilltrees/skilltreecreator.md)
4. open the menu on the top left hand corner
5. select `Import Legacy Skilltree`
6. follow the 3 steps of the wizard
7. hit the save button
8. upload the new `.st.json` files to the **skilltrees** folder on your server

### Step 3 - Adjust your config files

MyPet doesn't support numeric item IDs anymore. All settings that requires an [config item](/mypet-3/setup/configurations/configitems.md) will require the 1.13 item ID even if you don't run a 1.13 server


---

# 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/mypet-3/setup/update-to-3.0.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.