Throw 2


This plugin allows the players to get the new Spawn Eggs from Minecraft 1.1 by throwing regular eggs at mobs. It is intended to be simple to set up and use. The plugin is open source and can be forked on github. If you make any changes, pull requests are appreciated.

Current features

  • Configurable mob health limit.
  • Respects animal protection plugins such as GriefPrevention
  • Compatible with all trading plugins.
  • Very simple, throw an egg at a mob and it will be turned into a spawn egg.
  • Permissions support.
  • Configurable catch chance.
  • Configurable cost (vault support, or items).
  • Explosion effects.

Installation and requirements

Vault is not required unless you intend to use it

Download the jar file and the configuration file will be generated on the first startup.

Configuration and permissions


Video credits: VariationVault

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of VariousArtist VariousArtist Feb 08, 2015 at 22:01 UTC - 0 likes

    @shansen1: Go

    This stupid plugin even autoupdates when the updater is disabled! Can you please fix this crap? Thanks!

    MadRealms: The Skyland Pirates [Factions-PvP][Airships][Skylands][Survival][PvP][HardCore] - - We create worlds!

  • Avatar of wd40bomber7 wd40bomber7 Feb 08, 2015 at 20:47 UTC - 0 likes

    I'm almost certain this isn't a problem with eggcatcher, but I'll ask anyways. Is anyone having a problem with spawned villagers disappearing after the player gets too far, exactly like hostile mobs? Or know of anything that could cause that?

  • Avatar of shansen1 shansen1 Feb 05, 2015 at 11:27 UTC - 0 likes

    @MikeGold: Go

    No it doesn't have to be updated. Only to add in new mobs etc. So if you are running the 1.8 server with the EggCatcher version for 1.7 it will still work but you'll be unable to catch the new 1.8 mobs.

    Although it hasn't happened for 3 years there is of course always a chance that something major changes in the Bukkit/Spigot/whatever api that breaks the plugin. But the whole point of the Bukkit API is to keep the plugins forward compatible.

  • Avatar of MikeGold MikeGold Feb 05, 2015 at 11:20 UTC - 1 like

    I'm totally new to your plugin. So you mean that your plugin doesn't have to be updated with each server update? That would be a huge thing for me, as my users are heavily dependent on mob catcher and I always have to wait for it to update.

  • Avatar of shansen1 shansen1 Feb 05, 2015 at 01:53 UTC - 0 likes

    @MikeGold: Go

    When I made EggCatcher I made it to have a way to get the vanilla spawn eggs with vanilla features. I wanted it to be simple and compliant with other plugins. Shortly after MobCatcher was introduced and released with additional features. It is though not as compliant with many plugins (they can't handle the extra data on the items). Also MobCatcher has to release an update for each new build of bukkit/spigot, which means waiting.

    If I were to put the same features into EggCatcher I would end up with the same limitations as MobCatcher. It also seems like the users of EggCatcher chooses EggCatcher over MobCatcher because of simplicity and stability (I've been told this over and over again). Same as MobCatcher users chooses MobCatcher over EggCatcher for the extra features.

    So it's much better that if people want those extra features that they just use MobCatcher, instead of starting to add the same features to EggCatcher. To have 2 different plugins with the exact same features doesn't make much sense :)

    I personally like both plugins. It completely depends on how you run your server. As you can see on there's many users of both plugins.

  • Avatar of shansen1 shansen1 Feb 05, 2015 at 01:29 UTC - 0 likes

    @VariousArtist: Go

    I am aware of this problem but it's not an easy fix as the versions (2.0+) that use the bukkit Updater is already deployed. The Updater can be disabled entirely for all plugins in config/Updater/config.yml which I would suggest for all 1.7 servers.

    It never happened before because the 2.0 is the first version with the new updater and there's been no updates since then.

    Right before 2.0 was released bukkit changed their guidelines for auto updating. EggCatchers own updater was no longer compliant. I was therefore forced to change the auto updater to be compliant and changed it to the recommended Updater at the time.

    The default behaviour of Updater is to always update to the latest version no matter what version the server is running.

    The instructions for using that Updater has since changed but I can't change the 2.0 version that is already deployed.

  • Avatar of MikeGold MikeGold Feb 05, 2015 at 01:11 UTC - 1 like

    Thanks for the reply. It was a feature that was in the plugin that I have previously used and it's name starts with "mob" if you catch my drift. None the less it's ok and my users are happy to have mob catching in game once again ;].

  • Avatar of VariousArtist VariousArtist Feb 05, 2015 at 00:15 UTC - 1 like

    2 days ago your plugin autoupdated to version 2.3 on a 1.7.10 server. Not cool! Even with "checkforupdates" true it shouldnt autoupdate without the input from an admin! And especially not on a server that cant run the plugin! Why did that never happen before? Fix that please!

  • Avatar of WillyBee55 WillyBee55 Feb 04, 2015 at 19:35 UTC - 0 likes

    @MikeGold: Go

    The plugin uses the spawn eggs Minecraft already has, which spawning on the ground where you right click is the only way, so I doubt there could be a way to do it, at least not easily.

  • Avatar of MikeGold MikeGold Feb 04, 2015 at 19:06 UTC - 1 like

    Great plugin! The only thing I'd love to see is the way to throw the spawn eggs. At the moment I can only place them on the ground and the mob spawns from them.


Date created
Jan 14, 2012
Last update
Mar 12, 2016
Development stage
  • enUS
GNU General Public License version 3 (GPLv3)
Curse link
Recent files