> For the complete documentation index, see [llms.txt](https://wiki.dcxwc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.dcxwc.com/minecraft-content/data-packs-and-plugins/double-shulker-shells.md).

# Double Shulker Shells ‼️

#### 🧠 How It Works

In vanilla Minecraft:

* Shulkers have a **50% chance** to drop **1 shulker shell** when killed.

With this datapack:

* Shulkers instead have a **100% chance** to drop **1 shell**.
* Looting enchantments **still apply**, giving a chance to drop **extra shells**.
* This effectively **doubles the average number of shells** you’ll get per shulker kill, but doesn’t make every kill drop 2 shells.

🔍 **Key Difference:**\
This is not a guaranteed “2 shells per kill” change — it's a **probability tweak** that **doubles the base drop rate**, making shulker farming more reliable without being overpowered.


---

# 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://wiki.dcxwc.com/minecraft-content/data-packs-and-plugins/double-shulker-shells.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.