I would like to be able to have command blocks do things in other dimensions. For example, /tp 0 0 0 teleports the player to (0, 0, 0) in the dimension that the player is currently in. Then, if 0, 1, or 2 are added to a specific place depending on the command, it uses the coordinate for the Overworld, Nether, or End, respectively. This would apply to any command that uses coordinates as arguments. Commands would then be able to interact with blocks and entities in other dimensions. The dimension would also be a target selector argument. Also, I'd like for the spawn chunks to load as long as any player in that world.
I like this idea, but it needs to be rebalanced a bit. You need to keep in mind that rotation coordinates are a thing. Currently the format is this:
/tp <player> <x> <y> <z> [<rx> <ry>]
where <> is mandatory and [] is optional, but I could easily see them adding something to the end to specify dimension, such as this:
/tp <player> <x> <y> <z> [<rx> <ry> [dimension]].
So if you wanted to TP a player to a different dimension you'd need to specify the rotation coords as well. For two reasons: 1) Based on the way portals work, rotations don't translate very well between dimensions, and 2) the spot right after the "z" is already taken up by rotation- adding a new format would be kind of tedious.
As for the main idea of this suggestion: I support it, because /tp <player1> <player2> will work even if the players are in different dimensions
I like this idea, but it needs to be rebalanced a bit. You need to keep in mind that rotation coordinates are a thing. Currently the format is this:
/tp <player> <x> <y> <z> [<rx> <ry>]
where <> is mandatory and [] is optional, but I could easily see them adding something to the end to specify dimension, such as this:
/tp <player> <x> <y> <z> [<rx> <ry> [dimension]].
So if you wanted to TP a player to a different dimension you'd need to specify the rotation coords as well. For two reasons: 1) Based on the way portals work, rotations don't translate very well between dimensions, and 2) the spot right after the "z" is already taken up by rotation- adding a new format would be kind of tedious.
As for the main idea of this suggestion: I support it, because /tp <player1> <player2> will work even if the players are in different dimensions
I made a list of syntaxes for every command involving coordinates (except for commands that change spawnpoints), including tp.
Rollback Post to RevisionRollBack
If you follow your heart, it will only lead to your arteries.
I made a list of syntaxes for every command involving coordinates (except for commands that change spawnpoints), including tp.
I still think you need to add [dimension] at the end of all those, not just randomly stuck in the middle. Putting optional parameters in between required parameters is highly risky, as it can interfere with the ones that are required.
Even if it doesnt look pretty, it's much safer that way. And besides, Mojang has ALWAYS put optional stuff at the end. And sometimes their stuff doesnt seem very logical either, but it's for the purpose of making commands more consistent and less awkward.
I still think you need to add [dimension] at the end of all those, not just randomly stuck in the middle. Putting optional parameters in between required parameters is highly risky, as it can interfere with the ones that are required.
Even if it doesnt look pretty, it's much safer that way. And besides, Mojang has ALWAYS put optional stuff at the end. And sometimes their stuff doesnt seem very logical either, but it's for the purpose of making commands more consistent and less awkward.
Have you checked the syntax for every command? Also, I made sure that, if the dimension is followed by a required parameter, that parameter is never a number.
Rollback Post to RevisionRollBack
If you follow your heart, it will only lead to your arteries.
I still think you need to add [dimension] at the end of all those, not just randomly stuck in the middle. Putting optional parameters in between required parameters is highly risky, as it can interfere with the ones that are required.
Even if it doesnt look pretty, it's much safer that way. And besides, Mojang has ALWAYS put optional stuff at the end. And sometimes their stuff doesnt seem very logical either, but it's for the purpose of making commands more consistent and less awkward.
The simplest way to do it is make it not optional, always after <z>, and use the ~ like with regular coordinates. So teleporting one block above you would be.
The simplest way to do it is make it not optional, always after <z>, and use the ~ like with regular coordinates. So teleporting one block above you would be.
I still think it should be optional though, as if people have command blocks set up already that have these commands, they're going to have to go back and change them to accomodate. That's why changing the syntax of a command is always so risky.
I just discovered that Minecraft 1.13 Java Edition does allow you to teleport between dimensions. Well sort of. The new execute command allows you to execute in the overworld, nether, or end. What this does is execute the command after the run as if you were standing in the specified dimension when the command executes. For teleporting, this means that the coordinates you specify will be coordinates for the specified dimension. So let's say I want to teleport to coordinates 0 70 0 in each of those dimensions. I would use the following commands.
/execute in the_nether run teleport @p 0 70 0
/execute in overworld run teleport @p 0 70 0
/execute in the_end run teleport @p 0 70 0
It would seem that a couple of years after your post, Mojang answered it. I've tested these teleportation commands from the command line, and they do work. Those particular coordinates dropped me near the ender dragon. In the nether, I was near a nether fortress. But that may vary according to your world seed. I could just as easily have been swimming in some lava or materialized in the middle of solid rock and suffocated. I would try this in creative mode for those sorts of reasons. It should be noted that this was what I set my world spawn point too. So that may have impacted the situation in the end. Keep in mind that this form of the execute command can be used with a wide variety of commands. Not just teleport. So it sounds fairly similar to what you are suggesting.
I would like to be able to have command blocks do things in other dimensions. For example, /tp 0 0 0 teleports the player to (0, 0, 0) in the dimension that the player is currently in. Then, if 0, 1, or 2 are added to a specific place depending on the command, it uses the coordinate for the Overworld, Nether, or End, respectively. This would apply to any command that uses coordinates as arguments. Commands would then be able to interact with blocks and entities in other dimensions. The dimension would also be a target selector argument. Also, I'd like for the spawn chunks to load as long as any player in that world.
List of commands that would be affected
<required parameter> [optional parameter]
blockdata <x> <y> <z> [dimension] <dataTag>
clone <x1> <y1> <z1> <x2> <2y> <z2> <x> <y> <z> [dimension1] [dimension] [maskMode] [cloneMode] [tileName]
If two dimensions are entered, it clones blocks from one dimension to the other.
execute <entity> <x> <y> <z> [dimension] <command...>
execute <entity> <x> <y> <z> [dimension] detect <x1> <y1> <z1> [dimension1] <block> <data> <command...>
fill <x1> <y1> <z1> <x2> <y2> <z2> [dimension] <TileName> [dataValue] [oldBlockHandling] [dataTag]
particle <name> <x> <y> <z> <xd> <yd> <zd> <speed> [count] [dimension] [mode] [player] [params...]
playsound <sound> <source> <player> [x] [y] [z] [volume] [pitch] [minimumVolume] [dimension]
setblock <x> <y> <z> [dimension] <TileName> [dataValue] [oldBlockHandling] [dataTag]
spreadplayers <x> <z> <spreadDistance> <maxRange> [dimension] <respectTeams> < player...>
stats block <x> <y> <z> [dimension] clear <stat>
stats block <x> <y> <z> [dimension] set <stat> <selector> <objective>
summon <EntityName> [x] [y] [z] [dimension] [dataTag]
teleport <targetEntity> <x> <y> <z> [<yaw> <pitch>] [dimension]
testforblock <x> <y> <z> [dimension] <TileName> [dataValue] [dataTag]
testforblocks <x1> <y1> <z1> <x2> <y2> <z2> <x> <y> <z> [dimension] [mode]
tp [targetPlayer] <x> <y> <z> [<yaw> <pitch>] [dimension]
worldborder center <x> <z> [dimension]
Would this be useful?
If you follow your heart, it will only lead to your arteries.
Looks good, but the dimension should be after the coordinates, not before. Why? Because commands always put the optional arguments last.
Want to see my suggestions? Here they are!
I am also known as GameWyrm or GameWyrm97. You can also find me at snapshotmc.com
I like this idea, but it needs to be rebalanced a bit. You need to keep in mind that rotation coordinates are a thing. Currently the format is this:
/tp <player> <x> <y> <z> [<rx> <ry>]
where <> is mandatory and [] is optional, but I could easily see them adding something to the end to specify dimension, such as this:
/tp <player> <x> <y> <z> [<rx> <ry> [dimension]].
So if you wanted to TP a player to a different dimension you'd need to specify the rotation coords as well. For two reasons: 1) Based on the way portals work, rotations don't translate very well between dimensions, and 2) the spot right after the "z" is already taken up by rotation- adding a new format would be kind of tedious.
As for the main idea of this suggestion: I support it, because /tp <player1> <player2> will work even if the players are in different dimensions
I edited it. It should look better now.
If you follow your heart, it will only lead to your arteries.
I have always found it annoying to not be able to teleport entities between dimensions, support if the command is formatted like
My Github ด้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้дด็็็็็้้้้้็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้
Mostly I find it annoying that the spawn chunks stop loading after all the players go to the end.
If you follow your heart, it will only lead to your arteries.
I made a list of syntaxes for every command involving coordinates (except for commands that change spawnpoints), including tp.
If you follow your heart, it will only lead to your arteries.
I still think you need to add [dimension] at the end of all those, not just randomly stuck in the middle. Putting optional parameters in between required parameters is highly risky, as it can interfere with the ones that are required.
Even if it doesnt look pretty, it's much safer that way. And besides, Mojang has ALWAYS put optional stuff at the end. And sometimes their stuff doesnt seem very logical either, but it's for the purpose of making commands more consistent and less awkward.
Have you checked the syntax for every command? Also, I made sure that, if the dimension is followed by a required parameter, that parameter is never a number.
If you follow your heart, it will only lead to your arteries.
Can't believe they haven't added this already.
The simplest way to do it is make it not optional, always after <z>, and use the ~ like with regular coordinates. So teleporting one block above you would be.
My Github ด้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้дด็็็็็้้้้้็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้
I still think it should be optional though, as if people have command blocks set up already that have these commands, they're going to have to go back and change them to accomodate. That's why changing the syntax of a command is always so risky.
I just discovered that Minecraft 1.13 Java Edition does allow you to teleport between dimensions. Well sort of. The new execute command allows you to execute in the overworld, nether, or end. What this does is execute the command after the run as if you were standing in the specified dimension when the command executes. For teleporting, this means that the coordinates you specify will be coordinates for the specified dimension. So let's say I want to teleport to coordinates 0 70 0 in each of those dimensions. I would use the following commands.
/execute in the_nether run teleport @p 0 70 0
/execute in overworld run teleport @p 0 70 0
/execute in the_end run teleport @p 0 70 0
It would seem that a couple of years after your post, Mojang answered it. I've tested these teleportation commands from the command line, and they do work. Those particular coordinates dropped me near the ender dragon. In the nether, I was near a nether fortress. But that may vary according to your world seed. I could just as easily have been swimming in some lava or materialized in the middle of solid rock and suffocated. I would try this in creative mode for those sorts of reasons. It should be noted that this was what I set my world spawn point too. So that may have impacted the situation in the end. Keep in mind that this form of the execute command can be used with a wide variety of commands. Not just teleport. So it sounds fairly similar to what you are suggesting.