Mob Spawn Control
Mob Spawn Control allows you to take control of the XP grinders (experience grinders, mob farms) on your server. Our server had a problem with XP grinders bringing the server to its knees. I created this plugin to limit the number of monsters (mobs) that could pop out of a given spawner. Once the spawner is maxed it will prevent further monster spawns until a monster is killed. Once the monster is killed it is decremented from the list. Basically the plugin keeps track of active/alive monsters attached to a spawner.
Feature List
- Limit monsters spawned from a single spawner
- Report on top spawners currently on the server
- Assigns spawner to a player in the report
- Teleport to a given spawner for investigation
- In-game debugging option
- In-game enable/disable option
- In-game stat reset
- In-game configuration reload
Why Should I use MSC?
There are many different plugins that handle mob spawners. I've reviewed each of them and they all have their advantages. Rather than tell you "MSC is the best" I will give you a break-down of the problem each plugin resolves. I fully support the other plugins in the community which is why I've linked them below. You decide which is best for your scenario.
My thoughts on other Mob Spawner control plugins can be found HERE.
Commands
All commands can be accessed by typing /msc or /mobspawncontrol followed by the following subcommands:
- HELP = shows the help menu
- STATS = shows the current spawner stats
- TP = teleports to a given spawner in the stats report
- RESETSTATS = reset all current stats on the server
- DEBUG = enabled debugging mode in the console (Lots of spam here!)
- RELOAD = reload the config from disk
- TOGGLE = toggles the plugin on and off in real time
Permissions
- msc.*: Gives access to all MobSpawnControl features
- msc.command: Allows player access to MSC commands
- msc.stats: Allows players access to STATS command
- msc.tp: Allows players access to TP command
- msc.resetstats: Allows players access to RESETSTATS command
- msc.debug: Enables MSC debugging
- msc.reload: Reloads config from disk
- msc.toggle: Toggles the plugin on and off in real time
Config Options
- spawnsAllowed:
- reportSize:
- pluginEnable:
- debug:
- oneTimeUse:
- warnThreshold:
- alertThreshold:
- spawnerRadiusX:
- spawnerRadiusY:
- spawnerRadiusZ:
- playerDistance:
Detailed config descriptions can be found HERE.
Source
Source can be found HERE.
doesnt work for 1.12
i cant change the player distance for the spawner to work, still stuck on 16
Still works in 1.9! Just had to rebuilt it with latest bukkit. :)
Looks a great plugin, we would need the ability to limit the number of spawners a player can place, that would be our biggest requirement as clear lagg controls most everything else. Like the features though
Would be great if the developer would update it...
Doesn't work for 1.7.9 Plugin appears in green but It doesn't calculate the number of monster at all. I waited the spawn of ten monster by one specific monsterspawner block and the stats are still displaying 1/10 (I fixed a limit of 10 in the config.yml) and mobs continue to spawn from it.
It seems after updating to 1.7.5, spawners that are placed right next to each other or very close (a couple blocks) will have a combined limit. So if I set the max to 25, it will only allow 25 TOTAL from both spawners, instead of 25 each. Once I move them around 5+ blocks away from each other, it creates their own limits.
Thanks for being awesome!
Very nice plugin working perfectly fine even with the newer bukkit versions.
Hi all. Just for sharing information and adding my comments to what kingmonkeycrafter said, this plugin Mob Spawn Control is also working 100% (properly) for me in the 1.7.2 Minecraft version (using Spigot dev. build 1319, Feb. 13). Thank you for your plugin, XxTRAINEExX. It is very useful.
Works like a charm on 1.7.2 and has helped stop players going afk next to mob farms allowing loads of mobs to build up. The TP function is great to keep track of where active spawners are and allowing admins to keep an eye on mob farms and grinders to make sure they are not excessive.
So using this plugin, I've set the range that a spawner will detect a player to much further, as I would like spawners to be active when further away for mob farms to work properly. Anyhow, it doesn't seem to have worked though. From range the spawner still spins as if it's active however it never spawns.
@MasterMithrandir
That's far from true. As long as plugin is utilizing the Bukkit API, there is no need for the plugin to be updated between builds...
@zag09
Chances are, another plugin on your server is conflicting with this one. Most likely one that is using NMS code.
@JAG100
This plugin works perfectly fine, lag free, on 1.6.2. Feel free to use it.
@JAG100 The author hasnt logged in since March 17th, I highly doubt this will be continued.
Anyone try this successfully under 1.6.2?
Any chance of an update on this incredible plugin?
Best, JAG100
@MinecraftAdmin
using outdated plugins can cause lag on bukkit servers...
This plugin brought our tps really low, after removing it it went back to normal
@IceFrog1
This plugin works fine with 1.5. Please try using the plugin before asking for an update!
update to 1.5 please
This plugin work with 1.5 ?
I'm glad it's still working for everyone. I took a small break from Minecraft but I'm back. :) ragan262 is right that the plugin is hard to break. I use some very basic methods to stop the spawn so it's doubtful new versions of CB will break the functionality.
Just tried it on our test server and it seems to work like a charm. Goodbye to people AFKing at their XP farms and bringing the server down to 7TPS!