<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sun Jan 12 11:54:20 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-1406] Server and client can disagree on block placement range</title>
                <link>https://bugs.mojang.com/browse/MC-1406</link>
                <project id="10400" key="MC">Minecraft: Java Edition</project>
                    <description>&lt;p&gt;Sometimes when placing a block as far away as possible, it will flicker into existence for a brief moment and then disappear again. This affects survival and creative. In survival the item pops back into your inventory.&lt;/p&gt;

&lt;p&gt;To reproduce the problem, load the attached world and, without moving, place the anvil you are holding against the block you are looking at (the first stone block above the portal).&lt;/p&gt;

&lt;p&gt;The bug first appeared in 1.3.&lt;/p&gt;</description>
                <environment></environment>
        <key id="12736">MC-1406</key>
            <summary>Server and client can disagree on block placement range</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="-1">Unassigned</assignee>
                                    <reporter username="sycholic">Sycholic</reporter>
                        <labels>
                    </labels>
                <created>Wed, 31 Oct 2012 01:06:05 +0100</created>
                <updated>Wed, 29 Oct 2014 13:18:41 +0100</updated>
                            <resolved>Fri, 24 Oct 2014 23:05:42 +0200</resolved>
                                    <version>Minecraft 1.4.2</version>
                    <version>Minecraft 1.4.7</version>
                    <version>Minecraft 1.5.1</version>
                    <version>Minecraft 1.5.2</version>
                    <version>Minecraft 1.7.4</version>
                    <version>Minecraft 14w05b</version>
                    <version>Minecraft 14w06b</version>
                    <version>Minecraft 14w07a</version>
                    <version>Minecraft 14w08a</version>
                    <version>Minecraft 1.7.5</version>
                                    <fixVersion>Minecraft 1.8</fixVersion>
                                                        <votes>4</votes>
                                    <watches>8</watches>
                                                                            <comments>
                            <comment id="206434" author="galaxy_2alex" created="Wed, 29 Oct 2014 13:18:41 +0100"  >&lt;p&gt;Let&apos;s analyze the &quot;Incomplete&quot; message I give out:&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;This ticket is &lt;em&gt;incomplete&lt;/em&gt; without the requested information, no response has been received within a reasonable time and we are assuming this is no longer an issue. If you are still experiencing this issue, we can reopen it at your request.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;&quot;we are assuming this is no longer an issue&quot; = Can be either seen as &quot;this has been Fixed in a random version&quot; or &quot;this was once an issue of some sorts, but it is handled as something intended now&quot;.&lt;/p&gt;

&lt;p&gt;&quot;we can reopen it at your request.&quot; = We are actually serious with this, for my part, I am getting E-Mail for every response to a ticket I closed as Incomplete, and therefor I can see if someone comments on it.&lt;/p&gt;

&lt;p&gt;I agree that this is a farily new method, but at the current state, the bug tracker as a whole seems a bit unorganized. I&apos;ve seen quite a few duplicates that were not detected as one. My plan for the future is to do this every big update, and what I am expecting at least from anyone reporting a bug is that he checks it in every big release (next one would be 1.9). Just reporting a bug and thinking that everything would resolve around it completely automatical is not enough.&lt;/p&gt;

&lt;p&gt;All bug tracker moderators are volunteers by the way.&lt;/p&gt;</comment>
                            <comment id="206409" author="immibis" created="Wed, 29 Oct 2014 01:50:27 +0100"  >&lt;p&gt;I have to agree with @Sycholic about passing the buck. Saying &quot;Nobody has re-confirmed this in the last 2 years, therefore it&apos;s invalid&quot; is just sticking your head in the sand (and by &quot;you&quot; I mean Mojang).&lt;/p&gt;

&lt;p&gt;&quot;Pending information&quot; or similar would be a valid status, but only if there&apos;s someone at Mojang whose job it is to confirm bugs. Otherwise, it&apos;s just another way to disown responsibility.&lt;/p&gt;

&lt;p&gt;TL;DR: Getting bugs fixed once they are reported is Mojang&apos;s responsibility. If I am expected to help Mojang, then I expect to be paid for my time, like everyone else working for Mojang.&lt;/p&gt;</comment>
                            <comment id="205051" author="galaxy_2alex" created="Fri, 24 Oct 2014 23:05:42 +0200"  >&lt;p&gt;Just going to resolve it to fixed in 1.8. 1.7.x versions are no longer supported.&lt;/p&gt;</comment>
                            <comment id="205047" author="sycholic" created="Fri, 24 Oct 2014 22:56:31 +0200"  >&lt;p&gt;Btw cant add any 1.7.x versions.  The problem seems to stop @ 1.8 as destroy and placement block distances changes from 1.7.10 to 1.8.  Not sure if this &apos;solved&apos; the problem or just started to &apos;mask&apos; it, as I cant repo it on 1.8. or 1.8.1-pre2 the distance from placing a block vs destroying one is not the same anymore.  I cant place blocks @ the same distance as the farthest point that I can destroy one now.   Offsetting placement about .05m in distance seems to have changed it all, atleast for me.  When the server bugged out on block removal or placement, it was always happening when I was placing blocks at the edge of the highlighted range.  &lt;/p&gt;</comment>
                            <comment id="205035" author="galaxy_2alex" created="Fri, 24 Oct 2014 22:31:57 +0200"  >&lt;p&gt;No problem. I am just going through around 3,800 tickets, and try to sort out those that are completely orphaned.&lt;/p&gt;</comment>
                            <comment id="205032" author="sycholic" created="Fri, 24 Oct 2014 22:28:34 +0200"  >&lt;p&gt;okay sweet I&apos;ll dig some more into it and get back to yas.  Sorry if I was short with yas also, everyone around me getting their heads bit off today with me &lt;sup&gt;_&lt;/sup&gt;&lt;/p&gt;</comment>
                            <comment id="205020" author="galaxy_2alex" created="Fri, 24 Oct 2014 22:11:17 +0200"  >&lt;p&gt;Reopened, gave you reporter access to adjust the versions.&lt;br/&gt;
@immibis: Issue can be retaken by you at any time, just leave a comment.&lt;/p&gt;</comment>
                            <comment id="205016" author="sycholic" created="Fri, 24 Oct 2014 22:06:00 +0200"  >&lt;p&gt;Still happens for 1.7.10 already seen it.  Asking someone to update a 2+ year old ticket is not acceptable either.  I personally have had blocks broken and then still are physically there to the server but client side they are gone and vise versa. I have not see it on 1.8.x nor have I looked for it I only drops my comment because I was on a the watch list when this was closed.   I&apos;ll do more forceful testing to get blocks to glitch out possibly this weekend also see if it still happens with 1.8.x but it definitely exists for all versions up to 1.8  And as for a resolution, incomplete is not acceptable either as no fix was created for this problem so there is no resolution, not incomplete or partial but &apos;none&apos; or &apos;not applicable&apos;.  Passing the buck like that is not cool either, seriously.&lt;/p&gt;</comment>
                            <comment id="204967" author="galaxy_2alex" created="Fri, 24 Oct 2014 19:57:56 +0200"  >&lt;p&gt;This ticket is &lt;em&gt;incomplete&lt;/em&gt; without the requested information, no response has been received within a reasonable time and we are assuming the issue has been resolved. If you are still experiencing this issue, we can reopen it at your request.&lt;/p&gt;</comment>
                            <comment id="180214" author="ezekielelin" created="Sat, 26 Jul 2014 20:43:12 +0200"  >&lt;p&gt;Is this still a concern in the latest Minecraft version &lt;b&gt;14w30c&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="144211" author="hartspoon" created="Sun, 2 Mar 2014 19:41:12 +0100"  >&lt;p&gt;Still a concern in 14w08a.&lt;/p&gt;</comment>
                            <comment id="67668" author="sycholic" created="Tue, 21 May 2013 09:41:06 +0200"  >&lt;p&gt;confirmed. 1.5.2 both vanilla and bukkit server no plugins SP/MP any game mode&lt;br/&gt;
&lt;a href=&quot;http://www.youtube.com/watch?v=rd9DECFqwNk&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://www.youtube.com/watch?v=rd9DECFqwNk&lt;/a&gt;&lt;br/&gt;
Also now it also drops items from them glitching out on the placement.  Example Ive had a random # stack drop of xp potions after the placed block dissapeared (no I cant say which block as its kinda a serious exploit in the game mechanics).&lt;/p&gt;</comment>
                            <comment id="65819" author="ileon" created="Fri, 10 May 2013 18:26:01 +0200"  >&lt;p&gt;confirm in 1.5.2&lt;/p&gt;</comment>
                            <comment id="57789" author="ileon" created="Fri, 29 Mar 2013 13:59:15 +0100"  >&lt;p&gt;confirm in 1.5.1&lt;/p&gt;</comment>
                            <comment id="40455" author="icetrailer" created="Sun, 27 Jan 2013 20:42:41 +0100"  >&lt;p&gt;I can confirm that too, and I hat that issue, &#242;.&#243;&lt;/p&gt;</comment>
                            <comment id="22521" author="jeffreykog" created="Sat, 17 Nov 2012 13:44:18 +0100"  >&lt;p&gt;Can confirm this bug. I&apos;ve seen this happen before 1.3&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10102">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="20514">MC-7706</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="46882">MC-27095</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="12765">MC-1435</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="11487" name="New World.7z" size="4403657" author="immibis" created="Wed, 31 Oct 2012 01:06:06 +0100"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                <customfield id="customfield_10701" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>CHK</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Tue, 5 Feb 2013 01:04: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_11100" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Linked</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                <customfield id="customfield_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i0nabz:</customfieldvalue>

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