This site works best with JavaScript enabled. Please enable JavaScript to get the best experience from this site.
This ticket is related to the following update in verion 2.9.0 for MC 1.8.1:Changed mob-spawner. It'll now nerf mob-spawners much better and prevent bypassing
What steps will reproduce the problem?1. Set the following in the config:mobspawner: enabled: true max-spawn: 42. place a spawner at the corner of a chunk3. watch the mobs spawn
What is the expected output? What do you see instead?Expect that the spawner will only spawn 4 mobs.The mobs can spawn on 4 different chunks so there can be as may as 4 times the mods that was specified in the config.
What version of the product are you using?verion 2.9.0 for MC 1.8.1
Do you have an error log of what happened?No error log. It is just not working as expected.
Please provide any additional information below.
Mc Server version ? 1.8.8 is latest, y'know.
Not a bug. The mob-spawner limiter will limit solely based on where the entity is placed by the mob spawner.
Why? Well it's extremely efficient to go by "chunk-keys", and IMO does a better job of limiting thousands of mob-spawners within a small region.
Why not go by the mob-spawners chunk? Bukkit provides no API for getting the location of the spawner. It simply provides a static final enum that's sole intention is for identifying the spawn reason. I could iterate through the nearby chunks and check for tile-entities, but that still wouldn't provide an accurate mob-spawner and would most likely cause more lagg then prevent.
To post a comment, please login or register a new account.