<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sat Jan 11 15:02:57 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-14233] Redstone components update upon reloading a world</title>
                <link>https://bugs.mojang.com/browse/MCPE-14233</link>
                <project id="10200" key="MCPE">Minecraft (Bedrock codebase)</project>
                    <description>&lt;p&gt;Upon loading a world, redstone components update. The redstone may change based on an unloaded chunk, causeing it to turn off when it should be being powered by something in the unloaded chunk next to it. To reproduce: make a long line of Redstone with repeaters, power &lt;br/&gt;
one end, then stand at the other end and lower your render distance. Then reload the world. The redstone will turn off, then turn back on as you load the component powering it. This affects all redstone components that I am aware of, including pistons. It tends to break contraptions as one half may update while the other is unloaded, often sending redstone contraptions into a clock.&lt;/p&gt;</description>
            <key id="139860">MCPE-14233</key>
            <summary>Redstone components update upon reloading a world</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="3">Duplicate</resolution>
                                            <reporter username="ProNoob135">Tavish McEwen</reporter>
                        <labels>
                            <label>redstone</label>
                            <label>redstone-update</label>
                            <label>world-loading</label>
                    </labels>
                <created>Mon, 25 Apr 2016 22:10:23 +0200</created>
                <updated>Tue, 25 Oct 2016 16:26:05 +0200</updated>
                            <resolved>Tue, 25 Oct 2016 14:41:35 +0200</resolved>
                                    <version>0.15.0 Realms Alpha build 2</version>
                    <version>0.15.0 Beta build 1</version>
                    <version>0.15.0 Beta build 3</version>
                    <version>0.15.6</version>
                    <version>0.15.10</version>
                    <version>0.15.90.8</version>
                                                                        <votes>3</votes>
                                    <watches>6</watches>
                                                                            <comments>
                            <comment id="334284" author="zebulanstanphill@gmail.com" created="Mon, 10 Oct 2016 03:03:29 +0200"  >&lt;p&gt;Affects 0.15.90.8 (0.16.0 beta build 5). Again, shouldn&apos;t this issue be closed since it is a duplicate of &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-13608&quot; title=&quot;Redstone components update when world is reloaded&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-13608&quot;&gt;&lt;del&gt;MCPE-13608&lt;/del&gt;&lt;/a&gt;?&lt;/p&gt;</comment>
                            <comment id="331143" author="pronoob135" created="Mon, 26 Sep 2016 16:12:35 +0200"  >&lt;p&gt;Yes&lt;/p&gt;</comment>
                            <comment id="327648" author="zebulanstanphill@gmail.com" created="Tue, 30 Aug 2016 23:25:00 +0200"  >&lt;p&gt;Isn&apos;t this a duplicate of (or at least related to) &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-13608&quot; title=&quot;Redstone components update when world is reloaded&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-13608&quot;&gt;&lt;del&gt;MCPE-13608&lt;/del&gt;&lt;/a&gt;?&lt;/p&gt;</comment>
                            <comment id="325067" author="pronoob135" created="Fri, 12 Aug 2016 03:55:22 +0200"  >&lt;p&gt;Confirmed for 0.15.6&lt;/p&gt;</comment>
                            <comment id="325032" author="pronoob135" created="Thu, 11 Aug 2016 22:45:51 +0200"  >&lt;p&gt;The main issue (things breaking because they are partly unloaded while one part updates) would probably be fixed if &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-15779&quot; title=&quot;Redstone does not load chunks&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-15779&quot;&gt;&lt;del&gt;MCPE-15779&lt;/del&gt;&lt;/a&gt; (redstone not loading chunks) was fixed, but this &quot;feature&quot; doesn&apos;t really help anything and should be removed anyways.&lt;/p&gt;</comment>
                            <comment id="324667" author="azelef" created="Wed, 10 Aug 2016 18:48:54 +0200"  >&lt;p&gt;Confirmed in 0.15.4, please reopen.&lt;/p&gt;</comment>
                            <comment id="324039" author="aman4700" created="Mon, 8 Aug 2016 03:49:58 +0200"  >&lt;p&gt;Please respond and add the current version if you can reproduce this issue.&lt;/p&gt;</comment>
                            <comment id="313887" author="azelef" created="Wed, 15 Jun 2016 15:44:07 +0200"  >&lt;p&gt;Can confirm it affects pistons in 0.15.1 beta 1. The flying machine in &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-15475&quot; title=&quot;Piston mechanics change at chunk borders&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-15475&quot;&gt;&lt;del&gt;MCPE-15475&lt;/del&gt;&lt;/a&gt; and &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-15476&quot; title=&quot;Stuck pistons stay stuck forever&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-15476&quot;&gt;&lt;del&gt;MCPE-15476&lt;/del&gt;&lt;/a&gt; goes one block forward when reloaded.&lt;/p&gt;</comment>
                            <comment id="309994" author="pronoob135" created="Sat, 4 Jun 2016 02:44:13 +0200"  >&lt;p&gt;Confirmed for 0.15 b1&lt;/p&gt;</comment>
                            <comment id="301796" author="depressed-pho" created="Wed, 27 Apr 2016 07:08:46 +0200"  >&lt;p&gt;Ah, I see. The root cause of the problem is that the powered state of redstone components (like repeaters and comparators) is not saved when they are unloaded, i.e. they completely forget the fact that they were powered before getting unloaded. When they are loaded again, all the components in that chunk receive redstone updates to recover their previous state... with a fatal delay that completely messes up any non-trivial redstone circuitries. So yes, this is indeed a &lt;em&gt;partial&lt;/em&gt; duplicate of &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-13714&quot; title=&quot;When opening a world, redstone takes a couple of ticks to update.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-13714&quot;&gt;&lt;del&gt;MCPE-13714&lt;/del&gt;&lt;/a&gt; which is a general case of &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-13270&quot; title=&quot;Comparators measuring a non-empty container momentarily stop emitting power upon reloading&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-13270&quot;&gt;&lt;del&gt;MCPE-13270&lt;/del&gt;&lt;/a&gt; and &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-13413&quot; title=&quot;Active unpowered locked repeaters become inactive after reloading&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-13413&quot;&gt;&lt;del&gt;MCPE-13413&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="301707" author="luisrobles" created="Tue, 26 Apr 2016 16:20:34 +0200"  >&lt;p&gt;Maybe a Duplicate of &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-13714&quot; title=&quot;When opening a world, redstone takes a couple of ticks to update.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-13714&quot;&gt;&lt;del&gt;MCPE-13714&lt;/del&gt;&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="301683" author="pronoob135" created="Tue, 26 Apr 2016 09:56:31 +0200"  >&lt;p&gt;No, it just has to not give them a block update. Then they won&apos;t change because they don&apos;t check if they are being powered, and there is even less lag upon loading a world. This bug does not occur in PC edition.&lt;/p&gt;</comment>
                            <comment id="301682" author="depressed-pho" created="Tue, 26 Apr 2016 09:51:39 +0200"  >&lt;p&gt;This is very likely to be an intended behavior, because in order to &quot;fix&quot; this, the game must load each and every chunk of the world upon reloading, and continue processing all those redstone components no matter how far you are away from them. I don&apos;t think this is feasible.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10102">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="134789">MCPE-13608</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10103">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="135252">MCPE-13714</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="144418">MCPE-15779</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                <customfield id="customfield_10701" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>CHK</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Wed, 19 Oct 2016 00:21:00 +0200</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10500" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Confirmation Status</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10303"><![CDATA[Confirmed]]></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_11300" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>Operating System Version</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Android 5.1.1</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10402" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Platform</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10718"><![CDATA[Phone - Android - LG Other (Specify in description)]]></customfieldvalue>

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

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