1
In my non eludian map I was using hidden command blocks with the command "/tp @a[r=1] ~5 ~ ~-5" to create a seemingly endless corridor. The reason it was seamless is because the player coordinates were subtracted. I recently updated my map 1.16.4 to use the new blocks and the structure block. None of the command blocks were working. I tried the 'New method' using "/tp @a[dy=1] ~-5 ~ ~4". But instead of subtracting the cords it just teleport you to a specific coordinate, making the teleportation noticeable. Is there anyway to create seamless teleportation in 1.16.4?
Create an account or sign in to comment.
3
In 1.13, many commands were changed. /scoreboard teams is now /team, /scoreboard players tag is now /tag, /execute is completely revamped, /testfor, /testforblock, and /testforblocks are now all part of /execute if, and many selector arguments have been changed.
Since 1.13, the "r" selector argument has been replaced with distance: @a[distance=<range>]. Ranges are a new type of value used in a couple different spots (also used in scoreboards and some other selector arguments) that works like this:
This is the first issue. Instead of @a[r=1] you want @a[distance=..1]. The second is that /tp now works just like /teleport: The relative coordinates are relative to the command's execution point, not the target's location. This means that "/tp @p ~ ~1 ~" in a command block teleports the player above the command block instead of above their current location. You instead want to use /execute with "as" and "at" arguments. This will use the new @s selector, which selects the entity running the command. The final command is:
/execute as @a[distance=..1] at @s run tp @s ~5 ~ ~-5
I recommend you read up on the new command syntax, as a lot has changed and it allows you to do much more than the old stuff.
Since 1.13, the "r" selector argument has been replaced with distance: @a[distance=<range>]. Ranges are a new type of value used in a couple different spots (also used in scoreboards and some other selector arguments) that works like this:
| range value | meaning |
| 4 | exactly 4 (blocks away) |
| ..4 | 4 or less (blocks away, equivalent to r=4) |
| 4.. | 4 or more (blocks away) |
| 4..8 | 4 to 8 (blocks away) |
This is the first issue. Instead of @a[r=1] you want @a[distance=..1]. The second is that /tp now works just like /teleport: The relative coordinates are relative to the command's execution point, not the target's location. This means that "/tp @p ~ ~1 ~" in a command block teleports the player above the command block instead of above their current location. You instead want to use /execute with "as" and "at" arguments. This will use the new @s selector, which selects the entity running the command. The final command is:
/execute as @a[distance=..1] at @s run tp @s ~5 ~ ~-5
I recommend you read up on the new command syntax, as a lot has changed and it allows you to do much more than the old stuff.
In 1.13, many commands were changed. /scoreboard teams is now /team, /scoreboard players tag is now /tag, /execute is completely revamped, /testfor, /testforblock, and /testforblocks are now all part of /execute if, and many selector arguments have been changed.
Since 1.13, the "r" selector argument has been replaced with distance: @a[distance=<range>]. Ranges are a new type of value used in a couple different spots (also used in scoreboards and some other selector arguments) that works like this:
This is the first issue. Instead of @a[r=1] you want @a[distance=..1]. The second is that /tp now works just like /teleport: The relative coordinates are relative to the command's execution point, not the target's location. This means that "/tp @p ~ ~1 ~" in a command block teleports the player above the command block instead of above their current location. You instead want to use /execute with "as" and "at" arguments. This will use the new @s selector, which selects the entity running the command. The final command is:
/execute as @a[distance=..1] at @s run tp @s ~5 ~ ~-5
I recommend you read up on the new command syntax, as a lot has changed and it allows you to do much more than the old stuff.
Since 1.13, the "r" selector argument has been replaced with distance: @a[distance=<range>]. Ranges are a new type of value used in a couple different spots (also used in scoreboards and some other selector arguments) that works like this:
| range value | meaning |
| 4 | exactly 4 (blocks away) |
| ..4 | 4 or less (blocks away, equivalent to r=4) |
| 4.. | 4 or more (blocks away) |
| 4..8 | 4 to 8 (blocks away) |
This is the first issue. Instead of @a[r=1] you want @a[distance=..1]. The second is that /tp now works just like /teleport: The relative coordinates are relative to the command's execution point, not the target's location. This means that "/tp @p ~ ~1 ~" in a command block teleports the player above the command block instead of above their current location. You instead want to use /execute with "as" and "at" arguments. This will use the new @s selector, which selects the entity running the command. The final command is:
/execute as @a[distance=..1] at @s run tp @s ~5 ~ ~-5
I recommend you read up on the new command syntax, as a lot has changed and it allows you to do much more than the old stuff.
Thank you for this long and detailed answers, I'll certainly read up on the new stuff
Marking solved
Marking solved
