> For the complete documentation index, see [llms.txt](https://bylotuz.gitbook.io/petslime/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bylotuz.gitbook.io/petslime/account-levels.md).

# Account levels

Your account starts at level 0, every time a Slime dies, your account goes up 1 level. Every 5 levels you gain an advantage in Slime production:

Level 5: +0.5% 

Level 10: +1% 

Level 15: +1.5% 

Level 20: +2% 

Level 25: +2.5% 

Level 30: +3% 

Level 35: +3.5% 

Level 40: +4% 

Level 45: +4.5% 

Level 50: +5% 

Level 60: +5.5% 

Level 65: +6% 

Level 70: +6.5% 

Level 75: +7% 

Level 80: +7.5%

 Level 85: +8% 

Level 90: +8.5% 

Level 95: +9% 

Level 100: +10%

**Advanced levels**

Level 120: +1% Rainbow Slime production 

Level 140: +2% Rainbow Slime production 

Level 160: +3% Rainbow Slime production 

Level 180: +4% Rainbow Slime production 

Level 200: +5% Rainbow Slime production


---

# 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://bylotuz.gitbook.io/petslime/account-levels.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.