Richard A. Hallett
- RichardAHallett
- richardahallett
- Europe/London
- Yes
- No
MC-54825![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
If you fill a dispenser, aiming upward, with flight-duration-3 fireworks and then push the firework entity horizontally with a slime block attached to a sticky piston (with a delay of one setting-4 repeater between the dispenser being triggered and the piston extending) it launches the firework diagonally with a ridiculous velocity.
Sometimes when a firework is launched in such a way it causes the game to experience crippling framerate lag or even temporarily freeze up. Hooking the device up to a clock can have terrible effects on a world until the clock is disengaged. In 1.8-pre2, launching a single firework in this way crashed a singleplayer world.
If you fill a dispenser, aiming upward, with flight-duration-3 fireworks and then push the firework entity horizontally with a slime block attached to a sticky piston (with a delay of one setting-4 repeater between the dispenser being triggered and the piston extending) it launches the firework diagonally with a ridiculous velocity.
Flight duration
Sometimes when a firework is launched in such a way it causes the game to experience crippling framerate lag or even temporarily freeze up. Hooking the device up to a clock can have terrible effects on a world until the clock is disengaged. In 1.8-pre2, launching a single firework in this way crashed a singleplayer world.
If you fill a dispenser, aiming upward, with flight-duration-3 fireworks and then push the firework entity horizontally with a slime block attached to a sticky piston (with a delay of one setting-4 repeater between the dispenser being triggered and the piston extending) it launches the firework diagonally with a ridiculous velocity.
Flight duration
Sometimes when a firework is launched in such a way it causes the game to experience crippling framerate lag or even temporarily freeze up. Hooking the device up to a clock can have terrible effects on a world until the clock is disengaged. In 1.8-pre2, launching a single firework in this way crashed a singleplayer world.
If you fill a dispenser, aiming upward, with flight-duration-3 fireworks and then push the firework entity horizontally with a slime block attached to a sticky piston (with a delay of one setting-4 repeater between the dispenser being triggered and the piston extending) it launches the firework diagonally with a ridiculous velocity.
Sometimes when a firework is launched in such a way it causes the game to experience crippling framerate lag or even temporarily freeze up. Hooking the device up to a clock can have terrible effects on a world until the clock is disengaged. In 1.8-pre2, launching a single firework in this way crashed a singleplayer world.If you fill a dispenser, aiming upward, with flight-duration-3 fireworks and then push the firework entity horizontally with a slime block attached to a sticky piston (with a delay of one setting-4 repeater between the dispenser being triggered and the piston extending) it launches the firework diagonally with a ridiculous velocity.
Flight duration 1 and 2 do not seem to cause this problem. I launched a few of each and there were no adverse affects. It seems that it might be from the firework reaching unloaded chunks without managing to explode I was using 16 chunk render distance. Once I changed it to 32 chunks I could launch flight duration 3 fireworks with no adverse effects.
Sometimes when a firework is launched in such a way it causes the game to experience crippling framerate lag or even temporarily freeze up. Hooking the device up to a clock can have terrible effects on a world until the clock is disengaged. In 1.8-pre2, launching a single firework in this way crashed a singleplayer world.
If you fill a dispenser, aiming upward, with flight-duration-3 fireworks and then push the firework entity horizontally with a slime block attached to a sticky piston (with a delay of one setting-4 repeater between the dispenser being triggered and the piston extending) it launches the firework diagonally with a ridiculous velocity.
Flight duration 1 and 2 do not seem tocause this problem. I launched a few of each and there were no adverse affects. It seems that it might be from the firework reaching unloaded chunks without managing to explode I was using 16 chunk render distance. Once I changed it to 32 chunks I could launch flight duration 3 fireworks with no adverse effects.
Sometimes when a firework is launched in such a way it causes the game to experience crippling framerate lag or even temporarily freeze up. Hooking the device up to a clock can have terrible effects on a world until the clock is disengaged. In 1.8-pre2, launching a single firework in this way crashed a singleplayer world.If you fill a dispenser, aiming upward, with flight-duration-3 fireworks and then push the firework entity horizontally with a slime block attached to a sticky piston (with a delay of one setting-4 repeater between the dispenser being triggered and the piston extending) it launches the firework diagonally with a ridiculous velocity.
Sometimes when a firework is launched in such a way it causes the game to experience crippling framerate lag or even temporarily freeze up. Hooking the device up to a clock can have terrible effects on a world until the clock is disengaged. In 1.8-pre2, launching a single firework in this way crashed a singleplayer world.
Flight duration 1 and 2 do not seem to cause this problem. I launched a few of each and there were no adverse affects. It seems that it might be from the firework reaching unloaded chunks without managing to explode I was using 16 chunk render distance. Once I changed it to 32 chunks I could launch flight duration 3 fireworks with no adverse effects.
If you fill a dispenser, aiming upward, with flight-duration-3 fireworks and then push the firework entity horizontally with a slime block attached to a sticky piston (with a delay of one setting-4 repeater between the dispenser being triggered and the piston extending) it launches the firework diagonally with a ridiculous velocity.
Sometimes when a firework is launched in such a way it causes the game to experience crippling framerate lag or even temporarily freeze up. Hooking the device up to a clock can have terrible effects on a world until the clock is disengaged. In 1.8-pre2, launching a single firework in this way crashed a singleplayer world.
Flight duration 1 and 2 do not seem to cause this problem. I launched a few of each and there were no adverse affects. It seems that it might be from the firework reaching unloaded chunks without managing to explode. I was using 16 chunk render distance. Once I changed it to 32 chunks I could launch flight duration 3 fireworks with no adverse effects.
If you fill a dispenser, aiming upward, with flight-duration-3 fireworks and then push the firework entity horizontally with a slime block attached to a sticky piston (with a delay of one setting-4 repeater between the dispenser being triggered and the piston extending) it launches the firework diagonally with a ridiculous velocity.
Sometimes when a firework is launched in such a way it causes the game to experience crippling framerate lag or even temporarily freeze up. Hooking the device up to a clock can have terrible effects on a world until the clock is disengaged. In 1.8-pre2, launching a single firework in this way crashed a singleplayer world.
Flight duration 1 and 2 do not seem to cause this problem. I launched a few of each and there were no adverse affects. It seems that it might be from the firework reaching unloaded chunks without managing to explode. I was using 16 chunk render distance. Once I changed it to 32 chunks I could launch flight duration 3 fireworks with no adverse effects.
Edit: After switching back to 16 chunks the issue vanished. It seems it might be caused by fireworks reaching ungenerated chunks without exploding.
If you fill a dispenser, aiming upward, with flight-duration-3 fireworks and then push the firework entity horizontally with a slime block attached to a sticky piston (with a delay of one setting-4 repeater between the dispenser being triggered and the piston extending) it launches the firework diagonally with a ridiculous velocity.
Sometimes when a firework is launched in such a way it causes the game to experience crippling framerate lag or even temporarily freeze up. Hooking the device up to a clock can have terrible effects on a world until the clock is disengaged. In 1.8-pre2, launching a single firework in this way crashed a singleplayer world.
Flight duration 1 and 2 do not seem to cause this problem. I launched a few of each and there were no adverse affects. It seems that it might be from the firework reaching unloaded chunks without managing to explode. I was using 16 chunk render distance. Once I changed it to 32 chunks I could launch flight duration 3 fireworks with no adverse effects.
Edit: After switching back to 16 chunks the issue vanished. It seems it might be caused by fireworks reaching ungenerated chunks without exploding. Or possibly not. The lock-up happened again after launching a lot more.
horsebones_horsebones.json
Overview
Summoning at an entity via execute fails silently if the entity is in a different dimension than the source of the command or function. The entity does not appear at the specified coordinates in any dimension, and there is no error message in the log or chat.
This is inconsistent with other behaviour. For example, the particle command does work at the entity's location in any dimension regardless of the dimension the command or function originates in.
- A function run from #minecraft:tick counts as running in the Overworld.
- A function running on a command block or player runs in the dimension it is in.
Simple demonstration
- Drop an Iron Sword and, without going to another dimension, run the command /execute at @e[type=minecraft:item,nbt={Item:{id:"minecraft:iron_sword"}}] run summon minecraft:armor_stand ~ ~ ~ An Armor Stand will appear at the item's location and the message Summoned new Armor Stand will appear in chat.
- Drop an Iron Sword in the spawn chunks of the Overworld, go to the Nether, and run the above command. The same message will appear in chat, but when you go back to the Overworld there will be no Armor Stand at the item's location.
Example data pack
The attached data pack demonstrates this more exhaustively, and how it is inconsistent with the particle }} command. There are 3 functions that each execute a secondary function {{as and at a sword item on the ground. The secondary function:
- Summons an invulnerable, no gravity Armor Stand holding that type of sword at that location.
- Spawns some particles at that location.
- Gives a chat message.
- Kills the item.
The three functions are triggered in different ways:- dimension_execute_test:player_tick - The one for the Wooden Sword is run automatically on each player every tick using an advancement.
- dimension_execute_test:minecraft_tick - The one for the Stone Sword is run automatically before every tick using #minecraft:tick
- dimension_execute_test:manual - The one for the Iron Sword can be run either by a player or in a command block.
Anomalous behaviour includes:- Drop a Stone Sword in the Nether or End. The Armor Stand will not be summoned, but the particles and chat message will appear.
- Drop an Iron Sword in the spawn chunks of the Overworld, go into the Nether or End and run function dimension_execute_test:manual The Armor Stand will not be summoned, but the chat message will appear (and presumably the particles if someone was there to observe it.)
- Put function dimension_execute_test:manual in a repeating, always active Command Block. In dimensions other than the one the Command Block is in, the Armor Stand will not be summoned, but the particles and chat message will appear. (Easiest to test with the Command Block in the spawn chunks of the Overworld.)
- Build a device in the spawn chunks of the Overworld that, after a delay, drops a Wooden Sword. Go into the Nether or End. When the device drops the Wooden Sword the Armor Stand will not be summoned, but the chat message will appear (and presumably the particles if someone was there to observe it.)
Overview
Summoning at an entity via execute fails silently if the entity is in a different dimension than the source of the command or function. The entity does not appear at the specified coordinates in any dimension, and there is no error message in the log or chat.
This is inconsistent with other behaviour. For example, the particle command does work at the entity's location in any dimension regardless of the dimension the command or function originates in.
- A function run from #minecraft:tick counts as running in the Overworld.
- A function running on a command block or player runs in the dimension it is in.
Simple demonstration
- Drop an Iron Sword and, without going to another dimension, run the command /execute at @e[type=minecraft:item,nbt={Item:{id:"minecraft:iron_sword"}}] run summon minecraft:armor_stand ~ ~ ~ An Armor Stand will appear at the item's location and the message Summoned new Armor Stand will appear in chat.
- Drop an Iron Sword in the spawn chunks of the Overworld, go to the Nether, and run the above command. The same message will appear in chat, but when you go back to the Overworld there will be no Armor Stand at the item's location.
Example data pack
The attached data pack demonstrates this more exhaustively, and how it is inconsistent with the particle }} command. There are 3 functions that each execute a secondary function {{as and at a sword item on the ground. The secondary function:
- Summons an invulnerable, no gravity Armor Stand holding that type of sword at that location.
- Spawns some particles at that location.
- Gives a chat message.
- Kills the item.
The three functions are triggered in different ways:- dimension_execute_test:player_tick - The one for the Wooden Sword is run automatically on each player every tick using an advancement.
- dimension_execute_test:minecraft_tick - The one for the Stone Sword is run automatically before every tick using #minecraft:tick
- dimension_execute_test:manual - The one for the Iron Sword can be run either by a player or in a command block.
Anomalous behaviour includes:- Drop a Stone Sword in the Nether or End. The Armor Stand will not be summoned, but the particles and chat message will appear.
- Drop an Iron Sword in the spawn chunks of the Overworld, go into the Nether or End and run function dimension_execute_test:manual The Armor Stand will not be summoned, but the chat message will appear (and presumably the particles if someone was there to observe it.)
- Put function dimension_execute_test:manual in a repeating, always active Command Block. In dimensions other than the one the Command Block is in, the Armor Stand will not be summoned, but the particles and chat message will appear. (Easiest to test with the Command Block in the spawn chunks of the Overworld.)
- Build a device in the spawn chunks of the Overworld that, after a delay, drops a Wooden Sword. Go into the Nether or End. When the device drops the Wooden Sword the Armor Stand will not be summoned, but the chat message will appear (and presumably the particles if someone was there to observe it.)
Overview
Summoning at an entity via execute fails silently if the entity is in a different dimension than the source of the command or function. The entity does not appear at the specified coordinates in any dimension, and there is no error message in the log or chat.
This is inconsistent with other behaviour. For example, the particle command does work at the entity's location in any dimension regardless of the dimension the command or function originates in.
- A function run from #minecraft:tick counts as running in the Overworld.
- A function running on a command block or player runs in the dimension it is in.
Simple demonstration
- Drop an Iron Sword and, without going to another dimension, run the command /execute at @e[type=minecraft:item,nbt={Item:{id:"minecraft:iron_sword"}}] run summon minecraft:armor_stand ~ ~ ~ An Armor Stand will appear at the item's location and the message Summoned new Armor Stand will appear in chat.
- Drop an Iron Sword in the spawn chunks of the Overworld, go to the Nether, and run the above command. The same message will appear in chat, but when you go back to the Overworld there will be no Armor Stand at the item's location.
Example data pack
The attached data pack demonstrates this more exhaustively, and how it is inconsistent with the particle }} command. There are 3 functions that each execute a secondary function {{as and at a sword item on the ground. The secondary function:
- Summons an invulnerable, no gravity Armor Stand holding that type of sword at that location.
- Spawns some particles at that location.
- Gives a chat message.
- Kills the item.
The three functions are triggered in different ways:- dimension_execute_test:player_tick - The one for the Wooden Sword is run automatically on each player every tick using an advancement.
- dimension_execute_test:minecraft_tick - The one for the Stone Sword is run automatically before every tick using #minecraft:tick
- dimension_execute_test:manual - The one for the Iron Sword can be run either by a player or in a command block.
Anomalous behaviour includes:- Drop a Stone Sword in the Nether or End. The Armor Stand will not be summoned, but the particles and chat message will appear.
- Drop an Iron Sword in the spawn chunks of the Overworld, go into the Nether or End and run function dimension_execute_test:manual The Armor Stand will not be summoned, but the chat message will appear (and presumably the particles if someone was there to observe it.)
- Put function dimension_execute_test:manual in a repeating, always active Command Block. In dimensions other than the one the Command Block is in, the Armor Stand will not be summoned, but the particles and chat message will appear. (Easiest to test with the Command Block in the spawn chunks of the Overworld.)
- Build a device in the spawn chunks of the Overworld that, after a delay, drops a Wooden Sword. Go into the Nether or End. When the device drops the Wooden Sword the Armor Stand will not be summoned, but the chat message will appear (and presumably the particles if someone was there to observe it.)
Overview
Summoning at an entity via execute fails silently if the entity is in a different dimension than the source of the command or function. The entity does not appear at the specified coordinates in any dimension, and there is no error message in the log or chat.
This is inconsistent with other behaviour. For example, the particle command does work at the entity's location in any dimension regardless of the dimension the command or function originates in.
- A function run from #minecraft:tick counts as running in the Overworld.
- A function running on a command block or player runs in the dimension it is in.
Simple demonstration
- Drop an Iron Sword and, without going to another dimension, run the command /execute at @e[type=minecraft:item,nbt={Item:{id:"minecraft:iron_sword"}}] run summon minecraft:armor_stand ~ ~ ~ An Armor Stand will appear at the item's location and the message Summoned new Armor Stand will appear in chat.
- Drop an Iron Sword in the spawn chunks of the Overworld, go to the Nether, and run the above command. The same message will appear in chat, but when you go back to the Overworld there will be no Armor Stand at the item's location.
Example data pack
The attached data pack demonstrates this more exhaustively, and how it is inconsistent with the particle }} command. There are 3 functions that each execute a secondary function {{as and at a sword item on the ground. The secondary function:
- Summons an invulnerable, no gravity Armor Stand holding that type of sword at that location.
- Spawns some particles at that location.
- Gives a chat message.
- Kills the item.
The three functions are triggered in different ways:- dimension_execute_test:player_tick - The one for the Wooden Sword is run automatically on each player every tick using an advancement.
- dimension_execute_test:minecraft_tick - The one for the Stone Sword is run automatically before every tick using #minecraft:tick
- dimension_execute_test:manual - The one for the Iron Sword can be run either by a player or in a command block.
Anomalous behaviour includes:- Drop a Stone Sword in the Nether or End. The Armor Stand will not be summoned, but the particles and chat message will appear.
- Drop an Iron Sword in the spawn chunks of the Overworld, go into the Nether or End and run function dimension_execute_test:manual The Armor Stand will not be summoned, but the chat message will appear (and presumably the particles if someone was there to observe it.)
- Put function dimension_execute_test:manual in a repeating, always active Command Block. In dimensions other than the one the Command Block is in, the Armor Stand will not be summoned, but the particles and chat message will appear. (Easiest to test with the Command Block in the spawn chunks of the Overworld.)
- Build a device in the spawn chunks of the Overworld that, after a delay, drops a Wooden Sword. Go into the Nether or End. When the device drops the Wooden Sword the Armor Stand will not be summoned, but the chat message will appear (and presumably the particles if someone was there to observe it.)
Overview
Summoning at an entity via execute fails silently if the entity is in a different dimension than the source of the command or function. The entity does not appear at the specified coordinates in any dimension, and there is no error message in the log or chat.
This is inconsistent with other behaviour. For example, the particle command does work at the entity's location in any dimension regardless of the dimension the command or function originates in.
- A function run from #minecraft:tick counts as running in the Overworld.
- A function running on a command block or player runs in the dimension it is in.
Simple demonstration
- Drop an Iron Sword and, without going to another dimension, run the command /execute at @e[type=minecraft:item,nbt={Item:{id:"minecraft:iron_sword"}}] run summon minecraft:armor_stand ~ ~ ~ An Armor Stand will appear at the item's location and the message Summoned new Armor Stand will appear in chat.
- Drop an Iron Sword in the spawn chunks of the Overworld, go to the Nether, and run the above command. The same message will appear in chat, but when you go back to the Overworld there will be no Armor Stand at the item's location.
Example data pack
The attached data pack demonstrates this more exhaustively, and how it is inconsistent with the
particle }}command. There are 3 functions that each execute a secondary function{{asand at a sword item on the ground. The secondary function:
- Summons an invulnerable, no gravity Armor Stand holding that type of sword at that location.
- Spawns some particles at that location.
- Gives a chat message.
- Kills the item.
The three functions are triggered in different ways:- dimension_execute_test:player_tick - The one for the Wooden Sword is run automatically on each player every tick using an advancement.
- dimension_execute_test:minecraft_tick - The one for the Stone Sword is run automatically before every tick using #minecraft:tick
- dimension_execute_test:manual - The one for the Iron Sword can be run either by a player or in a command block.
Anomalous behaviour includes:- Drop a Stone Sword in the Nether or End. The Armor Stand will not be summoned, but the particles and chat message will appear.
- Drop an Iron Sword in the spawn chunks of the Overworld, go into the Nether or End and run function dimension_execute_test:manual The Armor Stand will not be summoned, but the chat message will appear (and presumably the particles if someone was there to observe it.)
- Put function dimension_execute_test:manual in a repeating, always active Command Block. In dimensions other than the one the Command Block is in, the Armor Stand will not be summoned, but the particles and chat message will appear. (Easiest to test with the Command Block in the spawn chunks of the Overworld.)
- Build a device in the spawn chunks of the Overworld that, after a delay, drops a Wooden Sword. Go into the Nether or End. When the device drops the Wooden Sword the Armor Stand will not be summoned, but the chat message will appear (and presumably the particles if someone was there to observe it.)
Overview
Summoning at an entity via execute fails silently if the entity is in a different dimension than the source of the command or function. The entity does not appear at the specified coordinates in any dimension, and there is no error message in the log or chat.
This is inconsistent with other behaviour. For example, the particle command does work at the entity's location in any dimension regardless of the dimension the command or function originates in.
- A function run from #minecraft:tick counts as running in the Overworld.
- A function running on a command block or player runs in the dimension it is in.
Simple demonstration
- Drop an Iron Sword and, without going to another dimension, run the command /execute at @e[type=minecraft:item,nbt={Item:{id:"minecraft:iron_sword"}}] run summon minecraft:armor_stand ~ ~ ~ An Armor Stand will appear at the item's location and the message Summoned new Armor Stand will appear in chat.
- Drop an Iron Sword in the spawn chunks of the Overworld, go to the Nether, and run the above command. The same message will appear in chat, but when you go back to the Overworld there will be no Armor Stand at the item's location.
Example data pack
The attached data pack demonstrates this more exhaustively, and how it is inconsistent with the particle command. There are 3 functions that each execute a secondary function as and at a sword item on the ground. The secondary function:
- Summons an invulnerable, no gravity Armor Stand holding that type of sword at that location.
- Spawns some particles at that location.
- Gives a chat message.
- Kills the item.
The three functions are triggered in different ways:- dimension_execute_test:player_tick - The one for the Wooden Sword is run automatically on each player every tick using an advancement.
- dimension_execute_test:minecraft_tick - The one for the Stone Sword is run automatically before every tick using #minecraft:tick
- dimension_execute_test:manual - The one for the Iron Sword can be run either by a player or in a command block.
Anomalous behaviour includes:- Drop a Stone Sword in the Nether or End. The Armor Stand will not be summoned, but the particles and chat message will appear.
- Drop an Iron Sword in the spawn chunks of the Overworld, go into the Nether or End and run function dimension_execute_test:manual The Armor Stand will not be summoned, but the chat message will appear (and presumably the particles if someone was there to observe it.)
- Put function dimension_execute_test:manual in a repeating, always active Command Block. In dimensions other than the one the Command Block is in, the Armor Stand will not be summoned, but the particles and chat message will appear. (Easiest to test with the Command Block in the spawn chunks of the Overworld.)
- Build a device in the spawn chunks of the Overworld that, after a delay, drops a Wooden Sword. Go into the Nether or End. When the device drops the Wooden Sword the Armor Stand will not be summoned, but the chat message will appear (and presumably the particles if someone was there to observe it.)
Overview
Summoning at an entity via executefails silently if the entity is in a different dimension than the source of the command or function. The entity does not appear at the specified coordinates in any dimension, and there is no error message in the log or chat.
This is inconsistent with other behaviour. For example, the particle command does work at the entity's location in any dimension regardless of the dimension the command or function originates in.
- A function run from #minecraft:tick counts as running in the Overworld.
- A function running on a command block or player runs in the dimension it is in.
Simple demonstration
- Drop an Iron Sword and, without going to another dimension, run the command /execute at @e[type=minecraft:item,nbt={Item:{id:"minecraft:iron_sword"}}] run summon minecraft:armor_stand ~ ~ ~ An Armor Stand will appear at the item's location and the message Summoned new Armor Stand will appear in chat.
- Drop an Iron Sword in the spawn chunks of the Overworld, go to the Nether, and run the above command. The same message will appear in chat, but when you go back to the Overworld there will be no Armor Stand at the item's location.
Example data pack
The attached data pack demonstrates this more exhaustively, and how it is inconsistent with the particle command. There are 3 functions that each execute a secondary function as and at a sword item on the ground. The secondary function:
- Summons an invulnerable, no gravity Armor Stand holding that type of sword at that location.
- Spawns some particles at that location.
- Gives a chat message.
- Kills the item.
The three functions are triggered in different ways:- dimension_execute_test:player_tick - The one for the Wooden Sword is run automatically on each player every tick using an advancement.
- dimension_execute_test:minecraft_tick - The one for the Stone Sword is run automatically before every tick using #minecraft:tick
- dimension_execute_test:manual - The one for the Iron Sword can be run either by a player or in a command block.
Anomalous behaviour includes:- Drop a Stone Sword in the Nether or End. The Armor Stand will not be summoned, but the particles and chat message will appear.
- Drop an Iron Sword in the spawn chunks of the Overworld, go into the Nether or End and run function dimension_execute_test:manual The Armor Stand will not be summoned, but the chat message will appear (and presumably the particles if someone was there to observe it.)
- Put function dimension_execute_test:manual in a repeating, always active Command Block. In dimensions other than the one the Command Block is in, the Armor Stand will not be summoned, but the particles and chat message will appear. (Easiest to test with the Command Block in the spawn chunks of the Overworld.)
- Build a device in the spawn chunks of the Overworld that, after a delay, drops a Wooden Sword. Go into the Nether or End. When the device drops the Wooden Sword the Armor Stand will not be summoned, but the chat message will appear (and presumably the particles if someone was there to observe it.)
Overview
Summoning at an entity via execute fails silently if the entity is in a different dimension than the source of the command or function. The entity does not appear at the specified coordinates in any dimension, and there is no error message in the log or chat.
This is inconsistent with other behaviour. For example, the particle command does work at the entity's location in any dimension regardless of the dimension the command or function originates in.
- A function run from #minecraft:tick counts as running in the Overworld.
- A function running on a command block or player runs in the dimension it is in.
Simple demonstration
- Drop an Iron Sword and, without going to another dimension, run the command /execute at @e[type=minecraft:item,nbt={Item:{id:"minecraft:iron_sword"}}] run summon minecraft:armor_stand ~ ~ ~ An Armor Stand will appear at the item's location and the message Summoned new Armor Stand will appear in chat.
- Drop an Iron Sword in the spawn chunks of the Overworld, go to the Nether, and run the above command. The same message will appear in chat, but when you go back to the Overworld there will be no Armor Stand at the item's location.
Example data pack
The attached data pack demonstrates this more exhaustively, and how it is inconsistent with the particle command. There are 3 functions that each execute a secondary function as and at a sword item on the ground. The secondary function:
- Summons an invulnerable, no gravity Armor Stand holding that type of sword at that location.
- Spawns some particles at that location.
- Gives a chat message.
- Kills the item.
The three functions are triggered in different ways:- dimension_execute_test:player_tick - The one for the Wooden Sword is run automatically on each player every tick using an advancement.
- dimension_execute_test:minecraft_tick - The one for the Stone Sword is run automatically before every tick using #minecraft:tick
- dimension_execute_test:manual - The one for the Iron Sword can be run either by a player or in a command block.
Anomalous behaviour includes:- Drop a Stone Sword in the Nether or End. The Armor Stand will not be summoned, but the particles and chat message will appear.
- Drop an Iron Sword in the spawn chunks of the Overworld, go into the Nether or End and run function dimension_execute_test:manual The Armor Stand will not be summoned, but the chat message will appear (and presumably the particles if someone was there to observe it.)
- Put function dimension_execute_test:manual in a repeating, always active Command Block. In dimensions other than the one the Command Block is in, the Armor Stand will not be summoned, but the particles and chat message will appear. (Easiest to test with the Command Block in the spawn chunks of the Overworld.)
- Build a device in the spawn chunks of the Overworld that, after a delay, drops a Wooden Sword. Go into the Nether or End. When the device drops the Wooden Sword the Armor Stand will not be summoned, but the chat message will appear (and presumably the particles if someone was there to observe it.)
Overview
Summoning at an entity via execute fails silently if the entity is in a different dimension than the source of the command or function. The entity does not appear at the specified coordinates in any dimension, and there is no error message in the log or chat.
This is inconsistent with other behaviour. For example, the particle command does work at the entity's location in any dimension regardless of the dimension the command or function originates in.
- A function run from #minecraft:tick counts as running in the Overworld.
- A function running on a command block or player runs in the dimension it is in.
Simple demonstration
- Drop an Iron Sword and, without going to another dimension, run the command /execute at @e[type=minecraft:item,nbt={Item:{id:"minecraft:iron_sword"}}] run summon minecraft:armor_stand ~ ~ ~ An Armor Stand will appear at the item's location and the message Summoned new Armor Stand will appear in chat.
- Drop an Iron Sword in the spawn chunks of the Overworld, go to the Nether, and run the above command. The same message will appear in chat, but when you go back to the Overworld there will be no Armor Stand at the item's location.
Example data pack
The attached data pack demonstrates this more exhaustively, and how it is inconsistent with the particle command. There are 3 functions that each execute a secondary function as and at a sword item on the ground. The secondary function:
- Summons an invulnerable, no gravity Armor Stand holding that type of sword at that location.
- Spawns some particles at that location.
- Gives a chat message.
- Kills the item.
The three functions are triggered in different ways:- dimension_execute_test:player_tick - The one for the Wooden Sword is run automatically on each player every tick using an advancement.
- dimension_execute_test:minecraft_tick - The one for the Stone Sword is run automatically before every tick using #minecraft:tick
- dimension_execute_test:manual - The one for the Iron Sword can be run either by a player or in a command block.
Anomalous behaviour includes:- Drop a Stone Sword in the Nether or End. The Armor Stand will not be summoned, but the particles and chat message will appear.
- Drop an Iron Sword in the spawn chunks of the Overworld, go into the Nether or End and run function dimension_execute_test:manual The Armor Stand will not be summoned, but the chat message will appear (and presumably the particles if someone was there to observe it.)
- Put function dimension_execute_test:manual in a repeating, always active Command Block. In dimensions other than the one the Command Block is in, the Armor Stand will not be summoned, but the particles and chat message will appear. (Easiest to test with the Command Block in the spawn chunks of the Overworld.)
- Build a device in the spawn chunks of the Overworld that, after a delay, drops a Wooden Sword. Go into the Nether or End. When the device drops the Wooden Sword the Armor Stand will not be summoned, but the chat message will appear (and presumably the particles if someone was there to observe it.)
Overview
Summoning at an entity via execute fails silently if the entity is in a different dimension than the source of the command or function. The entity does not appear at the specified coordinates in any dimension, and there is no error message in the log or chat.
This is inconsistent with other behaviour. For example, the particle command does work at the entity's location in any dimension regardless of the dimension the command or function originates in.
- A function run from #minecraft:tick counts as running in the Overworld.
- A function running on a command block or player runs in the dimension it is in.
Simple demonstration
- Drop an Iron Sword and, without going to another dimension, run the command /execute at @e[type=minecraft:item,nbt={Item:{id:"minecraft:iron_sword"}}] run summon minecraft:armor_stand ~ ~ ~ An Armor Stand will appear at the item's location and the message Summoned new Armor Stand will appear in chat.
- Drop an Iron Sword in the spawn chunks of the Overworld, go to the Nether, and run the above command. The same message will appear in chat, but when you go back to the Overworld there will be no Armor Stand at the item's location.
Example data pack
The attached data pack demonstrates this more exhaustively, and how it is inconsistent with the particle command. There are 3 functions that each execute a secondary function as and at a sword item on the ground. The secondary function:
- Summons an invulnerable, no gravity Armor Stand holding that type of sword at that location.
- Spawns some particles at that location.
- Gives a chat message.
- Kills the item.
The three functions are triggered in different ways:
- dimension_execute_test:player_tick - The one for the Wooden Sword is run automatically on each player every tick using an advancement.
- dimension_execute_test:minecraft_tick - The one for the Stone Sword is run automatically before every tick using #minecraft:tick
- dimension_execute_test:manual - The one for the Iron Sword can be run either by a player or in a command block.
Anomalous behaviour includes:
- Drop a Stone Sword in the Nether or End. The Armor Stand will not be summoned, but the particles and chat message will appear.
- Drop an Iron Sword in the spawn chunks of the Overworld, go into the Nether or End and run function dimension_execute_test:manual The Armor Stand will not be summoned, but the chat message will appear (and presumably the particles if someone was there to observe it.)
- Put function dimension_execute_test:manual in a repeating, always active Command Block. In dimensions other than the one the Command Block is in, the Armor Stand will not be summoned, but the particles and chat message will appear. (Easiest to test with the Command Block in the spawn chunks of the Overworld.)
- Build a device in the spawn chunks of the Overworld that, after a delay, drops a Wooden Sword. Go into the Nether or End. When the device drops the Wooden Sword the Armor Stand will not be summoned, but the chat message will appear (and presumably the particles if someone was there to observe it.)
Overview
Summoning at an entity via execute fails silently if the entity is in a different dimension than the source of the command or function. The entity does not appear at the specified coordinates in any dimension, and there is no error message in the log or chat.
This is inconsistent with other behaviour. For example, the particle command does work at the entity's location in any dimension regardless of the dimension the command or function originates in.
- A function run from #minecraft:tick counts as running in the Overworld.
- A function running on a command block or player runs in the dimension it is in.
Simple demonstration
- Drop an Iron Sword and, without going to another dimension, run the command /execute at @e[type=minecraft:item,nbt={Item:{id:"minecraft:iron_sword"}}] run summon minecraft:armor_stand ~ ~ ~ An Armor Stand will appear at the item's location and the message Summoned new Armor Stand will appear in chat.
- Drop an Iron Sword in the spawn chunks of the Overworld, go to the Nether, and run the above command. The same message will appear in chat, but when you go back to the Overworld there will be no Armor Stand at the item's location.
Example data pack
The attached data pack demonstrates this more exhaustively, and how it is inconsistent with the particle command. There are 3 functions that each execute a secondary function as and at a sword item on the ground. The secondary function:
- Summons an invulnerable, no gravity Armor Stand holding that type of sword at that location.
- Spawns some particles at that location.
- Gives a chat message.
- Kills the item.
The three functions are triggered in different ways:
- dimension_execute_test:player_tick - The one for the Wooden Sword is run automatically on each player every tick using an advancement.
- dimension_execute_test:minecraft_tick - The one for the Stone Sword is run automatically before every tick using #minecraft:tick
- dimension_execute_test:manual - The one for the Iron Sword can be run either by a player or in a command block.
Anomalous behaviour includes:
- Drop a Stone Sword in the Nether or End. The Armor Stand will not be summoned, but the particles and chat message will appear.
- Drop an Iron Sword in the spawn chunks of the Overworld, go into the Nether or End and run function dimension_execute_test:manual The Armor Stand will not be summoned, but the chat message will appear (and presumably the particles if someone was there to observe it.)
- Put function dimension_execute_test:manual in a repeating, always active Command Block. In dimensions other than the one the Command Block is in, the Armor Stand will not be summoned, but the particles and chat message will appear. (Easiest to test with the Command Block in the spawn chunks of the Overworld.)
- Build a device in the spawn chunks of the Overworld that, after a delay, drops a Wooden Sword. Go into the Nether or End. When the device drops the Wooden Sword the Armor Stand will not be summoned, but the chat message will appear (and presumably the particles if someone was there to observe it.)
Overview
Summoning at an entity via execute fails silently if the entity is in a different dimension than the source of the command or function. The entity does not appear at the specified coordinates in any dimension, and there is no error message in the log or chat.
This is inconsistent with other behaviour. For example, the particle command does work at the entity's location in any dimension regardless of the dimension the command or function originates in.
- A function run from #minecraft:tick counts as running in the Overworld.
- A function running on a command block or player runs in the dimension it is in.
Simple demonstration
- Drop an Iron Sword and, without going to another dimension, run the command /execute at @e[type=minecraft:item,nbt={Item:{id:"minecraft:iron_sword"}}] run summon minecraft:armor_stand ~ ~ ~ An Armor Stand will appear at the item's location and the message Summoned new Armor Stand will appear in chat.
- Drop an Iron Sword in the spawn chunks of the Overworld, go to the Nether, and run the above command. The same message will appear in chat, but when you go back to the Overworld there will be no Armor Stand at the item's location.
Example data pack
The attached data pack demonstrates this more exhaustively, and how it is inconsistent with the particle command. There are 3 functions that each execute a secondary function as and at a sword item on the ground. The secondary function:
- Summons an invulnerable, no gravity Armor Stand holding that type of sword at that location.
- Spawns some particles at that location.
- Gives a chat message.
- Kills the item.
The three functions are triggered in different ways:
- dimension_execute_test:player_tick - The one for the Wooden Sword is run automatically on each player every tick using an advancement.
- dimension_execute_test:minecraft_tick - The one for the Stone Sword is run automatically before every tick using #minecraft:tick
- dimension_execute_test:manual - The one for the Iron Sword can be run either by a player or in a command block.
Anomalous behaviour includes:
- Drop a Stone Sword in the Nether or End. The Armor Stand will not be summoned, but the particles and chat message will appear.
- Drop an Iron Sword in the spawn chunks of the Overworld, go into the Nether or End and run function dimension_execute_test:manual The Armor Stand will not be summoned, but the chat message will appear (and presumably the particles will too if someone was there to observe it.)
- Put function dimension_execute_test:manual in a repeating, always active Command Block. In dimensions other than the one the Command Block is in, the Armor Stand will not be summoned, but the particles and chat message will appear. (Easiest to test with the Command Block in the spawn chunks of the Overworld.)
- Build a device in the spawn chunks of the Overworld that, after a delay, drops a Wooden Sword. Go into the Nether or End. When the device drops the Wooden Sword the Armor Stand will not be summoned, but the chat message will appear (and presumably the particles will too if someone was there to observe it.)
Overview
Summoning at an entity via execute fails silently if the entity is in a different dimension than the source of the command or function. The entity does not appear at the specified coordinates in any dimension, and there is no error message in the log or chat.
This is inconsistent with other behaviour. For example, the particle command does work at the entity's location in any dimension regardless of the dimension the command or function originates in.
- A function run from #minecraft:tick counts as running in the Overworld.
- A function running on a command block or player runs in the dimension it is in.
Simple demonstration
- Drop an Iron Sword and, without going to another dimension, run the command /execute at @e[type=minecraft:item,nbt={Item:{id:"minecraft:iron_sword"}}] run summon minecraft:armor_stand ~ ~ ~ An Armor Stand will appear at the item's location and the message Summoned new Armor Stand will appear in chat.
- Drop an Iron Sword in the spawn chunks of the Overworld, go to the Nether, and run the above command. The same message will appear in chat, but when you go back to the Overworld there will be no Armor Stand at the item's location.
Example data pack
The attached data pack demonstrates this more exhaustively, and how it is inconsistent with the particle command. There are 3 functions that each execute a secondary function as and at a sword item on the ground. The secondary function:
- Summons an invulnerable, no gravity Armor Stand holding that type of sword at that location.
- Spawns some particles at that location.
- Gives a chat message.
- Kills the item.
The three functions are triggered in different ways:
- dimension_execute_test:player_tick - The one for the Wooden Sword is run automatically on each player every tick using an advancement.
- dimension_execute_test:minecraft_tick - The one for the Stone Sword is run automatically before every tick using #minecraft:tick
- dimension_execute_test:manual - The one for the Iron Sword can be run either by a player or in a command block.
Anomalous behaviour includes:
- Drop a Stone Sword in the Nether or End. The Armor Stand will not be summoned, but the particles and chat message will appear.
- Drop an Iron Sword in the spawn chunks of the Overworld, go into the Nether or End and run function dimension_execute_test:manual The Armor Stand will not be summoned, but the chat message will appear (and presumably the particles will too if someone was there to observe it.)
- Put function dimension_execute_test:manual in a repeating, always active Command Block. In dimensions other than the one the Command Block is in, the Armor Stand will not be summoned, but the particles and chat message will appear. (Easiest to test with the Command Block in the spawn chunks of the Overworld.)
- Build a device in the spawn chunks of the Overworld that, after a delay, drops a Wooden Sword. Go into the Nether or End. When the device drops the Wooden Sword the Armor Stand will not be summoned, but the chat message will appear (and presumably the particles will too if someone was there to observe it.)
Overview
Summoning at an entity via execute fails silently if the entity is in a different dimension than the source of the command or function. The entity does not appear at the specified coordinates in any dimension, and there is no error message in the log or chat.
This is inconsistent with other behaviour. For example, the particle command does work at the entity's location in any dimension regardless of the dimension the command or function originates in.
- A function run from #minecraft:tick counts as running in the Overworld.
- A function running on a command block or player runs in the dimension it is in.
Simple demonstration
- Drop an Iron Sword and, without going to another dimension, run the command /execute at @e[type=minecraft:item,nbt={Item:{id:"minecraft:iron_sword"}}] run summon minecraft:armor_stand ~ ~ ~
- An Armor Stand will appear at the item's location and the message Summoned new Armor Stand will appear in chat.
- Drop an Iron Sword in the spawn chunks of the Overworld, go to the Nether, and run the above command. The same message will appear in chat, but when you go back to the Overworld there will be no Armor Stand at the item's location.
Example data pack
The attached data pack demonstrates this more exhaustively, and how it is inconsistent with the particle command. There are 3 functions that each execute a secondary function as and at a sword item on the ground. The secondary function:
- Summons an invulnerable, no gravity Armor Stand holding that type of sword at that location.
- Spawns some particles at that location.
- Gives a chat message.
- Kills the item.
The three functions are triggered in different ways:
- dimension_execute_test:player_tick - The one for the Wooden Sword is run automatically on each player every tick using an advancement.
- dimension_execute_test:minecraft_tick - The one for the Stone Sword is run automatically before every tick using #minecraft:tick
- dimension_execute_test:manual - The one for the Iron Sword can be run either by a player or in a command block.
Anomalous behaviour includes:
- Drop a Stone Sword in the Nether or End. The Armor Stand will not be summoned, but the particles and chat message will appear.
- Drop an Iron Sword in the spawn chunks of the Overworld, go into the Nether or End and run function dimension_execute_test:manual The Armor Stand will not be summoned, but the chat message will appear (and presumably the particles will too if someone was there to observe it.)
- Put function dimension_execute_test:manual in a repeating, always active Command Block. In dimensions other than the one the Command Block is in, the Armor Stand will not be summoned, but the particles and chat message will appear. (Easiest to test with the Command Block in the spawn chunks of the Overworld.)
- Build a device in the spawn chunks of the Overworld that, after a delay, drops a Wooden Sword. Go into the Nether or End. When the device drops the Wooden Sword the Armor Stand will not be summoned, but the chat message will appear (and presumably the particles will too if someone was there to observe it.)
Overview
Summoning at an entity via execute fails silently if the entity is in a different dimension than the source of the command or function. The entity does not appear at the specified coordinates in any dimension, and there is no error message in the log or chat.
This is inconsistent with other behaviour. For example, the particle command does work at the entity's location in any dimension regardless of the dimension the command or function originates in.
- A function run from #minecraft:tick counts as running in the Overworld.
- A function
running ona command block or player runs in the dimension it is in.Simple demonstration
- Drop an Iron Sword and, without going to another dimension, run the command /execute at @e[type=minecraft:item,nbt={Item:{id:"minecraft:iron_sword"}}] run summon minecraft:armor_stand ~ ~ ~
- An Armor Stand will appear at the item's location and the message Summoned new Armor Stand will appear in chat.
- Drop an Iron Sword in the spawn chunks of the Overworld, go to the Nether, and run the above command. The same message will appear in chat, but when you go back to the Overworld there will be no Armor Stand at the item's location.
Example data pack
The attached data pack demonstrates this more exhaustively, and how it is inconsistent with the particle command. There are 3 functions that each execute a secondary function as and at a sword item on the ground. The secondary function:
- Summons an invulnerable, no gravity Armor Stand holding that type of sword at that location.
- Spawns some particles at that location.
- Gives a chat message.
- Kills the item.
The three functions are triggered in different ways:
- dimension_execute_test:player_tick - The one for the Wooden Sword is run automatically on each player every tick using an advancement.
- dimension_execute_test:minecraft_tick - The one for the Stone Sword is run automatically before every tick using #minecraft:tick
- dimension_execute_test:manual - The one for the Iron Sword can be run either by a player or in a command block.
Anomalous behaviour includes:
- Drop a Stone Sword in the Nether or End. The Armor Stand will not be summoned, but the particles and chat message will appear.
- Drop an Iron Sword in the spawn chunks of the Overworld, go into the Nether or End and run function dimension_execute_test:manual The Armor Stand will not be summoned, but the chat message will appear (and presumably the particles will too if someone was there to observe it.)
- Put function dimension_execute_test:manual in a repeating, always active Command Block. In dimensions other than the one the Command Block is in, the Armor Stand will not be summoned, but the particles and chat message will appear. (Easiest to test with the Command Block in the spawn chunks of the Overworld.)
- Build a device in the spawn chunks of the Overworld that, after a delay, drops a Wooden Sword. Go into the Nether or End. When the device drops the Wooden Sword the Armor Stand will not be summoned, but the chat message will appear (and presumably the particles will too if someone was there to observe it.)
Overview
Summoning at an entity via execute fails silently if the entity is in a different dimension than the source of the command or function. The entity does not appear at the specified coordinates in any dimension, and there is no error message in the log or chat.
This is inconsistent with other behaviour. For example, the particle command does work at the entity's location in any dimension regardless of the dimension the command or function originates in.
- A function run from #minecraft:tick counts as running in the Overworld.
- A function or command run by a command block or player runs in the dimension it is in.
Simple demonstration
- Drop an Iron Sword and, without going to another dimension, run the command /execute at @e[type=minecraft:item,nbt={Item:{id:"minecraft:iron_sword"}}] run summon minecraft:armor_stand ~ ~ ~
- An Armor Stand will appear at the item's location and the message Summoned new Armor Stand will appear in chat.
- Drop an Iron Sword in the spawn chunks of the Overworld, go to the Nether, and run the above command. The same message will appear in chat, but when you go back to the Overworld there will be no Armor Stand at the item's location.
Example data pack
The attached data pack demonstrates this more exhaustively, and how it is inconsistent with the particle command. There are 3 functions that each execute a secondary function as and at a sword item on the ground. The secondary function:
- Summons an invulnerable, no gravity Armor Stand holding that type of sword at that location.
- Spawns some particles at that location.
- Gives a chat message.
- Kills the item.
The three functions are triggered in different ways:
- dimension_execute_test:player_tick - The one for the Wooden Sword is run automatically on each player every tick using an advancement.
- dimension_execute_test:minecraft_tick - The one for the Stone Sword is run automatically before every tick using #minecraft:tick
- dimension_execute_test:manual - The one for the Iron Sword can be run either by a player or in a command block.
Anomalous behaviour includes:
- Drop a Stone Sword in the Nether or End. The Armor Stand will not be summoned, but the particles and chat message will appear.
- Drop an Iron Sword in the spawn chunks of the Overworld, go into the Nether or End and run function dimension_execute_test:manual The Armor Stand will not be summoned, but the chat message will appear (and presumably the particles will too if someone was there to observe it.)
- Put function dimension_execute_test:manual in a repeating, always active Command Block. In dimensions other than the one the Command Block is in, the Armor Stand will not be summoned, but the particles and chat message will appear. (Easiest to test with the Command Block in the spawn chunks of the Overworld.)
- Build a device in the spawn chunks of the Overworld that, after a delay, drops a Wooden Sword. Go into the Nether or End. When the device drops the Wooden Sword the Armor Stand will not be summoned, but the chat message will appear (and presumably the particles will too if someone was there to observe it.)
Overview
Summoning at an entity via execute fails silently if the entity is in a different dimension than the source of the command or function. The entity does not appear at the specified coordinates in any dimension, and there is no error message in the log or chat.
This is inconsistent with other behaviour. For example, the particle command does work at the entity's location in any dimension regardless of the dimension the command or function originates in.
- A function run from{{ #minecraft:tick}} counts as running in the Overworld.
- A function or command run by a command block or player runs in the dimension it is in.
Simple demonstration
- Drop an Iron Sword and, without going to another dimension, run the command /execute at @e[type=minecraft:item,nbt={Item:{id:"minecraft:iron_sword"}}] run summon minecraft:armor_stand ~ ~ ~
- An Armor Stand will appear at the item's location and the message Summoned new Armor Stand will appear in chat.
- Drop an Iron Sword in the spawn chunks of the Overworld, go to the Nether, and run the above command. The same message will appear in chat, but when you go back to the Overworld there will be no Armor Stand at the item's location.
Example data pack
The attached data pack demonstrates this more exhaustively, and how it is inconsistent with the particle command. There are 3 functions that each execute a secondary function as and at a sword item on the ground. The secondary function:
- Summons an invulnerable, no gravity Armor Stand holding that type of sword at that location.
- Spawns some particles at that location.
- Gives a chat message.
- Kills the item.
The three functions are triggered in different ways:
- dimension_execute_test:player_tick - The one for the Wooden Sword is run automatically on each player every tick using an advancement.
- dimension_execute_test:minecraft_tick - The one for the Stone Sword is run automatically before every tick using #minecraft:tick
- dimension_execute_test:manual - The one for the Iron Sword can be run either by a player or in a command block.
Anomalous behaviour includes:
- Drop a Stone Sword in the Nether or End. The Armor Stand will not be summoned, but the particles and chat message will appear.
- Drop an Iron Sword in the spawn chunks of the Overworld, go into the Nether or End and run function dimension_execute_test:manual The Armor Stand will not be summoned, but the chat message will appear (and presumably the particles will too if someone was there to observe it.)
- Put function dimension_execute_test:manual in a repeating, always active Command Block. In dimensions other than the one the Command Block is in, the Armor Stand will not be summoned, but the particles and chat message will appear. (Easiest to test with the Command Block in the spawn chunks of the Overworld.)
- Build a device in the spawn chunks of the Overworld that, after a delay, drops a Wooden Sword. Go into the Nether or End. When the device drops the Wooden Sword the Armor Stand will not be summoned, but the chat message will appear (and presumably the particles will too if someone was there to observe it.)
Overview
Summoning at an entity via execute fails silently if the entity is in a different dimension than the source of the command or function. The entity does not appear at the specified coordinates in any dimension, and there is no error message in the log or chat.
This is inconsistent with other behaviour. For example, the particle command does work at the entity's location in any dimension regardless of the dimension the command or function originates in.
- A function run from{{ #minecraft:tick}} counts as running in the Overworld.
- A function or command run by a command block or player runs in the dimension it is in.
Simple demonstration
- Drop an Iron Sword and, without going to another dimension, run the command /execute at @e[type=minecraft:item,nbt={Item:{id:"minecraft:iron_sword"}}] run summon minecraft:armor_stand ~ ~ ~
- An Armor Stand will appear at the item's location and the message Summoned new Armor Stand will appear in chat.
- Drop an Iron Sword in the spawn chunks of the Overworld, go to the Nether, and run the above command. The same message will appear in chat, but when you go back to the Overworld there will be no Armor Stand at the item's location.
Example data pack
The attached data pack demonstrates this more exhaustively, and how it is inconsistent with the particle command. There are 3 functions that each execute a secondary function as and at a sword item on the ground. The secondary function:
- Summons an invulnerable, no gravity Armor Stand holding that type of sword at that location.
- Spawns some particles at that location.
- Gives a chat message.
- Kills the item.
The three functions are triggered in different ways:
- dimension_execute_test:player_tick - The one for the Wooden Sword is run automatically on each player every tick using an advancement.
- dimension_execute_test:minecraft_tick - The one for the Stone Sword is run automatically before every tick using #minecraft:tick
- dimension_execute_test:manual - The one for the Iron Sword can be run either by a player or in a command block.
Anomalous behaviour includes:
- Drop a Stone Sword in the Nether or End. The Armor Stand will not be summoned, but the particles and chat message will appear.
- Drop an Iron Sword in the spawn chunks of the Overworld, go into the Nether or End and run function dimension_execute_test:manual The Armor Stand will not be summoned, but the chat message will appear (and presumably the particles will too if someone was there to observe it.)
- Put function dimension_execute_test:manual in a repeating, always active Command Block. In dimensions other than the one the Command Block is in, the Armor Stand will not be summoned, but the particles and chat message will appear. (Easiest to test with the Command Block in the spawn chunks of the Overworld.)
- Build a device in the spawn chunks of the Overworld that, after a delay, drops a Wooden Sword. Go into the Nether or End. When the device drops the Wooden Sword the Armor Stand will not be summoned, but the chat message will appear (and presumably the particles will too if someone was there to observe it.)
Overview
Summoning at an entity via execute fails silently if the entity is in a different dimension than the source of the command or function. The entity does not appear at the specified coordinates in any dimension, and there is no error message in the log or chat.
This is inconsistent with other behaviour. For example, the particle command does work at the entity's location in any dimension regardless of the dimension the command or function originates in.
- A function run from #minecraft:tick counts as running in the Overworld.
- A function or command run by a command block or player runs in the dimension it is in.
Simple demonstration
- Drop an Iron Sword and, without going to another dimension, run the command /execute at @e[type=minecraft:item,nbt={Item:{id:"minecraft:iron_sword"}}] run summon minecraft:armor_stand ~ ~ ~
- An Armor Stand will appear at the item's location and the message Summoned new Armor Stand will appear in chat.
- Drop an Iron Sword in the spawn chunks of the Overworld, go to the Nether, and run the above command. The same message will appear in chat, but when you go back to the Overworld there will be no Armor Stand at the item's location.
Example data pack
The attached data pack demonstrates this more exhaustively, and how it is inconsistent with the particle command. There are 3 functions that each execute a secondary function as and at a sword item on the ground. The secondary function:
- Summons an invulnerable, no gravity Armor Stand holding that type of sword at that location.
- Spawns some particles at that location.
- Gives a chat message.
- Kills the item.
The three functions are triggered in different ways:
- dimension_execute_test:player_tick - The one for the Wooden Sword is run automatically on each player every tick using an advancement.
- dimension_execute_test:minecraft_tick - The one for the Stone Sword is run automatically before every tick using #minecraft:tick
- dimension_execute_test:manual - The one for the Iron Sword can be run either by a player or in a command block.
Anomalous behaviour includes:
- Drop a Stone Sword in the Nether or End. The Armor Stand will not be summoned, but the particles and chat message will appear.
- Drop an Iron Sword in the spawn chunks of the Overworld, go into the Nether or End and run function dimension_execute_test:manual The Armor Stand will not be summoned, but the chat message will appear (and presumably the particles will too if someone was there to observe it.)
- Put function dimension_execute_test:manual in a repeating, always active Command Block. In dimensions other than the one the Command Block is in, the Armor Stand will not be summoned, but the particles and chat message will appear. (Easiest to test with the Command Block in the spawn chunks of the Overworld.)
- Build a device in the spawn chunks of the Overworld that, after a delay, drops a Wooden Sword. Go into the Nether or End. When the device drops the Wooden Sword the Armor Stand will not be summoned, but the chat message will appear (and presumably the particles will too if someone was there to observe it.)
Overview
Summoning at an entity via execute fails silently if the entity is in a different dimension than the source of the command or function. The entity does not appear at the specified coordinates in any dimension, and there is no error message in the log or chat.
This is inconsistent with other behaviour. For example, the particlecommand does work at the entity's location in any dimension regardless of the dimension the command or function originates in.
- A function run from #minecraft:tick counts as running in the Overworld.
- A function or command run by a command block or player runs in the dimension it is in.
Simple demonstration
- Drop an Iron Sword and, without going to another dimension, run the command /execute at @e[type=minecraft:item,nbt={Item:{id:"minecraft:iron_sword"}}] run summon minecraft:armor_stand ~ ~ ~
- An Armor Stand will appear at the item's location and the message Summoned new Armor Stand will appear in chat.
- Drop an Iron Sword in the spawn chunks of the Overworld, go to the Nether, and run the above command. The same message will appear in chat, but when you go back to the Overworld there will be no Armor Stand at the item's location.
Example data pack
The attached data pack demonstrates this more exhaustively, and how it is inconsistent with the particle command. There are 3 functions that each execute a secondary function as and at a sword item on the ground. The secondary function:
- Summons an invulnerable, no gravity Armor Stand holding that type of sword at that location.
- Spawns some particles at that location.
- Gives a chat message.
- Kills the item.
The three functions are triggered in different ways:
- dimension_execute_test:player_tick - The one for the Wooden Sword is run automatically on each player every tick using an advancement.
- dimension_execute_test:minecraft_tick - The one for the Stone Sword is run automatically before every tick using #minecraft:tick
- dimension_execute_test:manual - The one for the Iron Sword can be run either by a player or in a command block.
Anomalous behaviour
includes:
- Drop a Stone Sword in the Nether or End. The Armor Stand will not be summoned, but the particles and chat message will appear.
- Drop an Iron Sword in the spawn chunks of the Overworld, go into the Nether or End and run function dimension_execute_test:manual The Armor Stand will not be summoned, but the chat message will appear (and presumably the particles w
illtoo if someone was there to observe it.)- Put function dimension_execute_test:manual in a repeating, always active Command Block. In dimensions other than the one the Command Block is in, the Armor Stand will not be summoned, but the particles and chat message will appear. (Easiest to test with the Command Block in the spawn chunks of the Overworld.)
- Build a device in the spawn chunks of the Overworld that, after a delay, drops a Wooden Sword. Go into the Nether or End. When the device drops the Wooden Sword the Armor Stand will not be summoned, but the chat message will appear (and presumably the particles w
illtoo if someone was there to observe it.)Overview
Summoning at an entity via execute fails silently if the entity is in a different dimension than the source of the command or function. The entity does not appear at the specified coordinates in any dimension, and there is no error message in the log or chat.
This is inconsistent with other behaviour. For example, the particle command does work at the entity's location in any dimension regardless of the dimension the command or function originates in.
- A function run from #minecraft:tick counts as running in the Overworld.
- A function or command run by a command block or player runs in the dimension it is in.
Simple demonstration
- Drop an Iron Sword and, without going to another dimension, run the command /execute at @e[type=minecraft:item,nbt={Item:{id:"minecraft:iron_sword"}}] run summon minecraft:armor_stand ~ ~ ~
- An Armor Stand will appear at the item's location and the message Summoned new Armor Stand will appear in chat.
- Drop an Iron Sword in the spawn chunks of the Overworld, go to the Nether, and run the above command. The same message will appear in chat, but when you go back to the Overworld there will be no Armor Stand at the item's location.
Example data pack
The attached data pack demonstrates this more exhaustively, and how it is inconsistent with the particle command. There are 3 functions that each execute a secondary function as and at a sword item on the ground. The secondary function:
- Summons an invulnerable, no gravity Armor Stand holding that type of sword at that location.
- Spawns some particles at that location.
- Gives a chat message.
- Kills the item.
The three functions are triggered in different ways:
- dimension_execute_test:player_tick - The one for the Wooden Sword is run automatically on each player every tick using an advancement.
- dimension_execute_test:minecraft_tick - The one for the Stone Sword is run automatically before every tick using #minecraft:tick
- dimension_execute_test:manual - The one for the Iron Sword can be run either by a player or in a command block.
Anomalous behaviour:
- Drop a Stone Sword in the Nether or End. The Armor Stand will not be summoned, but the particles and chat message will appear.
- Drop an Iron Sword in the spawn chunks of the Overworld, go into the Nether or End and run function dimension_execute_test:manual The Armor Stand will not be summoned, but the chat message will appear (and presumably the particles would too if someone was there to observe it.)
- Put function dimension_execute_test:manual in a repeating, always active Command Block. If you drop an Iron Sword in dimensions other than the one the Command Block is in, the Armor Stand will not be summoned, but the particles and chat message will appear. (Easiest to test with the Command Block in the spawn chunks of the Overworld.)
- Build a device in the spawn chunks of the Overworld that, after a delay, drops a Wooden Sword. Go into the Nether or End. When the device drops the Wooden Sword the Armor Stand will not be summoned, but the chat message will appear (and presumably the particles would too if someone was there to observe it.)
This is still happening in Minecraft 1.8-pre 2. It locked up in single player upon the first firework launched.
Still an issue in 15w44a. Can't right click the boat to enter it or left click it to break it,
Ah, that's a shame. I was hoping to use this in a data pack to teleport a player to somewhere a vast distance away, then later back to where they were. Chunk loading would mean that teleporting to an entity would be unlikely to work, and the teleport command doesn't accept scoreboard data as inputs. Position seems like perhaps the one thing that could be safe to be editable, given that the teleport command exists.
I'll have to try that. I had assumed that moving an entity to an unloaded chunk would mean it would instantly unload, so commands not work on it.
I'll do that. Thanks for the help.
Thanks. I have corrected those. I wondered if perhaps the formatting had become stricter and that would fix it, but alas it still doesn't work.
The particle command works for me in 17w48a.
Are particles on Minimal or Decreased in video settings?
I am sorry for those repeated edits I did to the description as I made mistakes with the formatting spamming the feed.