Per-chunk limits
To keep the server running smooth, there's a cap on certain blocks (hoppers, pistons, spawners…) per chunk, plus an automatic brake for overly intense redstone. Check it with /limits.
To keep the server running smooth, there's a cap on certain blocks (hoppers, pistons, spawners…) per chunk, plus an automatic brake for overly intense redstone. Check it with /limits.
- Cap on certain blocks per chunk (16×16 area): 32 hoppers, 1 spawner, 256 chests/furnaces…
- The limit applies when placing; it doesn't delete what you already had
/limits Check the per-chunk block limits
To keep the server performing well, there's a cap on how many blocks of certain types you can place in a single chunk (a 16×16-block area of ground). The limit applies when placing: if the chunk is already maxed out on that block, it won't let you put down any more.
Limits are per chunk and apply in every world. They're not retroactive: they don't delete anything you had already placed. If you're going to build a big farm, spread it across several chunks.
| Block | Max per chunk |
|---|---|
| Hopper | 32 |
| Dropper | 32 |
| Dispenser | 32 |
| Observer | 16 |
| Piston / sticky piston | 16 |
| Repeater | 48 |
| Comparator | 32 |
| Redstone torch | 64 |
| Crafter (1.21) | 6 |
| TNT | 8 |
| Lectern | 12 |
| Spawner | 1 |
| Beds | 64 |
| Chests, furnaces and the like | 256 |
On top of the per-chunk limit, there's an automatic redstone brake: if a circuit fires too many signals too fast (more than 50,000 updates in half a second within a 30-block radius), the game stops the signals in that area to protect the server.
This doesn't bother normal circuits; it only kicks in with extremely fast clocks or machines built to create lag.
If your redstone suddenly stops for no apparent reason, you've probably gone over this limit. Slow the circuit down and it'll work again.