<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sun Jan 12 11:49:55 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-121] Blocks frequently reappear after having been mined</title>
                <link>https://bugs.mojang.com/browse/MC-121</link>
                <project id="10400" key="MC">Minecraft: Java Edition</project>
                    <description>&lt;p&gt;I usually play on a minefold.com server, and I&apos;ve noted that the latency is not always that great.  VERY often, when I mine blocks, they will reappear a few seconds later.  Sometimes after another few seconds they will disappear.  Sometimes I have to mine them again to really get rid of them.&lt;/p&gt;

&lt;p&gt;I am pretty sure this has to do with a high latency connection to the server because I&apos;ve noticed it gets worse when my connection has higher latency.&lt;/p&gt;</description>
                <environment>minefold.com server, Mac OSX 10.8</environment>
        <key id="11366">MC-121</key>
            <summary>Blocks frequently reappear after having been mined</summary>
                <type id="1" iconUrl="https://bugs.mojang.com/secure/viewavatar?size=xsmall&amp;avatarId=18903&amp;avatarType=issuetype">Bug</type>
                                    <status id="6" iconUrl="https://bugs.mojang.com/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="7">Invalid</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="smithsonj">John Smithson</reporter>
                        <labels>
                    </labels>
                <created>Wed, 24 Oct 2012 20:23:04 +0200</created>
                <updated>Wed, 29 Jan 2014 17:23:55 +0100</updated>
                            <resolved>Thu, 8 Nov 2012 06:30:28 +0100</resolved>
                                    <version>Minecraft 1.4.2</version>
                                                                        <votes>1</votes>
                                    <watches>2</watches>
                                                                            <comments>
                            <comment id="14413" author="dinnerbone" created="Sat, 27 Oct 2012 17:12:26 +0200"  >&lt;p&gt;Please don&apos;t mark something as &quot;effects 1.4.2&quot; if you haven&apos;t tried it in 1.4.2.&lt;/p&gt;</comment>
                            <comment id="13382" author="smithsonj" created="Thu, 25 Oct 2012 19:29:57 +0200"  >&lt;p&gt;I upgraded to 1.4.2 and no longer have this issue, even with a high latency connection of 550ms.  This can probably be closed.&lt;/p&gt;</comment>
                            <comment id="12649" author="mrooney" created="Thu, 25 Oct 2012 00:27:28 +0200"  >&lt;p&gt;I run into this problem quite a bit as well on multiplayer, and have latencies in the 200ms range as well. I don&apos;t think this is an unreasonable latency, so it would be great to have it handled slightly better if possible.&lt;/p&gt;</comment>
                            <comment id="12339" author="smithsonj" created="Wed, 24 Oct 2012 20:43:22 +0200"  >&lt;p&gt;It seems like it should be handled better though.  My latency isn&apos;t &lt;b&gt;that&lt;/b&gt; high, ~200ms.  That&apos;s not great, but it seems like it would be pretty common.&lt;/p&gt;</comment>
                            <comment id="12330" author="cloudy" created="Wed, 24 Oct 2012 20:37:06 +0200"  >&lt;p&gt;I don&apos;t really think this is a bug as such - it is the drawback to prediction in high latency connections.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                        <customfield id="customfield_10500" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Confirmation Status</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10300"><![CDATA[Unconfirmed]]></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_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i0mo9r:</customfieldvalue>

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