agentme
Assigned
Reported
Comments
That's not the behavior I experienced. In my testing, the command `/execute Alice ~ ~ ~ tp Bob ~ ~ ~` would teleport Bob to Alice's x/y/z coordinates in Bob's own dimension even if Alice was in another dimension. Doing the same with an entity like `/execute @e[name=Nether_tag] ~ ~ ~ tp Bob ~ ~ ~` also worked the same way for me, as long as the entity was in a loaded chunk in any dimension. I was on 1.10.1 in the Windows 10 version in a world hosted by an Xbox one player, only going between the main world and the Nether, and entering the commands through chat rather than a block if that matters.
Also just to be clear, `/tp @p @e[name=Nether_tag]` did work for me if the entity was loaded, teleporting me from any dimension to the entity's dimension and coordinates. (The problem was that it would teleport me directly to the entity's coordinates, which is why I wanted to use /execute instead.)
Apparently Code connection sometimes spawns you a new agent, so now I have 4 unremovable agents in a world and only 1 of them can be moved around. The other 3 seem to be stuck where they are for eternity now while I'm on.
The /execute command is supposed to run a command as if a specific target entity ran the command. The position parameters to the /execute command (2nd-4th args) are executed relative the entity's location so that `~` works. Currently it disregards the target entity's dimension, which isn't useful behavior, and it is inconsistent with how the /execute command works in the Java edition. It would be tremendously more useful if it used the target entity's dimension, like the Java edition does. It seems like a simple oversight that the Bedrock edition's version of the /execute command disregards dimensions entirely.
In the Java edition, this command teleports the player to a named armor stand's location, including its dimension:
The "~ ~ ~" could be replaced with specific coordinates like "100 110 120", and the player will be teleported to those coordinates, in the armor stand's dimension, not the player's.
This is the roughly equivalent command in the Bedrock edition:
However, this command in the Bedrock edition teleports the player to the coordinates in the player's own dimension, which isn't useful, and means there's no way in the Bedrock edition to teleport a player to arbitrary coordinates in another dimension.
>I did notice that you typed "1234 60 2345" at "...] 0 0 0 tp @p 1234 60 2345." Of course it would teleport the player to the coordinates in your own dimension. It checks to see it the entity is at 0 0 0, then teleports the player to 1234 60 2345 in their own dimension...
That's not what that command does. It executes the command as a specific target entity at its location, then adjusts the command's activation location to 0 0 0, and then runs "tp @p 1234 60 2345" as the target entity.
>You could try 2 command blocks[...]
The problem is that after the first command executes, the player is far away from the command block, and may no longer be the closest player to the command block, so the second command block may select a different player with @p.