> For the complete documentation index, see [llms.txt](https://docs.tweetzy.ca/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tweetzy.ca/official-plugins/crafty/mob-and-blocks.md).

# Mob & Blocks

**Shared Options** 

* **Drop Default Items** - If this is enabled, then blocks and mobs will no longer drop their default items.
* **Blocked Worlds** - These are worlds where Crafty will ignore any custom drops/changes to mobs/blocks.

**Drop Options**

* **Mobs** - When adding a drop to a mob, you will be able to toggle whether it gets dropped from naturally spawned mobs, mobs spawned in from an egg or from mobs spawned from a spawner.
* **Blocks** - When adding a drop to a block, you will be able to toggle if the drop is dropped from naturally spawned blocks and if they should drop from user placed blocks.  

**NOTICE:** By default any user placed blocks before the plugin is installed will be considered natural since Crafty tags user placed blocks manually.

For more information about drops see [**Drops**](/official-plugins/crafty/drops.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.tweetzy.ca/official-plugins/crafty/mob-and-blocks.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.