What Is VillagerBlock and Why Your Server Needs It
Villagers are among the most valuable passive mobs in Minecraft. They offer trades for emeralds, enchanted books, diamond gear, and food. Yet they are also extremely vulnerable. A single stray arrow, a splash potion, or a zombie siege can wipe out an entire trading hall in seconds. For server owners who want to preserve their economy or protect carefully bred villagers, VillagerBlock provides a lightweight, highly configurable solution. This plugin lets you block a wide range of harmful actions against villagers, from direct player attacks to environmental hazards, and even restrict trading in protected areas.
Core Protection Features
VillagerBlock does not simply cancel damage from a player’s sword. It covers nearly every imaginable threat a villager might face. You can toggle each damage source independently, so you only block what matters for your server’s gameplay style.
- Direct Player Attacks: Melee hits are blocked when enabled. Players without the right permission will see a custom message.
- Projectiles: Snowballs, arrows, and eggs can all be prevented from harming villagers.
- Potions: Harmful splash and lingering potions are neutralized before they deal damage.
- Environmental Hazards: Fire, lava, fall damage, drowning, and even creeper explosions are all configurable. You can stop a creeper from obliterating your trading hall or prevent villagers from dying in a lava pool.
- Mob Attacks: Zombies that target villagers can be blocked entirely, so zombie sieges become harmless to your villagers.
- TNT Explosions: Whether from griefers or redstone contraptions, TNT damage to villagers can be disabled.
Each of these options lives in a simple configuration file, giving you fine-grained control without needing to touch a single line of code.
Region-Based Protection with WorldGuard and Residence
One of the plugin’s standout features is its seamless integration with popular region plugins. You can choose between WorldGuard or Residence to limit villager protection to specific areas. This means you can allow normal villager deaths in the wilderness while keeping them immortal inside a protected city or shopping district. If you set regions.use to true and select your region plugin, all the damage blocking options will only apply inside regions where the player lacks build permissions. This is perfect for survival servers that want a safe spawn village but a dangerous open world.
Trade Restrictions for Extra Control
VillagerBlock also includes an optional trade blocking system. You can prevent players from trading with villagers entirely, or only inside protected regions where they cannot build. This helps prevent exploitation of discounted trades or locks certain villagers behind permission nodes. The messages are fully customizable, so you can inform players exactly why trading is unavailable.
Configuration Walkthrough
After the first run, VillagerBlock generates a config.yml file inside /plugins/VillagerBlock/. Here is a breakdown of the most important sections:
Logging
Enable log to record every attempt to kill a villager. Set log_deaths to true to capture the exact death position, which is invaluable for tracking down rule-breakers or finding gaps in your protection.
Region Settings
Under regions, you can toggle the entire region feature on or off and pick either worldguard or residence. If you set use to false, the plugin will protect villagers everywhere regardless of regions.
Damage Blocking Toggles
Every damage source has its own true/false flag. For example, setting zombies: true stops zombies from damaging villagers, while creeper: true prevents creeper explosions from killing them.
Trade Block
The trade_block section lets you disable trading globally or only in protected areas. The block_only_in_protects option works hand-in-hand with region plugins, so players can still trade freely outside restricted zones.
Custom Messages
All denial messages are editable. You can tailor cantkill, cantkill_all, canttrade, and canttrade_protect to match your server’s tone.
Permissions and Commands
VillagerBlock uses a minimal set of permissions to keep things simple:
villagerblock.cankill— Allows a player to hit or kill villagers inside protected regions (default for operators).villagerblock.reload— Grants access to the/vreloadcommand for reloading the config in-game (OP default).villagerblock.trade— If trade blocking is active and not limited to protected areas, this permission lets a player trade (OP default).
The only command you need is /vreload, which instantly applies any changes you made to the configuration without restarting the server.
Installation Made Simple
Setting up VillagerBlock follows the standard Bukkit/Spigot plugin process. Stop your server, place the plugin JAR into the plugins folder, and start the server again. The plugin will create its config file automatically. After editing the settings to your liking, use /vreload to activate them. Many server admins prefer to manage their plugins through a modern launcher that simplifies the whole workflow. For instance, the foxygame.net launcher lets you browse and install mods directly from its menu, making it a convenient and flexible tool for keeping your server’s plugin collection up to date without manual file transfers. Once installed, you can fine-tune VillagerBlock exactly as described.
Why VillagerBlock Stands Out
Unlike broad anti-grief plugins that add overhead and complexity, VillagerBlock focuses solely on villagers. It respects region boundaries, logs incidents, and gives you message customization. The source code is available on GitHub for those who want to inspect or contribute, and the plugin remains actively maintained with community feedback. Whether you run a small survival world or a large economy server, protecting your villagers has never been easier.
Final Thoughts
VillagerBlock fills a specific but essential niche. It prevents accidental and intentional villager deaths, preserves trading halls, and integrates smoothly with your existing protection setup. With its clear configuration, straightforward permissions, and support for WorldGuard and Residence, it is a must-have for any server owner who values their villagers. Install it, configure your protected zones, and give your villagers the safety they deserve.