<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sat Jan 11 15:34:37 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>[MCPE-22360] Is this lag or a glitch?</title>
                <link>https://bugs.mojang.com/browse/MCPE-22360</link>
                <project id="10200" key="MCPE">Minecraft (Bedrock codebase)</project>
                    <description>&lt;p&gt;This is a short one. I do not know if this was lag or a glitch but I decided to report anyway! So, as in my other report, I was far from the spawn in my new found location to build a house and as I was building the floor, which was wooden planks, 3 blocks wouldn&apos;t render for about 5 seconds until I placed the fourth. They still lit up when I hovered my cursor over them but it looked just like air. As with my other issue, I did search before reporting so it is not my fault if it is a duplicate issue.&lt;/p&gt;</description>
            <key id="172464">MCPE-22360</key>
            <summary>Is this lag or a glitch?</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="5">Cannot Reproduce</resolution>
                                            <reporter username="_TheRat_">Jeremy Peter Nunn</reporter>
                        <labels>
                    </labels>
                <created>Sun, 4 Jun 2017 18:47:37 +0200</created>
                <updated>Tue, 17 Jul 2018 02:14:01 +0200</updated>
                            <resolved>Tue, 5 Jun 2018 18:03:22 +0200</resolved>
                                    <version>1.1.0.55</version>
                                                                        <votes>1</votes>
                                    <watches>1</watches>
                                                                            <comments>
                            <comment id="472050" author="morgwenna" created="Tue, 17 Jul 2018 02:14:01 +0200"  >&lt;p&gt;Auldrick. You are absolutely right on one score but I would say don&apos;t just assume the issue cannot be reproduced just because no-one from Mojang side commented on the call or no other players made a comment. This time I voted for it, started viewing it and was waiting for a response but it was then just closed with no opportunity to say whether the issue still exists.More than one call I was viewing and waiting for an answer on has been closed recently as cannot reproduce when the issue clearly still exists. Therefore, new issues for the same original problem had to be opened. If anyone analyses the stats then the answers are not accurate as 2 calls had been opened for the same issue because one was prematurely closed. On older calls cannot the status be set to awaiting response first and if no response within a certain time scale then set to cannot reproduce or another, more appropriate, closure reason? That way the people who are interested can update the issue and the issue properly kept open, or closed with possibly a more appropriate closure reason, as the case may be.&lt;/p&gt;</comment>
                            <comment id="465380" author="handlbar.rick@comcast.net" created="Sat, 30 Jun 2018 05:17:35 +0200"  >&lt;p&gt;Don&apos;t assume this problem is the same as the later bugs just because they sound similar. If it was, why did literally nobody else report it until 1.2? If it was the same bug, we should have seen many more reports of it on 1.1.&lt;/p&gt;

&lt;p&gt;We usually don&apos;t combine bugs just because their symptoms sound similar. If we did, we&apos;d run the risk of hiding one bug behind another. Then, when the fix for &lt;em&gt;that&lt;/em&gt; one doesn&apos;t fix &lt;em&gt;this&lt;/em&gt; one, we&apos;ve lost a lot of time that somebody could have been working on &lt;em&gt;this&lt;/em&gt; one, maybe even solved it earlier.&lt;/p&gt;

&lt;p&gt;For that matter, who knows if this was even a bug? The reporter himself admitted it might just be lag. For all we know, he was playing Minecraft while leaving a bunch of hoggy apps running in the background, or his device may have been overheating or malfunctioning. About 1/3 of reported bugs aren&apos;t actually bugs at all.&lt;/p&gt;

&lt;p&gt;Since there&apos;s no reliable evidence that anybody else had this problem, and we were not able to reproduce it, and the only person it affected is no longer responding to prompts for more information, and we can&apos;t even be sure there was ever a bug here in the first place, closing this ticket as &quot;Cannot Reproduce&quot; is the only sensible thing to do.&lt;/p&gt;</comment>
                            <comment id="465193" author="morgwenna" created="Fri, 29 Jun 2018 20:42:48 +0200"  >&lt;p&gt;Mega spud.. this another that has been closed prematurely. Possibly should be linked to the later bugs re memory especially near water but should not be closed as cannot be reproduced. Probably fixed at one time but memory issues is causing it to happen again.&lt;/p&gt;</comment>
                            <comment id="462477" author="morgwenna" created="Fri, 22 Jun 2018 02:47:37 +0200"  >&lt;p&gt;Was fixed at one point but 1.4.2 seriously bad because it has such memory issues - you can sometimes wait ages now for the blocks placed to render but considering I now get a wait bar when trying to open a chest this memory problem is minor. Not resolved but just another memory/performance issue.&lt;/p&gt;</comment>
                            <comment id="458484" author="mega_spud" created="Tue, 5 Jun 2018 18:03:22 +0200"  >&lt;p&gt;Cleaning up old tickets:  This ticket has not been updated recently (1 year+) so is being closed as &lt;em&gt;Cannot Reproduce&lt;/em&gt;.  If you feel this is still a valid issue then please comment, or create a new ticket following the &lt;a href=&quot;http://help.mojang.com/customer/portal/articles/801354-writing-helpful-bug-reports-for-minecraft&quot; title=&quot;How To Write helpful bug reports&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Issue Guidelines&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Quick Links&lt;/b&gt;:&lt;br/&gt;
&#128211; &lt;a href=&quot;http://help.mojang.com/customer/portal/articles/801354-writing-helpful-bug-reports-for-minecraft&quot; title=&quot;How To Write Awesome Tickets! &#128175;&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Issue Guidelines&lt;/a&gt; &amp;#8211; &#128172; &lt;a href=&quot;https://www.reddit.com/r/MCPE/&quot; title=&quot;Help From the Minecraft Community &#128377;&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Community Support&lt;/a&gt; &amp;#8211; &#128231; &lt;a href=&quot;https://feedback.minecraft.net/&quot; title=&quot;Feedback and Suggestions &#9997;&#65039;&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Feedback&lt;/a&gt; &amp;#8211; &#128214; &lt;a href=&quot;http://minecraft.gamepedia.com/Minecraft_Wiki&quot; title=&quot;Official Minecraft Wiki &#127891;&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Game Wiki&lt;/a&gt;&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_11300" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>Operating System Version</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>5.3.3.0</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10402" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Platform</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10604"><![CDATA[Tablet - Android - Amazon Kindle Fire HD]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i0rpvj:</customfieldvalue>

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