> For the complete documentation index, see [llms.txt](https://wiki.lemoncloud.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.lemoncloud.org/server-features/spawners.md).
# Spawners
### Spawners
Spawners are useful for grinding mobs to earn money on our economy gamemodes.
### Stacked Spawners
Spawners can be stacked up to 64 in the same block.
In vanilla, spawners attempt to spawn up to 4 mobs every 10 to 39.95 seconds. We then simply multiply the amount of mobs that spawn by the amount of spawners in the stack.
### Stacked Mobs
Mobs stack up to 1024 mobs in one entity.
#### Functionality
* Stacked mobs attempt to merge with other stacked mobs within a 16 block radius
* Stacked mobs die one-by-one when killed by a player
* Loot is added directly to the killer’s inventory if there’s space, otherwise it will drop to the ground
* XP is given directly to the killer
* Stacked mobs die entirely when killed by natural causes
* Loot for the whole stack is dropped
* XP only drops if the stack took player-inflicted damage in the past 5 seconds
* When a stack reaches 1024, nearby spawners will spawn a new stack in
---
# 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.lemoncloud.org/server-features/spawners.md?ask=&goal=
```
`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.