<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sun Jan 12 12:07:09 UTC 2025

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Mojang Studios Jira</title>
    <link>https://bugs.mojang.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en</language>    <build-info>
        <version>9.12.2</version>
        <build-number>9120002</build-number>
        <build-date>10-01-2024</build-date>
    </build-info>


<item>
            <title>[MC-5215] MobSpawner &quot;MaximumNearbyEntity&quot; Tag only has maximum range of 4 above and 4 below</title>
                <link>https://bugs.mojang.com/browse/MC-5215</link>
                <project id="10400" key="MC">Minecraft: Java Edition</project>
                    <description>&lt;p&gt;When configuring custom spawners, the &quot;MaximumNearbyEntity&quot; 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 &apos;&quot;SpawnRange&quot; +1 centred around the spawner block&apos;. However, setting the &quot;SpawnRange&quot; 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&apos;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.&lt;/p&gt;</description>
                <environment></environment>
        <key id="17790">MC-5215</key>
            <summary>MobSpawner &quot;MaximumNearbyEntity&quot; Tag only has maximum range of 4 above and 4 below</summary>
                <type id="1" iconUrl="https://bugs.mojang.com/secure/viewavatar?size=xsmall&amp;avatarId=18903&amp;avatarType=issuetype">Bug</type>
                                    <status id="5" iconUrl="https://bugs.mojang.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="searge">[Mojang] Searge (Michael Stoyke)</assignee>
                                    <reporter username="klepsauce">KlepSauce</reporter>
                        <labels>
                            <label>entity</label>
                            <label>maxnearbyentities</label>
                            <label>range</label>
                            <label>spawner</label>
                    </labels>
                <created>Sat, 22 Dec 2012 16:16:29 +0100</created>
                <updated>Fri, 22 Aug 2014 14:45:50 +0200</updated>
                            <resolved>Wed, 20 Aug 2014 13:40:21 +0200</resolved>
                                    <version>Minecraft 1.4.6</version>
                    <version>Minecraft 1.6.1</version>
                    <version>Minecraft 1.7.2</version>
                    <version>Minecraft 1.7.4</version>
                    <version>Minecraft 14w02b</version>
                    <version>Minecraft 14w02c</version>
                    <version>Minecraft 14w05b</version>
                    <version>Minecraft 14w06b</version>
                    <version>Minecraft 14w07a</version>
                    <version>Minecraft 14w08a</version>
                    <version>Minecraft 1.7.5</version>
                    <version>Minecraft 1.7.9</version>
                    <version>Minecraft 14w20a</version>
                    <version>Minecraft 14w20b</version>
                    <version>Minecraft 14w21b</version>
                    <version>Minecraft 14w25a</version>
                    <version>Minecraft 1.7.10-pre4</version>
                    <version>Minecraft 14w25b</version>
                    <version>Minecraft 14w26b</version>
                    <version>Minecraft 1.7.10</version>
                    <version>Minecraft 14w28a</version>
                    <version>Minecraft 14w30c</version>
                    <version>Minecraft 14w31a</version>
                    <version>Minecraft 14w32a</version>
                    <version>Minecraft 14w32b</version>
                    <version>Minecraft 14w32c</version>
                    <version>Minecraft 14w32d</version>
                    <version>Minecraft 14w33a</version>
                    <version>Minecraft 14w33c</version>
                    <version>Minecraft 14w34a</version>
                    <version>Minecraft 14w34b</version>
                    <version>Minecraft 14w34c</version>
                                    <fixVersion>Minecraft 14w34d</fixVersion>
                                                        <votes>7</votes>
                                    <watches>4</watches>
                                                                            <comments>
                            <comment id="192290" author="jelle" created="Fri, 22 Aug 2014 14:45:24 +0200"  >&lt;p&gt;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...&lt;/p&gt;

&lt;p&gt;But it&apos;s fixed now&lt;/p&gt;</comment>
                            <comment id="190687" author="qmagnet" created="Tue, 19 Aug 2014 15:01:32 +0200"  >&lt;p&gt;Confirmed for 14w34b&lt;/p&gt;</comment>
                            <comment id="188760" author="ezekielelin" created="Thu, 14 Aug 2014 15:43:07 +0200"  >&lt;p&gt;Not that I know of&lt;/p&gt;</comment>
                            <comment id="188577" author="qmagnet" created="Thu, 14 Aug 2014 03:23:03 +0200"  >&lt;p&gt;Confirmed for 14w33a. Does no one use custom spawners anymore?&lt;/p&gt;</comment>
                            <comment id="186638" author="qmagnet" created="Sat, 9 Aug 2014 01:05:54 +0200"  >&lt;p&gt;Confirmed for 14w32d&lt;/p&gt;</comment>
                            <comment id="185783" author="qmagnet" created="Thu, 7 Aug 2014 18:18:23 +0200"  >&lt;p&gt;Confirmed for 14w32b&lt;/p&gt;</comment>
                            <comment id="185387" author="qmagnet" created="Thu, 7 Aug 2014 01:39:05 +0200"  >&lt;p&gt;Confirmed 14w32a&lt;/p&gt;</comment>
                            <comment id="182742" author="qmagnet" created="Thu, 31 Jul 2014 01:17:02 +0200"  >&lt;p&gt;Confirmed for 14w31a&lt;/p&gt;</comment>
                            <comment id="172846" author="qmagnet" created="Thu, 10 Jul 2014 15:51:41 +0200"  >&lt;p&gt;Confirmed 14w28a&lt;/p&gt;</comment>
                            <comment id="167943" author="qmagnet" created="Wed, 25 Jun 2014 19:46:40 +0200"  >&lt;p&gt;Confirmed for 14w26b&lt;/p&gt;</comment>
                            <comment id="164863" author="qmagnet" created="Thu, 19 Jun 2014 13:03:27 +0200"  >&lt;p&gt;Confirmed for 14w25a&lt;/p&gt;</comment>
                            <comment id="158263" author="qmagnet" created="Sat, 17 May 2014 15:01:11 +0200"  >&lt;p&gt;Confirmed for 14w20b&lt;/p&gt;</comment>
                            <comment id="144542" author="qmagnet" created="Tue, 4 Mar 2014 15:19:52 +0100"  >&lt;p&gt;Still an issue in 14w08a&lt;/p&gt;</comment>
                            <comment id="130543" author="ezekielelin" created="Sat, 11 Jan 2014 17:17:26 +0100"  >&lt;p&gt;Thanks Jesper&lt;/p&gt;</comment>
                            <comment id="130540" author="jespertheend" created="Sat, 11 Jan 2014 17:11:04 +0100"  >&lt;p&gt;confirmed for &lt;b&gt;14w02c&lt;/b&gt;&lt;/p&gt;</comment>
                            <comment id="130525" author="ezekielelin" created="Sat, 11 Jan 2014 16:55:30 +0100"  >&lt;p&gt;Is this still a concern in the latest Minecraft version &lt;b&gt;14w02c&lt;/b&gt;? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.&lt;/p&gt;</comment>
                            <comment id="121444" author="jespertheend" created="Tue, 26 Nov 2013 21:21:08 +0100"  >&lt;p&gt;confirmed for &lt;b&gt;1.7.2&lt;/b&gt; Launcher &lt;b&gt;1.3.4&lt;/b&gt;&lt;/p&gt;</comment>
                            <comment id="121430" author="talven81" created="Tue, 26 Nov 2013 21:04:43 +0100"  >&lt;p&gt;Is this still a concern in the &lt;em&gt;current Minecraft version&lt;/em&gt; &lt;b&gt;1.7.2&lt;/b&gt; / Launcher version &lt;b&gt;1.3.4&lt;/b&gt; ? If so, please &lt;em&gt;update the affected versions&lt;/em&gt; in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.&lt;/p&gt;</comment>
                            <comment id="84708" author="jespertheend" created="Sun, 7 Jul 2013 00:15:22 +0200"  >&lt;p&gt;confirmed for 1.6.1&lt;br/&gt;
btw minecraft wiki says the height is always 8, but I still think this should be fixed yes.&lt;/p&gt;</comment>
                            <comment id="84561" author="qmagnet" created="Sat, 6 Jul 2013 20:21:57 +0200"  >&lt;p&gt;I&apos;m having this issue.  I have tested this in 1.6.1.  I&apos;ll include some photos to explain the problem.  But maxnearbyenemies does not appear to follow the setting over 5 blocks from the SpawnData.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;I should clarify that I set the Spawn position of the silverfish to where that glowstone is.&lt;/p&gt;</comment>
                            <comment id="46699" author="bugi74" created="Wed, 20 Feb 2013 10:51:17 +0100"  >&lt;p&gt;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?)&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;Without proof for otherwise, I&apos;d say &quot;invalid&quot;.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10103">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="17407">MC-4855</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="35831" name="bug1.png" size="137931" author="qmagnet" created="Sat, 6 Jul 2013 20:21:57 +0200"/>
                            <attachment id="35832" name="bug2.png" size="81073" author="qmagnet" created="Sat, 6 Jul 2013 20:21:57 +0200"/>
                            <attachment id="35833" name="bug3.png" size="262281" author="qmagnet" created="Sat, 6 Jul 2013 20:21:57 +0200"/>
                            <attachment id="35834" name="bug4.png" size="287124" author="qmagnet" created="Sat, 6 Jul 2013 20:21:57 +0200"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                <customfield id="customfield_10701" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>CHK</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Mon, 24 Feb 2014 22:41:00 +0100</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10500" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Confirmation Status</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10302"><![CDATA[Community Consensus]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_11700" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10501" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Game Mode</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10305"><![CDATA[Creative]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_11100" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Linked</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                <customfield id="customfield_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i0dauv:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    </customfields>
    </item>
</channel>
</rss>