Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-5215

MobSpawner "MaximumNearbyEntity" Tag only has maximum range of 4 above and 4 below

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Minecraft 14w34d
    • Minecraft 1.4.6, Minecraft 1.6.1, Minecraft 1.7.2, Minecraft 1.7.4, Minecraft 14w02b, Minecraft 14w02c, Minecraft 14w05b, Minecraft 14w06b, Minecraft 14w07a, Minecraft 14w08a, Minecraft 1.7.5, Minecraft 1.7.9, Minecraft 14w20a, Minecraft 14w20b, Minecraft 14w21b, Minecraft 14w25a, Minecraft 1.7.10-pre4, Minecraft 14w25b, Minecraft 14w26b, Minecraft 1.7.10, Minecraft 14w28a, Minecraft 14w30c, Minecraft 14w31a, Minecraft 14w32a, Minecraft 14w32b, Minecraft 14w32c, Minecraft 14w32d, Minecraft 14w33a, Minecraft 14w33c, Minecraft 14w34a, Minecraft 14w34b, Minecraft 14w34c
    • Community Consensus
    • Creative

      When configuring custom spawners, the "MaximumNearbyEntity" tag which is intended to set a cap for the spawner in relation only appears to have a vertical range of 4 above the spawner and 4 below the spawner. The Wiki states that the y range should be '"SpawnRange" +1 centred around the spawner block'. However, setting the "SpawnRange" tag to anything will still result in a above and below value of 4. This also means that if the position data of the spawned entities is above or below the vertical limits, the cap won't work correctly and they will continue to spawn until the game crashes. I am unsure if this is a bug however it seems desperately lacking as a feature if not in that the horizontal cap range can be made to be much larger than this.

        1. bug4.png
          bug4.png
          280 kB
        2. bug3.png
          bug3.png
          256 kB
        3. bug2.png
          bug2.png
          79 kB
        4. bug1.png
          bug1.png
          135 kB

            searge [Mojang] Searge (Michael Stoyke)
            klepsauce KlepSauce
            Votes:
            7 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: