> For the complete documentation index, see [llms.txt](https://docs.playtheatria.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.playtheatria.com/theatria/rules-policies/rules/automation-rule-in-depth.md).

# Automation Rule In Depth

{% hint style="danger" %}
Automation includes *any method* that allows you to bypass **manual gameplay**, including the use of **Minecraft’s own mechanics**.\
This means:

❌ **You must manually kill mobs**—using methods like entity cramming, lava traps, pistons, or similar setups to automatically kill mobs and collect drops *without your active participation* is not allowed.

The core principle is **you must be actively playing** to earn rewards.

If you’re ever unsure whether a setup is allowed, please ask staff. We’re here to help, and no one will be punished for seeking clarity.
{% endhint %}

Redstone mechanisms are allowed, primarily for non-monetary uses such as:

* Auto-smelters
* Door mechanisms
* Item sorters

If you have questions about what is allowed, feel free to open a [staff support ticket](https://discord.gg/hFJWRDKyNz) in Discord. We are happy to help clarify any concerns.

### Blacklisted Items for Hoppers and Pistons

The following items are blacklisted for use with hoppers and pistons, meaning these blocks will not interact with these mechanisms:

* **PUMPKIN**
* **MELON**
* **SUGAR\_CANE**
* **BAMBOO**
* **CACTUS**
* **WHEAT**

{% hint style="danger" %}
Anyone caught automating money-making methods risks severe penalties, including but not limited to:

* **Account wipe** (balance and ranks removed)
* **Audit** (investigation into money distribution and earnings)

**JUST DON'T DO IT.**
{% endhint %}

***

[Rules & Policies](/theatria/rules-policies.md)


---

# 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://docs.playtheatria.com/theatria/rules-policies/rules/automation-rule-in-depth.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.