> 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/misc/eula.md).

# Is MyPet EULA compliant?

MyPet was not designed with the EULA in mind but with some changes to the configuration, MyPet should be EULA compliant. This depends mainly on the MyPet features you want to use on your server.

{% hint style="info" %}
In this article players that paid for anything on a server with real money are referred as Donators.
{% endhint %}

## What do I have to change?

1. You can not have skilltrees that are available just for donators or players that paid for a pet. That means that every skilltree must be available for everyone at the same point.
2. Disable special abilities of the pets like cows giving milk or sheep shearing. Just go throuh the pet-config.yml and disable them all.
3. All base stats must be the same for all pets or at least not higher than pets that are freely available.
4. ![$](https://398449298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FO9eOHwvWW2IiZ6BGEVmE%2Fuploads%2Fgit-blob-215b32e76b6f57909a4b8e8d78a21b080b3056b2%2Fexclaim.gif?alt=media) Pets that can be bought on the shop are not allowed to have higher EXP or skilltrees that are not publicly available.
5. [Custom EXP scripts](https://wiki.mypet-plugin.de/experience) must treat everyone (donators and non donatos) equal

## Disclaimer

I can not be held responsible for the things written on this page. Everything was written with best intentions in mind but may contain flaws. If you think there are things missing or not correct please contact me on the [Spigot Forums](https://www.spigotmc.org/conversations/add?to=Keyle\&title=EULA).


---

# 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/misc/eula.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.