> For the complete documentation index, see [llms.txt](https://mossuh.gitbook.io/projects/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mossuh.gitbook.io/projects/plugins/moarmors/commands.md).

# Commands

{% hint style="info" %}
You can use `ALL` as a argument un `<piece type>` to take all the parts into account `(HELMET, CHESTPLATE, LEGGINGS, BOOTS)`.
{% endhint %}

| Command                                           | Description                           |
| ------------------------------------------------- | ------------------------------------- |
| `/moarmors give <code> <piece type> <player>`     | Gives a piece to a player.            |
| `/moarmors giveall <code> <piece type>`           | Gives a piece to every online player. |
| `/mopets addexp <piece type> <amount> <player>`   | Adds experience to the active piece.  |
| `/mopets setexp <piece type> <amount> <player>`   | Sets the active piece's experience.   |
| `/mopets addlevel <piece type> <amount> <player>` | Adds levels to the active piece.      |
| `/mopets setlevel <piece type> <amount> <player>` | Sets the piece level.                 |
| `/mopets activearmor`                             | Displays all active armor piece.      |
| `/mopets check`                                   | Shows piece information.              |

<p align="center"><strong>Permission to use the commands</strong></p>

<h3 align="center"><strong><code>moarmors.admin</code></strong></h3>


---

# 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://mossuh.gitbook.io/projects/plugins/moarmors/commands.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.