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

# Actions

Actions define what a pet does whenever a specific Minecraft event occurs. Every action may contain:

* Event

```yml
event: <event_type>
```

* Cooldown

```yml
cooldown: <time in seconds>
```

* Cooldown Message

```yml
cooldown_message: "&aA message"
```

* Cooldown Bypass

```yml
# The cooldown_bypass can be useful if you want to check, for example, that the cooldown
# is inactive to execute the rewards and if it is active it will execute the else rewards.

cooldown_bypass: <true/false>
```

* Requirements

```yml
requirements:
    - '[requirement_type] <conditions>'
```

* Rewards

```yml
rewards:
  - '[<chante_type> -> <chance>] <reward_type> -> <reward>'
```

* Else Rewards

```yml
else:
  - '[<chante_type> -> <chance>] <reward_type> -> <reward>'
```

* Cancel Action

```yml
cancel_action: <true/false>
```

* Boosters

```yml
  boosters:
    <custom booster name>:
      multiplier: <multiplier type>
      type: <booster type>
      applicator: <applicator type>
      boosted: <boosted>
      boost: <boost>
```

#### Example:

```yml
default:

  SpeedBoost:

    event: PLAYER_KILLS

    cooldown: 5

    requirements:
      - '[EVENT] ZOMBIE'
      - '[EVAL] %level% >= 5'

    rewards:
      - '[CHANCE -> 50] EFFECT -> SPEED:5:1'
```


---

# 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/actions.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.