MC-1563Command Blocks Teleporting Wrong
First i know the Command Blocks are still a WIP but
I had a Bunch of command blocks for a map i was making
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
i would be working and then i would randomly get teleported back there.
It is random and has gotten better but it is still there 
if you want to recreate the bug just have a bunch of command blocks hooked up to buttons "Not next to eachother or else they will emit a redstone signal ruining everything"
Environment
Windows 7
Java 7
Created Issue:
Command Blocks Teleporting Wrong
First i know the Command Blocks are still a WIP but
I had a Bunch of command blocks for a map i was making
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
i would be working and then i would randomly get teleported back there.
It is random and has gotten better but it is still there
if you want to recreate the bug just have a bunch of command blocks hooked up to buttons "Not next to eachother or else they will emit a redstone signal ruining everything"Environment
Windows 7
Java 7
- Unresolved
- Open
- Public
- Unconfirmed
- Survival
- 1.4.2 bug commandblock minecraft redstone repeaters
- 1.4.2
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
can you post your commands you are using please? they really should have a variable for who triggered the event not who'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 'on' after using the teleporter... if so then its likely related to
MC-638I've noticed this issue while testing out the PRE, I have not yet come across it on 1.4.2 but haven't tried either. As SniperPwner has experienced the issue on the most recent version
, but I don't think he describes it very clearly, I'll add my description.
I'm using "teleport pads": a block with a pressure plate, that powers a command block with a say command (say Teleported to Old Newbridge: @a[ <coordinates of pressure pad>,r=2 ]) first, and then another command block with the actual teleport command. (tp @a[ <coordinates of pressure pad>,r=2 ] <coordinates of destination> )
I'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.
When alone and testing these, everything works as expected.
When testing with a friend, we noticed the following:
I'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.
My guess is that the coordinates of the player that was teleported first somehow "linger" in the @a[ <coordinates of pressure pad>,r=2 ] area, even though the player has teleported out.
As the message is also affected, this would be a problem with @a, not with the tp command.
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't have triggered a second time)
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.
No response on querry, assuming fixed.