Last updated
Last updated
Mob Hoppers collect every specified mob that spawns in the chunk the hopper is placed in. Unlike , the Mob Hopper does not have a per-hopper-filter. Mobs collected by Mob Hoppers are specified in the config.yml ().
A Mob Hopper may e.g. collect pigs, cows, and skeletons.
To acquire a Mob Hopper, type:
This will give the specified player x amount of mob hoppers.
To use a Mob Hopper, simply place a Mob Hopper item in the chunk you want it to collect mobs from. The Mob Hopper is now active, and a hologram should appear above the hopper displaying the hopper type, owner name, and the total.
It should look something like this:
In the Mob Storage, you can sell and withdraw mobs:
Sell: Left click (this will sell every mob of that type)
Withdraw: Right click (this will sell up to 64 of the mob type each click)
If you want to sell everything in the Mob Hopper, simply sneak + left click on the Hopper block.
You can enable auto-sell on every Mob Hopper. This will automatically sell the mobs instead of collecting them. To toggle auto-sell, click on the auto-sell item at the bottom of the storage menu.
When withdrawing a mob, every item that's also in the void filter will automatically disposed instead of giving it to the player. This can be useful for filtering out waste loot from mobs.
You can also give players Mob Hoppers which only can collect a single mob type. To give such a Mob Hopper, specify the [single-type] argument in the give command with the entity type you want the hopper to only collect.
The Mob Hopper's storage is similar to the . The Mob storage displays every collectable mob, and the amount and worth you have of each.
Since Minecraft mobs, does not have certain items for each mob type, the item representing each mob is configured in the config.yml (see ).
For more information: see .
The MobHopper also has a void filter, which can be configured the same way as the . To open the void filter, simply click the void filter item in the storage menu.
Unlike the , players can't customize which mobs the hopper should collect themselves. The collected mobs are configured in the mobs.yml file (see ). In this file you need to specify both the mob prices used for selling, and the item that should represent the mob in the GUI.
If you enable HeadDatabase integration, you can also use HeadDB ids instead of vanilla items to represent mobs (see ).
You can also configure custom loot tables and xp for you mobs. This is done in the loot.yml file (see ). When enabled, all mobs in the custom loot table will have their vanilla drops replaced by the custom one. Configuring custom loot is required for legacy versions (< 1.13), since automatic loot generation is not supported for these versions.
