<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sat Jan 11 15:10:58 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-16286] Pistons are incorrectly activated when adjacent to a block that is adjacent to an activation-power source, but the block is not powered by the power source</title>
                <link>https://bugs.mojang.com/browse/MCPE-16286</link>
                <project id="10200" key="MCPE">Minecraft (Bedrock codebase)</project>
                    <description>&lt;p&gt;Pistons are incorrectly activated when adjacent to a block that is adjacent to a power source that emits activation power (except for redstone blocks, which seem to be a special case), but the block is not powered by the power source.&lt;/p&gt;

&lt;p&gt;Confirmed to affect pistons that are adjacent to blocks that are adjacent to redstone torches, observers, buttons, levers, pressure plates, and detector rails.&lt;/p&gt;

&lt;p&gt;Ironically, this bug causes pistons to be powered by observers as if observers output strong power instead of activation power. So this bug actually makes observers more consistent with the Java edition when it comes to pistons. (They still only technically output activation power, though, so this is a piston bug.)&lt;/p&gt;

&lt;p&gt;&lt;b&gt;To Reproduce:&lt;/b&gt;&lt;br/&gt;
Place any block that strongly powers at least one other block and pay attention to the blocks that it also activates.&lt;br/&gt;
Place pistons adjacent to the activated blocks taking care to ensure they are not adjacent to any strongly powered blocks.&lt;br/&gt;
Observe that the pistons (regular or sticky) activate when they should not.&lt;/p&gt;

&lt;p&gt;We dug a bit deeper and have determined this bug affects both regular pistons and sticky pistons.&lt;/p&gt;

&lt;p&gt;This bug affects any power source (redstone torch, lever, trapped chest).  Basically any block that powers at least one other block.  This bug does not affect blocks that merely activate other blocks (i.e. redstone block, buttons).&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Original Report:&lt;/em&gt; A torch can power a piston sideways through a block. The torch can power the piston sideways no matter how it placed. The torch sends power through the block but the block is not powered. &lt;/p&gt;</description>
            <key id="146763">MCPE-16286</key>
            <summary>Pistons are incorrectly activated when adjacent to a block that is adjacent to an activation-power source, but the block is not powered by the power source</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>
                                            <reporter username="jahunt78">Jason Hunt</reporter>
                        <labels>
                            <label>activation-power</label>
                            <label>button</label>
                            <label>detector_rail</label>
                            <label>lever</label>
                            <label>observer</label>
                            <label>piston</label>
                            <label>pressure_plate</label>
                            <label>redstone</label>
                            <label>redstone_torch</label>
                    </labels>
                <created>Wed, 20 Jul 2016 04:35:13 +0200</created>
                <updated>Wed, 3 May 2017 22:54:37 +0200</updated>
                            <resolved>Wed, 7 Dec 2016 23:23:26 +0100</resolved>
                                    <version>0.15.3</version>
                    <version>0.15.6</version>
                    <version>0.15.90.2</version>
                    <version>0.15.90.7</version>
                    <version>0.15.9</version>
                    <version>0.15.10</version>
                    <version>0.16.0</version>
                    <version>0.16.1</version>
                    <version>0.17.0.1</version>
                    <version>0.16.2</version>
                    <version>1.0.0.0</version>
                                    <fixVersion>1.0.0.1</fixVersion>
                                                        <votes>6</votes>
                                    <watches>8</watches>
                                                                            <comments>
                            <comment id="336318" author="zebulanstanphill@gmail.com" created="Fri, 21 Oct 2016 18:53:08 +0200"  >&lt;p&gt;This bug doesn&apos;t just affect pistons next to blocks adjacent to redstone torches. It also affects pistons adjacent to blocks being powered by observers. See &lt;a href=&quot;https://youtu.be/m0Mee4aBcBs&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://youtu.be/m0Mee4aBcBs&lt;/a&gt; . Can confirm this behavior occurs in 0.16.0.&lt;/p&gt;</comment>
                            <comment id="333302" author="zebulanstanphill@gmail.com" created="Wed, 5 Oct 2016 17:05:07 +0200"  >&lt;p&gt;Affects 0.15.10. (Tested on Windows 10.)&lt;/p&gt;</comment>
                            <comment id="330443" author="nighter" created="Tue, 20 Sep 2016 14:08:05 +0200"  >&lt;p&gt;This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided). &lt;/p&gt;</comment>
                            <comment id="329929" author="zebulanstanphill@gmail.com" created="Fri, 16 Sep 2016 16:12:03 +0200"  >&lt;p&gt;Affects 0.16.0 beta build 4 AKA 0.15.90.7.&lt;/p&gt;</comment>
                            <comment id="328611" author="zebulanstanphill@gmail.com" created="Mon, 5 Sep 2016 01:19:44 +0200"  >&lt;p&gt;Affects 0.15.90.2.&lt;/p&gt;</comment>
                            <comment id="327063" author="zebulanstanphill@gmail.com" created="Sat, 27 Aug 2016 04:21:23 +0200"  >&lt;p&gt;This is definitely a bug. The block to which a torch is attached to should not be powered, and the block directly above the torch should receive strong power, but all other adjacent blocks should recieve weak power.&lt;/p&gt;

&lt;p&gt;As demonstrated in Screenshot_2016-07-19-21-49-08.png, the block adjacent to the torch is only weakly powered, and so the piston should not be powered. If the block was strongly powered, the redstoen dust on top of the block would also be powered like the piston.&lt;/p&gt;

&lt;p&gt;Perhaps this is related to &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-15195&quot; title=&quot;Restone torches on piston power piston&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-15195&quot;&gt;&lt;del&gt;MCPE-15195&lt;/del&gt;&lt;/a&gt; &amp;amp; &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-16283&quot; title=&quot;Redstone torch burn/turn off when placed on the side of a piston&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-16283&quot;&gt;&lt;del&gt;MCPE-16283&lt;/del&gt;&lt;/a&gt; - they all involve redstone torches and pistons.&lt;/p&gt;</comment>
                            <comment id="321458" author="rplatham" created="Wed, 20 Jul 2016 15:04:55 +0200"  >&lt;p&gt;As in Screenshot_2016-07-20-08-47-33, piston touching the blocks to the side of the redstone torch should not activate. (The piston touching the block above the torch works as intended and the redstone lamps built to the right work as intended).&lt;/p&gt;</comment>
                            <comment id="321423" author="jahunt78" created="Wed, 20 Jul 2016 07:01:29 +0200"  >&lt;p&gt;I have passed on whether it&apos;s intended or not hopefully I will get an answer back.&lt;/p&gt;</comment>
                            <comment id="321422" author="plantseed" created="Wed, 20 Jul 2016 06:55:39 +0200"  >&lt;p&gt;I think the block acts like redstone wire, but it redirect the power to pistons 6 ways.&lt;/p&gt;</comment>
                            <comment id="321417" author="jahunt78" created="Wed, 20 Jul 2016 05:50:30 +0200"  >&lt;p&gt;Since I forgot to say it but will edit. Pretty sure it is a bug due to the block is not powered. &lt;/p&gt;</comment>
                            <comment id="321408" author="depressed-pho" created="Wed, 20 Jul 2016 05:17:30 +0200"  >&lt;p&gt;This doesn&apos;t affect 0.15.2. It&apos;s a regression for 0.15.3.&lt;/p&gt;</comment>
                            <comment id="321400" author="bugreporter101" created="Wed, 20 Jul 2016 04:58:15 +0200"  >&lt;p&gt;I am sure that is implemented because the redstone torch will power the block, thus, passing its redstone signal to the piston.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10102">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="148237">MCPE-16602</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="150179">MCPE-17290</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="157569">MCPE-19128</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10103">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="143209">MCPE-15195</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="146757">MCPE-16283</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="148826">MCPE-16831</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="153366">MCPE-17909</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="154014">MCPE-18114</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="122041" name="Screenshot_2016-07-19-21-12-56.png" size="1554751" author="jahunt78" created="Wed, 20 Jul 2016 04:35:13 +0200"/>
                            <attachment id="122045" name="Screenshot_2016-07-19-21-49-08.png" size="1244482" author="jahunt78" created="Wed, 20 Jul 2016 05:53:16 +0200"/>
                            <attachment id="122055" name="Screenshot_2016-07-20-08-47-33.png" size="3124093" author="rplatham" created="Wed, 20 Jul 2016 15:04:55 +0200"/>
                            <attachment id="122046" name="Screenshot_2016-07-20-11-33-34.png" size="378646" author="PlantSeed" created="Wed, 20 Jul 2016 06:55:39 +0200"/>
                            <attachment id="127802" name="Screenshot_2016-11-05-09-18-47.png" size="3912282" author="jahunt78" created="Sat, 5 Nov 2016 16:28:40 +0100"/>
                            <attachment id="122713" name="piston-activation-glitch.png" size="1847942" author="depressed-pho" created="Mon, 8 Aug 2016 01:26:26 +0200"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_11500" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>ADO</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>41083</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10701" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>CHK</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Fri, 2 Dec 2016 11:24:00 +0100</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_11300" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>Operating System Version</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>android vanilla 5.0</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10402" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Platform</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10726"><![CDATA[Phone - Android - Samsung Galaxy Note]]></customfieldvalue>

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

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