zMBlockLimiter

Limit specific blocks per chunk to reduce lag and keep your server running smoothly.

Designed for Paper, Spigot, Pufferfish, and Purpur, zMBlockLimiter helps control automatic farms and technical builds with minimal performance impact.

---

✨ Features

• Limit blocks per chunk (16×16).
• Configure different limits for each world.
• Fully compatible with existing worlds.
• PlaceholderAPI integration.
• SQLite persistence.
• Smart and lightweight chunk scanning.
• Asynchronous database operations.
• Optimized for high-performance servers.
• Simple and easy-to-use configuration.

---

⚙️ How It Works

Unlike plugins that constantly scan the world, zMBlockLimiter only updates counters when necessary.

• Blocks are tracked individually inside each chunk.
• Counters update instantly when blocks are placed or broken.
• Chunks are scanned only when needed.
• No continuous world scans.
• Existing worlds are fully supported.
• After adding new block limits, simply run:

/zmblocklimiter rescan

to safely recalculate all counters.

---

📷 Preview

!Preview

---

📋 Commands

Command	Description
/zmblocklimiter reload	Reload the configuration.
/zmblocklimiter rescan	Recalculate block counters after editing the configuration.

---

🔑 Permissions

Permission	Description
zmblocklimiter.admin	Access to all commands.
zmblocklimiter.reload	Allows using /zmblocklimiter reload.
zmblocklimiter.rescan	Allows using /zmblocklimiter rescan.

---

🌍 Per-World Limits

Need different limits for different worlds?

No problem.

Each world can have its own configuration, allowing you to set stricter limits in survival while using different values in creative, resource, or event worlds.

---

🔌 PlaceholderAPI

PlaceholderAPI is optional.

If PlaceholderAPI is not installed, zMBlockLimiter will continue working normally. Only placeholders will be unavailable.

Available Placeholders

Placeholder	Description
%zmblocklimiter_limit_[BLOCK]%	Displays the configured limit for the block.
%zmblocklimiter_remaining_[BLOCK]%	Displays how many blocks remain before reaching the limit.
%zmblocklimiter_blockcount_[BLOCK]%	Displays the current amount of that block in the player's chunk.

Examples

%zmblocklimiter_limit_HOPPER%
%zmblocklimiter_remaining_HOPPER%
%zmblocklimiter_blockcount_HOPPER%

---

⚙️ Configuration Example

limits:
  HOPPER: 32
  DISPENSER: 64
  DROPPER: 64

worlds:
  world:
    HOPPER: 32

  world_nether:
    HOPPER: 16

---

🚀 Performance

Why is zMBlockLimiter so lightweight?

• No constant world scans.
• No heavy repeating tasks.
• Incremental block counting.
• SQLite persistence.
• Asynchronous database writes.
• Optimized for survival servers with many players.

---

📦 Compatibility

Software	Supported
Paper	✅
Spigot	✅
Purpur	✅
Pufferfish	✅
PlaceholderAPI (Optional)	✅

Minecraft Versions

• 1.21+

---

❤️ Why zMBlockLimiter?

Feature	Included
Per-chunk limits	✅
Per-world limits	✅
Existing world support	✅
SQLite persistence	✅
PlaceholderAPI support	✅
Lightweight	✅
Low TPS impact	✅
Automatic chunk tracking	✅

---

🌎 Languages

• English
• Español

---

👨‍💻 Developer

Developed by zMarkitos_