MobManager
Description:
- MobManager's limiter aims to limit the number of mobs that can spawn at one time while still providing the appearance of having lots of mobs (Or less if you really want)
- MobManager's Abilities allow you to fully customize the difficulty of each mob, per world!
- MobManager's Bounty component gives you a flexible way to give players rewards when killing mobs
- MobManager's Spawner gives you total control over where different mobs spawn. Perfect to complete a rpg experience or just add a difficulty to your survival server.
Component Features:
Limiter
- Stop mobs from spawning when no players are nearby
- Stop mobs from spawning when no players are on or near the same height
- Limit the number of mobs allowed to spawn per world
- Limit the number of mobs allowed to spawn dynamically depending on the number of loaded chunks in a world
- Limit the number of mobs allowed to spawn by type (Monsters/Animals/Water Animals/Ambient/Villagers)
- Automagically despawns mobs which move out of range of players
- Does not despawn animals which are in farms Read more
- Does not despawn mobs which have picked up players armor or weapons
- Has the option to stop mobs from spawning near players in creative mode
- Can prevent mobs from spawning which you don't want
- Can allow mobs to spawn without counting towards the mob limits
- Super efficient!
- Optional Multi-Threaded despawner
Abilities
- Customisable Mob Abilities!!
- Customisable Mob SpawnRates
- Have mobs spawn as babies, Creepers spawn Charged and Wolves spawn Angry!
- Customisable Mob Bonus Health
- Customisable Mob Damage Multipliers
- Customisable Mob Potion effects (Last for the life of the mob)
- Customisable Mob Bonus Spawns (Spawn mobs on certain mob when it spawns/dies)
- Customisable Mob Armour sets (Per position, with enchantments)
- Customisable Mob Starting Items/Weapons
- Customisable Mob Drops (Count Range per item, set data, durability and enchantments!)
- Customisable Mob Ability Sets (Combine the above abilities together to create rare super mobs! (Or common :P))
- Show Mob Ability Set names above their heads!! (Mincraft 1.5+ only)
- Highly configurable!
Bounty
- Give players rewards for killing mobs
- Supports fines (Loss of money or experience)
- Customizable message upon receiving a reward/fine
- Rewards can be Money (Requires vault), Item drops or experience
- Set min/max reward values for each mob
- Set reward multipliers for worlds, biomes, time, permissions and even for AbilitySets (Requires Abilities component to be enabled)
- Exploit prevention techniques to prevent players from exploiting your server to earn rewards very fast
Spawner
- Spawns custom mobs around players
- Create specific regions with different sets of mobs which spawn within
- Control max/min distances for spawning in different regions
- Extensive mob limit system. Limit per player, region and specific mob type
- Default config similar to vanilla spawning (To use as a guide/template)
- Spawn requirements for every mob (Which spawn location must meet. Block Standing on, light levels, height, time, biome, world type
- Spawn actions performed upon spawns. Send messages to nearby players or run commands when your mob spawns.
What is a component?
A component is simply a part of MobManager. Every component can be enabled/disabled individually from config.ymlTo do
- Add Protection component to MobManager (Protect the world from things like explosions or Endermen picking up blocks)
Note: Ordered by importance to me (Higher == More important) (Your needs are important to me :D)
Commands:
- /mm help - Prints information about all the available commands
- /mm count - Prints mob counts and limits for each world which MobManager is active. Also prints totals for the server
- /mm count <WorldName> - Prints mob counts and limits for the specific world
- /mm butcher - Removes all mobs (Except villagers) from worlds enabled in MobManager
- /mm butcher <MobTypes> - Removes the given mob types from all worlds enabled in MobManager
- /mm spawn <MobType> <count> [world] [x] [y] [z] - Spawn a given mob at the location (Or yours)
- /mm spawnset <AbilitySetName> <count> [world] [x] [y] [z] - Spawn a given mob at the location (Or yours)
- /mm pspawn <MobType> <count> <Player> - Spawn a given mob on a player
- /mm pspawnset <AbilitySetName> <count> <Player> - Spawn a given mob on a player
- /mm abilitysets - Lists all AbilitySet names (Along with the mobtype) which can be used in /mm spawnset
- /mm mobtypes - Lists all valid EntityTypes for use in configs
- /mm reload - Reloads MobManagers configs
- /mm version - Tells you MobMangers current version + Checks my website for new versions
M = Monster, A = Animal, W = Water Animal (Squid), Am = Ambient Mob (Bats), V = Villagers
Permissions:
- mobmanager.admin - Gives permission to use all /mm commands (Default: OP)
- mobmanager.count - Gives permission to use the /mm count command
- mobmanager.butcher - Gives permission to use the /mm butcher command
- mobmanager.version - Gives permission to use the /mm version command
- mobmanager.reload - Gives permission to use the /mm reload command
- mobmanager.spawn - Gives permission to use the /mm spawn command
- mobmanager.pspawn - Gives permission to use the /mm pspawn command
- mobmanager.abilitysetlist - Gives permission to use the /mm abilitysets command
- mobmanager.mobtypes - Gives permission to use the /mm mobtypes command
Configuration:
As of v2.2 MobManagers configuration files consists of three parts- config.yml - Contains settings to enable/disable MobManager components
- Global configs - Contains global configs for each component, located in MobManager/<component>.yml
- World Configs - Contains settings for each component for each world located in MobManager/worlds/<worldname>/<component>.yml
Every config file contains a header block explaining every setting.
When you first install MobManager world and global configs are auto-magically generated. By default only MobManagers Limiter is enabled, configs for abilities are generated if the component is enabled The defaults for the limiter are pretty conservative. So you may wish to increase the limits. If you need help with the config feel free to PM me and I can make one for you :)
Auto-Update Checker
Mobmanager includes a update checker/downloader. It uses this project page to check for new approved builds. The /mm version command can be used to check if a new version is available on bukkit dev. The update checker is enabled by default and can be disabled in config.yml by setting EnableVersionCheck to false The update downloader is disabled by default can be enabled in config.yml by setting EnableAutoUpdater to trueStatistics
MobManager utilises Hidendra's plugin metrics system, which means that the following information is collected and sent to mcstats.org:- A unique identifier
- The server's version of Java
- Whether the server is in offline or online mode
- The plugin's version
- The server's version
- The OS version/name and architecture
- The core count for the CPU
- The number of players online
- The Metrics version
- MobManager components enabled
Opting out of this service can be done by editing plugins/Plugin Metrics/config.yml and changing opt-out to true
Public Test Server
Public test server has been shut down, will try get a new one in the futureAddress: mc.forgenz.com
Note: After joining, type /warp dev
Note: The test server only has the limiter component enabled
Developer Builds
Development builds of this project can be acquired at the provided continuous integration server.These builds have not been approved by the BukkitDev staff. Use them at your own risk.
Dev Builds
Configuration | Statistics | Reading
@ShadowDog007
Thanks :D answered my question
@xclucky
What do you want to do??
Spawn reasons are just ways mobs can spawn, EDIT: withers are built with this spawn reason BUILD_WITHER.
They are all determined by the bukkit developers, I have no control over them. You can find the rest of them here
Can you add a spawnreason for Withers (or if you already have it, can you update your config)?
@wez1981
Spawn reasons are only used to check whether or not the worlds mob limits are checked and if a player must be nearby for the spawn to occur. It has no effect on the despawner.
To totally stop this, you need to increase the size of your layers. To minimize the number of mobs despawned from spawners you can change MinTicksLivedForDespawn so that players have more of a chance to kill them before they despawn (Or let them get back to the players own level so they are not despawned)
Hi,
i dont think EnabledSpawnReasons is working. I removed -SPAWNER from this list so that mobs spawned from my spawner will not be de-spawned yet when i fly about 50 blocks into the air all the mobs are de-spawned, any ideas?
New build for MobManager has been uploaded!
v2.0 brings customisable SpawnRates + Bonus Health and Bonus Damage for different mob types With multi-world support!!
You can get the new build here
Warning: This build has not yet been approved by bukkitdev staff, use at your own risk
@Jobsti2
I have just confirmed that the command /mm count is displaying an incorrect number of chunks. But MobManager itself still calculates the ChunkCalculatedMaximum correctly
EDIT: The number displayed is in fact the number of chunks which I store information about (Players inside of it and also animal counts) Which is good :D Having it equal to the number of chunks loaded would be a waste of memory :)
@Jobsti2
I will have a look at that later.
@Machinimatt
If you are changing or adding layers, you should add apostrophes around the layer. For some reason it is not needed for all combinations of numbers, but for others it is.
So in the layers section do I need to put an Apostrophe around the values for them to take effect? Or does it not matter?
So..... works great ;-)
But, the plugins doesn't cout the correct Chunks,
MM says (total) 8752 Chunks loaded, Nolagg, lagmeter and wwwlag saying there are 15697 loaded.
Same with Chunks per world, it counts only the half.
I'm on RB 1.4.7 r1
@baffle
Yes that is certainly your problem.
The mob limit is calculated on the fly by checking the lowest of either the World maximum, or the chunk calculated maximum.
The world limit you have set (512) is meant to be an absolute maximum number of monsters/animals (etc) you want in that world at any time, where the chunk calculated maximum will stop too many mobs spawning when there are only a few players online. (e.g. 512 monsters spawning around one player)
Grinders are a slightly different problem, because mobs tend to spawn far above the player, (Or be moved far above) they can be prevented from spawning. To fix this, you could increase the size of the layers in config.yml
Having your layers too big however can cause more spawns further above/below players which have a chance of never being seen by the player. When you edit your layers, make sure there is at least some overlap between each layer.
@ShadowDog007
Forgive me, I guess I'm just confused about how this plugin works then. In my config, I have defaults for say Monsters, which is 512 for my main world. Right now I can do '/mm count world' and it will show 105/41. Why doesn't is say 105/512?
My players are complaining no mobs are spawning out of grinders and mobs in general aren't spawning around the land. Do I have to increase ChunkCalculatedMaximum values to fix this? Like for Monsters it's only 10 for a chunk, seems a bit low, so is that the issue?
@baffle
That is correct. Edit: No, the 2nd number is not the total number of mobs, it is the limit that MobManager will try to enforce.
It is possible to exceed those limits (With the default spawn reasons set in config) when a plugin spawns mobs, or a player spawns mobs via spawn eggs.
You could also end up over those limits when the limits drop (When chunks become unloaded)
I dunno what's up with the /mm count command, it's suppose to be total / limit ? It shows me: M:25/23, A:43/23, W:0/9, Am:3/9, V:0/11
So for Monster, that means 25 are spawned and the total is 23? I don't have my config setup that way...
@diannetea
At the moment, no. I might look into doing something like that for the next version of MobManager
Is there any way to have the plugin send a message to the player when their mobs die? Like say Fred didn't feed his animals and he comes back and 14 had died, it would say "14 of your pigs have died of starvation"
New build has been uploaded!
MobManager v1.8b brings a few small bug fixes + Some big optimizations to the despawner task and the world mob recounter
Remember you can use /mm version to check for updates to MobManager (It works! :D)
You can read about it and download it here
Warning: This build has not yet been approved by bukkitdev staff, use at your own risk
@Jobsti2
Just had a look at WG. If use-creature-spawn-event is false, it does not check mob spawns to see if they are allowed to spawn in the region.
Its not a problem, but a feature. "use-creature-spawn-event: Toggles use of mob-spawning and deny-spawn flags"
I think, it's a WG "problem", but if use-creature-spawn-event is true (default), it works
without problems
@Jobsti2
That's odd. MobManager does not spawn monsters... Don't see why it would cause them to appear in your WG regions.