<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sun Jan 12 11:54:52 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-1563] Command Blocks Teleporting Wrong</title>
                <link>https://bugs.mojang.com/browse/MC-1563</link>
                <project id="10400" key="MC">Minecraft: Java Edition</project>
                    <description>&lt;p&gt;First i know the Command Blocks are still a WIP but&lt;br/&gt;
I had a Bunch of command blocks for a map i was making&lt;br/&gt;
after about 10-20 Command Blocks The Command Block was Teleporting Everyone on my Server to Random Points i told the Command Blocks to Have ex. 120 5 210&lt;br/&gt;
i would be working and then i would randomly get teleported back there.&lt;br/&gt;
It is random and has gotten better but it is still there &lt;img class=&quot;emoticon&quot; src=&quot;https://bugs.mojang.com/images/icons/emoticons/wink.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;br/&gt;
if you want to recreate the bug just have a bunch of command blocks hooked up to buttons &quot;Not next to eachother or else they will emit a redstone signal ruining everything&quot;&lt;/p&gt;</description>
                <environment>Windows 7&lt;br/&gt;
Java 7</environment>
        <key id="12901">MC-1563</key>
            <summary>Command Blocks Teleporting Wrong</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="sniperpwner">SniperPwner</reporter>
                        <labels>
                            <label>command_block</label>
                            <label>redstone</label>
                            <label>repeaters</label>
                    </labels>
                <created>Thu, 1 Nov 2012 04:57:01 +0100</created>
                <updated>Fri, 29 Dec 2017 23:13:27 +0100</updated>
                            <resolved>Tue, 15 Jan 2013 17:40:52 +0100</resolved>
                                    <version>Minecraft 1.4.2</version>
                                    <fixVersion>Minecraft 1.4.5</fixVersion>
                                                        <votes>1</votes>
                                    <watches>1</watches>
                                                                            <comments>
                            <comment id="36981" author="bljat" created="Tue, 15 Jan 2013 17:40:52 +0100"  >&lt;p&gt;No response on querry, assuming fixed.&lt;/p&gt;</comment>
                            <comment id="25393" author="bljat" created="Tue, 27 Nov 2012 22:20:17 +0100"  >&lt;p&gt;Is this still a concern in the current Minecraft version? 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="16277" author="thoronwen" created="Thu, 1 Nov 2012 09:53:15 +0100"  >&lt;p&gt;I&apos;ve noticed this issue while testing out the PRE, I have not yet come across it on 1.4.2 but haven&apos;t tried either. As SniperPwner has experienced the issue on the most recent version &lt;img class=&quot;emoticon&quot; src=&quot;https://bugs.mojang.com/images/icons/emoticons/help_16.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;, but I don&apos;t think he describes it very clearly, I&apos;ll add my description.&lt;/p&gt;

&lt;p&gt;I&apos;m using &quot;teleport pads&quot;: a block with a pressure plate, that powers a command block with a say command (say Teleported to Old Newbridge: @a[ &amp;lt;coordinates of pressure pad&amp;gt;,r=2 ]) first, and then another command block with the actual teleport command. (tp @a[ &amp;lt;coordinates of pressure pad&amp;gt;,r=2 ] &amp;lt;coordinates of destination&amp;gt; )&lt;br/&gt;
I&apos;m using @a and not @p because should 2 players get on the pad, I want both of them to be teleported, despite only having one redstone pulse.&lt;/p&gt;

&lt;p&gt;When alone and testing these, everything works as expected.&lt;/p&gt;

&lt;p&gt;When testing with a friend, we noticed the following:&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;I use the teleport pad, get teleported as expected. Message: &quot;Teleported to Old Newbridge: Thoronwen&quot;&lt;/li&gt;
	&lt;li&gt;A few seconds later, my friend also uses the teleport pad. Now, both of us get teleported to the destination, despite me not being within @a[ &amp;lt;coordinates of pressure pad&amp;gt;,r=2 ]. Message: &quot;Teleported to Old Newbridge: ElanFromRSR and Thoronwen&quot;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;I&apos;m not sure if it matters, but the destination was far (-250,100ish to 10000,-10000ish) from the teleport pad: the chunks would not have been loaded.&lt;/p&gt;

&lt;p&gt;My guess is that the coordinates of the player that was teleported first somehow &quot;linger&quot; in the @a[ &amp;lt;coordinates of pressure pad&amp;gt;,r=2 ] area, even though the player has teleported out. &lt;br/&gt;
As the message is also affected, this would be a problem with @a, not with the tp command.&lt;/p&gt;

&lt;p&gt;EDIT: Oh, and as the second player was in the area when the pad was used the first time, it would not have been stuck in the powered position (and if it was it wouldn&apos;t have triggered a second time)&lt;/p&gt;</comment>
                            <comment id="16241" author="sycholic" created="Thu, 1 Nov 2012 05:16:42 +0100"  >&lt;p&gt;can you post your commands you are using please? they really should have a variable for who triggered the event not who&apos;s closest or even have a possible @r in one of your blocks. Want to try and repo this.  Are all your blocks in a central locale and then return blocks back from where they take you? or they just randomly all over?  Also if you using a button or redstone see if its being stuck &apos;on&apos; after using the teleporter... if so then its likely related to &lt;a href=&quot;https://bugs.mojang.com/browse/MC-638&quot; title=&quot;Chunks unload via teleporting with command block before a button or pressure plates unpowers&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MC-638&quot;&gt;&lt;del&gt;MC-638&lt;/del&gt;&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_10501" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Game Mode</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10304"><![CDATA[Survival]]></customfieldvalue>

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

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