Block Limits

Block Limits gives server admins fine-grained control over block placement – perfect for preventing lag machines, griefing, or overuse of powerful blocks on modpacks and SMP servers.

Server side – required. Client side – optional

What it does

Configure hard limits on how many of any block can exist:

• Per chunk – e.g. max 1 beacon per chunk
• Per FTB Chunks claim – e.g. max 3 beacons per claimed area (requires FTB Chunks)
• Adjacency rules – e.g. prevent TNT from being placed next to lava or fire

All rules are enforced even when pistons push tracked blocks across chunk or claim boundaries.

Features

• Simple TOML config – just a list of "modid:block=count" strings
• Passive mode – log and notify violations without cancelling placement
• Item tooltips – players can see the limits directly in the item tooltip
• Lightweight in-memory cache with configurable TTL to keep performance impact minimal
• Broadcasts violation messages to nearby players within a configurable radius

Configuration example

#Per-chunk block limits. Format: "modid:blockname=count"
chunk_limits = ["minecraft:beacon=1", "minecraft:conduit=2"]

#Per-FTB-claim block limits. Format: "modid:blockname=count"
claim_limits = ["minecraft:beacon=3"]

#Adjacency rules. Format: "modid:blockname=modid:forbidden1,modid:forbidden2"
adjacency_rules = ["minecraft:tnt=minecraft:lava,minecraft:fire"]

#When true, violations are reported to nearby players but block placements are NOT cancelled
passive_mode = false