[MC-5215] MobSpawner "MaximumNearbyEntity" Tag only has maximum range of 4 above and 4 below Created: 22/Dec/12  Updated: 22/Aug/14  Resolved: 20/Aug/14

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: 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
Fix Version/s: Minecraft 14w34d

Type: Bug
Reporter: KlepSauce Assignee: [Mojang] Searge (Michael Stoyke)
Resolution: Fixed Votes: 7
Labels: entity, maxnearbyentities, range, spawner

Attachments: PNG File bug1.png     PNG File bug2.png     PNG File bug3.png     PNG File bug4.png    
Issue Links:
Relates
relates to MC-4855 Mob spawners miss a row on X and Z ax... Resolved
CHK:
Confirmation Status: Community Consensus
Game Mode: Creative

 Description   

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.



 Comments   
Comment by Jelle [ 22/Aug/14 ]

I used to use them, but then it started doing things like this and when I now think about it, this is exactly what most of my spawners did...

But it's fixed now

Comment by qmagnet [ 19/Aug/14 ]

Confirmed for 14w34b

Comment by [Mod] Ezekiel (ezfe) [ 14/Aug/14 ]

Not that I know of

Comment by qmagnet [ 14/Aug/14 ]

Confirmed for 14w33a. Does no one use custom spawners anymore?

Comment by qmagnet [ 08/Aug/14 ]

Confirmed for 14w32d

Comment by qmagnet [ 07/Aug/14 ]

Confirmed for 14w32b

Comment by qmagnet [ 06/Aug/14 ]

Confirmed 14w32a

Comment by qmagnet [ 30/Jul/14 ]

Confirmed for 14w31a

Comment by qmagnet [ 10/Jul/14 ]

Confirmed 14w28a

Comment by qmagnet [ 25/Jun/14 ]

Confirmed for 14w26b

Comment by qmagnet [ 19/Jun/14 ]

Confirmed for 14w25a

Comment by qmagnet [ 17/May/14 ]

Confirmed for 14w20b

Comment by qmagnet [ 04/Mar/14 ]

Still an issue in 14w08a

Comment by [Mod] Ezekiel (ezfe) [ 11/Jan/14 ]

Thanks Jesper

Comment by Jesper the End [ 11/Jan/14 ]

confirmed for 14w02c

Comment by [Mod] Ezekiel (ezfe) [ 11/Jan/14 ]

Is this still a concern in the latest Minecraft version 14w02c? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

Comment by Jesper the End [ 26/Nov/13 ]

confirmed for 1.7.2 Launcher 1.3.4

Comment by Talven81 [ 26/Nov/13 ]

Is this still a concern in the current Minecraft version 1.7.2 / Launcher version 1.3.4 ? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

Comment by Jesper the End [ 06/Jul/13 ]

confirmed for 1.6.1
btw minecraft wiki says the height is always 8, but I still think this should be fixed yes.

Comment by qmagnet [ 06/Jul/13 ]

I'm having this issue. I have tested this in 1.6.1. I'll include some photos to explain the problem. But maxnearbyenemies does not appear to follow the setting over 5 blocks from the SpawnData.

Both monster spawners share the same properties. The left spawner is 5 blocks higher than the SpawnData position but the right spawner is 6 blocks higher than SpawnData position. The higher one will constantly spawn. The height is not affected but the MaxNearbyEnemies setting.

I should clarify that I set the Spawn position of the silverfish to where that glowstone is.

Comment by Markku [ 20/Feb/13 ]

I could not find a mention of spawnrange + 1, let alone that for vertical direction, in the wiki, but only constant values for each. (Am I missing something?)

In any case, the code in version 1.4.7 has the horizontal spawn and check ranges both based on spawn range, while the vertically both have constant values (-1 to +1 for spawning, -4 to +5 for checking). In all directions, the check range is at least twice as large as the spawning range. Thus, the described bug should not be possible.

Without proof for otherwise, I'd say "invalid".

Generated at Sun Jan 12 12:07:09 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.