MC-124222When using /execute store or if/unless score, execute sub-commands only run (for each entity), if store/score entity selector finds at least one entity for each execution
The bug
This is basically MC-121934, but only for certain cases. Currently known to be affected:
- /execute store (result|success) entity
- /execute store (result|success) score
- /execute (if|unless) score
Reproduction steps for store, provided by @Brian McNamara:
/summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","A"]}
/summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","B"]}
/scoreboard objectives add X dummy
/scoreboard objectives setdisplay sidebar X
/scoreboard players set @e[tag=foo] X 42
/execute as @e[tag=foo] at @s store result score @s[tag=A] X run say hi
/execute as @e[tag=foo] at @s store result score @s[tag=B] X run say hi
/execute as @e[tag=foo] at @s store result score @s[tag=foo] X run say hi
Expected behavior: In the last 3 lines, A and B to update the score of each respective pig only, and the final line updates both scores.
Actual behavior: The first 2 of the last 3 lines fail and only the final line updates both scores.
Reproduction steps for if/unless score:
/summon armor_stand ~ ~ ~ {NoGravity:1b,Marker:1b,Tags:[A],CustomName:"\"A1\""}
/execute at @e[tag=A] run summon armor_stand ~ ~ ~1 {NoGravity:1b,Marker:1b,Tags:[A],CustomName:"\"A2\""}
/scoreboard objectives add X dummy
/scoreboard objectives setdisplay sidebar X
/scoreboard players set @e[tag=A] X 1
/execute as @e[tag=A] at @s positioned ~ ~ ~1 run say @e[distance=..0.1]
/execute as @e[tag=A] at @s positioned ~ ~ ~1 if entity @e[tag=A,distance=..0.1,limit=1] run say hi
/execute as @e[tag=A] at @s positioned ~ ~ ~1 if score @e[tag=A,distance=..0.1,limit=1] X = @s X run say hi
The third to last line is just to ensure the setup is correct, expected (and actual) output is
[A1] A2 [A2]
The second to last line is to demonstrate that 'execute..as..at..if entity' works with a particular selector, it correctly outputs "[A1] hi".
The final line fails "No entity found". It should succeed exactly as the previous line does, since the scores match (all are 1).
Code analysis
Code analysis by Brian McNamara can be found in this comment.
Linked Issues
Created Issue:
Either Execute or Tags are broken
So, I have no idea if this bug is because of execute being broken, or the tag selector argument being broken, however, there is an issue with it:
The first picture (or should be) is the command:
{wms_uuid=0}] at @s run say hi`
`/execute as @e[type=area_effect_cloud,tag=_wand,scores=
- now this seems to work as intended, makes all the correct entities say "hi".
Now, this is where I'm not entirely sure if this is the execute part or the tag part that is broken, because, in the second image, I have the command:
`/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say @s[tag=_scaffold]`
- this command still highlights all entities, however, only the _scaffold AEC actually says the name of itself - Whether this is meant to be the correct choice or if all three AEC's should've said `_scaffold", I have no idea.
Lastly, where the system truly is broken, my last command is:
{wms_uuid=0}
`/execute as @e[type=area_effect_cloud,tag=_wand,scores=] at @s store result score @s[tag=_scaffold] wms_uuid run say hi`
- this last command registers "No entity was found" even though clearly it does exist, so again, I am not entirely sure what the deal is with it.
If any further commands are needed, or the world file or even a video, I'll gladly provide it as I need this bug fixed.
Attachments3
So, I have no idea if this bug is because of execute being broken, or the tag selector argument being broken, however, there is an issue with it:
The first picture (or should be) is the command:
{wms_uuid=0}] at @s run say hi`
`/execute as @e[type=area_effect_cloud,tag=_wand,scores=
- now this seems to work as intended, makes all the correct entities say "hi".
Now, this is where I'm not entirely sure if this is the execute part or the tag part that is broken, because, in the second image, I have the command:
`/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say @s[tag=_scaffold]`
- this command still highlights all entities, however, only the _scaffold AEC actually says the name of itself - Whether this is meant to be the correct choice or if all three AEC's should've said `_scaffold", I have no idea.
Lastly, where the system truly is broken, my last command is:
{wms_uuid=0}
`/execute as @e[type=area_effect_cloud,tag=_wand,scores=] at @s store result score @s[tag=_scaffold] wms_uuid run say hi`
- this last command registers "No entity was found" even though clearly it does exist, so again, I am not entirely sure what the deal is with it.
If any further commands are needed, or the world file or even a video, I'll gladly provide it as I need this bug fixed.
So, I have no idea if this bug is because of execute being broken, or the tag selector argument being broken, however, there is an issue with it:
The first picture (or should be) is the command:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say hi
- now this seems to work as intended, makes all the correct entities say "hi".
Now, this is where I'm not entirely sure if this is the execute part or the tag part that is broken, because, in the second image, I have the command:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say @s[tag=_scaffold]
- this command still highlights all entities, however, only the _scaffold AEC actually says the name of itself - Whether this is meant to be the correct choice or if all three AEC's should've said `_scaffold", I have no idea.
Lastly, where the system truly is broken, my last command is:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s store result score @s[tag=_scaffold] wms_uuid run say hi
- this last command registers "No entity was found" even though clearly it does exist, so again, I am not entirely sure what the deal is with it.
If any further commands are needed, or the world file or even a video, I'll gladly provide it as I need this bug fixed.
So, I have no idea if this bug is because of execute being broken, or the tag selector argument being broken, however, there is an issue with it:
The first picture (or should be) is the command:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say hi
- now this seems to work as intended, makes all the correct entities say "hi".
Now, this is where I'm not entirely sure if this is the execute part or the tag part that is broken, because, in the second image, I have the command:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say @s[tag=_scaffold]
- this command still highlights all entities, however, only the _scaffold AEC actually says the name of itself - Whether this is meant to be the correct choice or if all three AEC's should've said `_scaffold", I have no idea.
Lastly, where the system truly is broken, my
lastcommand is:/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s store result score @s[tag=_scaffold] wms_uuid run say hi
- this last command registers "No entity was found" even though clearly it does exist, so again, I am not entirely sure what the deal is with it.
If any further commands are needed, or the world file or even a video, I'll gladly provide it as I need this bug fixed.
So, I have no idea if this bug is because of execute being broken, or the tag selector argument being broken, however, there is an issue with it:
The first picture (or should be) is the command:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say hi
- now this seems to work as intended, makes all the correct entities say "hi".
Now, this is where I'm not entirely sure if this is the execute part or the tag part that is broken, because, in the second image, I have the command:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say @s[tag=_scaffold]
- this command still highlights all entities, however, only the _scaffold AEC actually says the name of itself - Whether this is meant to be the correct choice or if all three AEC's should've said `_scaffold", I have no idea.
Lastly, where the system truly is broken, my command is:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s store result score @s[tag=_scaffold] wms_uuid run say hi
- this last command registers "No entity was found" even though clearly
itdoes exist, so again, I am not entirely sure what the deal is with it.If any further commands are needed, or the world file or even a video, I'll gladly provide it as I need this bug fixed.
So, I have no idea if this bug is because of execute being broken, or the tag selector argument being broken, however, there is an issue with it:
The first picture (or should be) is the command:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say hi
- now this seems to work as intended, makes all the correct entities say "hi".
Now, this is where I'm not entirely sure if this is the execute part or the tag part that is broken, because, in the second image, I have the command:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say @s[tag=_scaffold]
- this command still highlights all entities, however, only the _scaffold AEC actually says the name of itself - Whether this is meant to be the correct choice or if all three AEC's should've said `_scaffold", I have no idea.
Lastly, where the system truly is broken, my command is:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s store result score @s[tag=_scaffold] wms_uuid run say hi
- this last command registers "No entity was found" even though it clearly does exist, so again, I am not entirely sure what the deal is with it.
If any further commands are needed, or the world file or even a video, I'll gladly provide it as I need this bug fixed.
So, I have no idea if this bug is because of execute being broken, or the tag selector argument being broken, however, there is an issue with it:
The first picture (or should be) is the command:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say hi
- now this seems to work as intended, makes all the correct entities say "hi".
Now, this is where I'm not entirely sure if this is the execute part or the tag part that is broken, because, in the second image, I have the command:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say @s[tag=_scaffold]
- this command still highlights all entities, however, only the _scaffold AEC actually says the name of itself - Whether this is meant to be the correct choice or if all three AEC's should've said `_scaffold", I have no idea.
Lastly, where the system truly is broken, my command is:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s store result score @s[tag=_scaffold] wms_uuid run say hi
- this last command registers "No entity was found" even though it clearly does exist
, so again, I am not entirely sure what the deal is with it.If any further commands are needed, or the world file or even a video, I'll gladly provide it as I need this bug fixed.
So, I have no idea if this bug is because of execute being broken, or the tag selector argument being broken, however, there is an issue with it:
The first picture (or should be) is the command:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say hi
- now this seems to work as intended, makes all the correct entities say "hi".
Now, this is where I'm not entirely sure if this is the execute part or the tag part that is broken, because, in the second image, I have the command:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say @s[tag=_scaffold]
- this command still highlights all entities, however, only the _scaffold AEC actually says the name of itself - Whether this is meant to be the correct choice or if all three AEC's should've said `_scaffold", I have no idea.
Lastly, where the system truly is broken, my command is:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s store result score @s[tag=_scaffold] wms_uuid run say hi
- this last command registers "No entity was found" even though it clearly does exist. So again, I am not entirely sure what the deal is with it, be it execute or the tag selector argument, but this definitely popped out to me as strange and buggy behavior.
If any further commands are needed, or the world file or even a video, I'll gladly provide it as I need this bug fixed.
EitherExecuteor Tags are brokenExecute is just utterly broken it seems
So, I have no idea if this bug is because of execute being broken, or the tag selector argument being broken, however, there is an issue with it:
The first picture (or should be) is the command:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say hi
- now this seems to work as intended, makes all the correct entities say "hi".
Now, this is where I'm not entirely sure if this is the execute part or the tag part that is broken, because, in the second image, I have the command:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say @s[tag=_scaffold]
- this command still highlights all entities,
however,only the _scaffold AEC actually says the name of itself- Whether this is meant to be the correct choice or if all three AEC's should've said `_scaffold", I have no idea.Lastly, where the system truly is broken, my command is:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s store result score @s[tag=_scaffold] wms_uuid run say hi
- this last command registers "No entity was found" even though it clearly does exist. So again, I am not entirely sure what the deal is with it, be it execute or the tag selector argument, but this definitely popped out to me as strange and buggy behavior.
If any further commands are needed, or the world file or even a video, I'll gladly provide it as I need this bug fixed.
So, I have no idea if this bug is because of execute being broken, or the tag selector argument being broken, however, there is an issue with it:
The first picture (or should be) is the command:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say hi
- now this seems to work as intended, makes all the correct entities say "hi".
Now, this is where I'm not entirely sure if this is the execute part or the tag part that is broken, because, in the second image, I have the command:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say @s[tag=_scaffold]
- this command still highlights all entities, and only the _scaffold AEC actually says the name of itself.
Lastly, where the system truly is broken, my command is:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s store result score @s[tag=_scaffold] wms_uuid run say hi
- this last command registers "No entity was found" even though it clearly does exist. So again, I am not entirely sure what the deal is with it, be it execute or the tag selector argument, but this definitely popped out to me as strange and buggy behavior.
If any further commands are needed, or the world file or even a video, I'll gladly provide it as I need this bug fixed.
So, I have no idea if this bug is because of execute being broken, or the tag selector argument being broken, however, there is an issue with it:
The first picture (or should be) is the command:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say hi
- now this seems to work as intended, makes all the correct entities say "hi".
Now,
this is where I'm not entirely sure if this is the execute part or the tag part that is broken, because, in the second image, I have the command:/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say @s[tag=_scaffold]
- this command still highlights all entities, and only the _scaffold AEC actually says the name of itself.
Lastly, where the system truly is broken, my command is:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s store result score @s[tag=_scaffold] wms_uuid run say hi
- this last command registers "No entity was found" even though it clearly does exist. So again, I am not entirely sure what the deal is with it, be it execute or the tag selector argument, but this definitely popped out to me as strange and buggy behavior.
If any further commands are needed, or the world file or even a video, I'll gladly provide it as I need this bug fixed.
So, I have no idea if this bug is because of execute being broken, or the tag selector argument being broken, however, there is an issue with it:
The first picture (or should be) is the command:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say hi
- now this seems to work as intended, makes all the correct entities say "hi".
Now, secondly, to prove that the _scaffold is working properly:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say @s[tag=_scaffold]
- this command still highlights all entities, and only the _scaffold AEC actually says the name of itself.
Lastly, where the system truly is broken, my command is:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s store result score @s[tag=_scaffold] wms_uuid run say hi
- this last command registers "No entity was found" even though it clearly does exist. So again, I am not entirely sure what the deal is with it, be it execute or the tag selector argument, but this definitely popped out to me as strange and buggy behavior.
If any further commands are needed, or the world file or even a video, I'll gladly provide it as I need this bug fixed.
Executeis just utterly broken it seemsExecute feels broken
Executefeels brokenExecute or @s + tag is broken.
Execute or @s + tag is broken.When using /execute store, execute sub-commands only run (for each entity), if store entity selector finds at least one entity for each execution
This is basically
Here are repro steps:
/summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","A"]} /summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","B"]} /scoreboard objectives add X dummy /scoreboard objectives setdisplay sidebar X /scoreboard players set @e[tag=foo] X 42 /execute as @e[tag=foo] at @s store result score @s[tag=A] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=B] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=foo] X run say hiIn the last 3 lines, EXPECT the A and B to update score of each respective pig only, and final foo line to update both. ACTUAL is that A and B lines fail, but final line does update both scores.
So, I have no idea if this bug is because of execute being broken, or the tag selector argument being broken, however, there is an issue with it:
The first picture (or should be) is the command:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say hi
- now this seems to work as intended, makes all the correct entities say "hi".
Now, secondly, to prove that the _scaffold is working properly:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say @s[tag=_scaffold]
- this command still highlights all entities, and only the _scaffold AEC actually says the name of itself.
Lastly, where the system truly is broken, my command is:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s store result score @s[tag=_scaffold] wms_uuid run say hi
- this last command registers "No entity was found" even though it clearly does exist. So again, I am not entirely sure what the deal is with it, be it execute or the tag selector argument, but this definitely popped out to me as strange and buggy behavior.
If any further commands are needed, or the world file or even a video, I'll gladly provide it as I need this bug fixed.
This is basically
Here are repro steps:
/summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","A"]} /summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","B"]} /scoreboard objectives add X dummy /scoreboard objectives setdisplay sidebar X /scoreboard players set @e[tag=foo] X 42 /execute as @e[tag=foo] at @s store result score @s[tag=A] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=B] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=foo] X run say hiIn the last 3 lines, EXPECT the A and B to update score of each respective pig only, and final foo line to update both. ACTUAL is that A and B lines fail, but final line does update both scores.
So, I have no idea if this bug is because of execute being broken, or the tag selector argument being broken, however, there is an issue with it:
The first picture (or should be) is the command:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say hi
- now this seems to work as intended, makes all the correct entities say "hi".
Now, secondly, to prove that the _scaffold is working properly:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s run say @s[tag=_scaffold]
- this command still highlights all entities, and only the _scaffold AEC actually says the name of itself.
Lastly, where the system truly is broken, my command is:
/execute as @e[type=area_effect_cloud,tag=_wand,scores={wms_uuid=0}] at @s store result score @s[tag=_scaffold] wms_uuid run say hi
- this last command registers "No entity was found" even though it clearly does exist. So again, I am not entirely sure what the deal is with it, be it execute or the tag selector argument, but this definitely popped out to me as strange and buggy behavior.
If any further commands are needed, or the world file or even a video, I'll gladly provide it as I need this bug fixed.
This is basically
MC-121934, but only for /execute store.Reproduction steps provided by @Brian McNamara:
/summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","A"]} /summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","B"]} /scoreboard objectives add X dummy /scoreboard objectives setdisplay sidebar X /scoreboard players set @e[tag=foo] X 42 /execute as @e[tag=foo] at @s store result score @s[tag=A] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=B] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=foo] X run say hiExpected behavior: In the last 3 lines, A and B to update the score of each respective pig only, and the final line updates both scores.
Actual behavior: The first 2 of the last 3 lines fail and only the final line updates both scores.
When using /execute store or if/unless score, execute sub-commands only run (for each entity), if store entity selector finds at least one entity for each execution
This is basically
MC-121934, but only for /execute store.Reproduction steps provided by @Brian McNamara:
/summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","A"]} /summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","B"]} /scoreboard objectives add X dummy /scoreboard objectives setdisplay sidebar X /scoreboard players set @e[tag=foo] X 42 /execute as @e[tag=foo] at @s store result score @s[tag=A] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=B] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=foo] X run say hiExpected behavior: In the last 3 lines, A and B to update the score of each respective pig only, and the final line updates both scores.
Actual behavior: The first 2 of the last 3 lines fail and only the final line updates both scores.Alternative reproduction steps here.
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
This is basically
MC-121934, but only for /execute store.Reproduction steps provided by @Brian McNamara:
/summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","A"]} /summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","B"]} /scoreboard objectives add X dummy /scoreboard objectives setdisplay sidebar X /scoreboard players set @e[tag=foo] X 42 /execute as @e[tag=foo] at @s store result score @s[tag=A] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=B] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=foo] X run say hiExpected behavior: In the last 3 lines, A and B to update the score of each respective pig only, and the final line updates both scores.
Actual behavior: The first 2 of the last 3 lines fail and only the final line updates both scores.
Alternative reproduction stepshere.The bug
This is basically
MC-121934, but only for /execute store.Reproduction steps provided by @Brian McNamara:
/summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","A"]} /summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","B"]} /scoreboard objectives add X dummy /scoreboard objectives setdisplay sidebar X /scoreboard players set @e[tag=foo] X 42 /execute as @e[tag=foo] at @s store result score @s[tag=A] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=B] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=foo] X run say hiExpected behavior: In the last 3 lines, A and B to update the score of each respective pig only, and the final line updates both scores.
Actual behavior: The first 2 of the last 3 lines fail and only the final line updates both scores.Alternative reproduction steps here.
Code analysis
Code analysis by Brian McNamara can be found here.
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
The bug
This is basically
MC-121934, but only for /execute store.Reproduction steps provided by @Brian McNamara:
/summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","A"]} /summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","B"]} /scoreboard objectives add X dummy /scoreboard objectives setdisplay sidebar X /scoreboard players set @e[tag=foo] X 42 /execute as @e[tag=foo] at @s store result score @s[tag=A] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=B] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=foo] X run say hiExpected behavior: In the last 3 lines, A and B to update the score of each respective pig only, and the final line updates both scores.
Actual behavior: The first 2 of the last 3 lines fail and only the final line updates both scores.Alternative reproduction steps here.
Code analysis
Code analysis by Brian McNamara can be found
here.The bug
This is basically
MC-121934, but only for /execute store.Reproduction steps provided by @Brian McNamara:
/summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","A"]} /summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","B"]} /scoreboard objectives add X dummy /scoreboard objectives setdisplay sidebar X /scoreboard players set @e[tag=foo] X 42 /execute as @e[tag=foo] at @s store result score @s[tag=A] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=B] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=foo] X run say hiExpected behavior: In the last 3 lines, A and B to update the score of each respective pig only, and the final line updates both scores.
Actual behavior: The first 2 of the last 3 lines fail and only the final line updates both scores.Alternative reproduction steps here.
Code analysis
Code analysis by Brian McNamara can be found in this comment.
When using /execute store or if/unless score, execute sub-commands only run (for each entity), if store/score entity selector finds at least one entity for each execution
The bug
This is basically
MC-121934, but only for /execute store.Reproduction steps
provided by @Brian McNamara:/summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","A"]} /summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","B"]} /scoreboard objectives add X dummy /scoreboard objectives setdisplay sidebar X /scoreboard players set @e[tag=foo] X 42 /execute as @e[tag=foo] at @s store result score @s[tag=A] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=B] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=foo] X run say hiExpected behavior: In the last 3 lines, A and B to update the score of each respective pig only, and the final line updates both scores.
Actual behavior: The first 2 of the last 3 lines fail and only the final line updates both scores.Alternative reproduction steps he
re.Code analysis
Code analysis by Brian McNamara can be found in this comment.
The bug
This is basically
MC-121934, but only for /execute store.Reproduction steps for store, provided by @Brian McNamara:
/summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","A"]} /summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","B"]} /scoreboard objectives add X dummy /scoreboard objectives setdisplay sidebar X /scoreboard players set @e[tag=foo] X 42 /execute as @e[tag=foo] at @s store result score @s[tag=A] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=B] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=foo] X run say hiExpected behavior: In the last 3 lines, A and B to update the score of each respective pig only, and the final line updates both scores.
Actual behavior: The first 2 of the last 3 lines fail and only the final line updates both scores.
Reproduction steps for if/unless score:
/summon armor_stand ~ ~ ~ {NoGravity:1b,Marker:1b,Tags:[A],CustomName:"\"A1\""} /execute at @e[tag=A] run summon armor_stand ~ ~ ~1 {NoGravity:1b,Marker:1b,Tags:[A],CustomName:"\"A2\""} /scoreboard objectives add X dummy /scoreboard objectives setdisplay sidebar X /scoreboard players set @e[tag=A] X 1 /execute as @e[tag=A] at @s positioned ~ ~ ~1 run say @e[distance=..0.1] /execute as @e[tag=A] at @s positioned ~ ~ ~1 if entity @e[tag=A,distance=..0.1,limit=1] run say hi /execute as @e[tag=A] at @s positioned ~ ~ ~1 if score @e[tag=A,distance=..0.1,limit=1] X = @s X run say hiThe third to last line is just to ensure the setup is correct, expected (and actual) output is
[A1] A2 [A2]The second to last line is to demonstrate that 'execute..as..at..if entity' works with a particular selector, it correctly outputs "[A1] hi".
The final line fails "No entity found". It should succeed exactly as the previous line does, since the scores match (all are 1).
Code analysis
Code analysis by Brian McNamara can be found in this comment.
The bug
This is basically
MC-121934, but only for /execute store.Reproduction steps for store, provided by @Brian McNamara:
/summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","A"]} /summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","B"]} /scoreboard objectives add X dummy /scoreboard objectives setdisplay sidebar X /scoreboard players set @e[tag=foo] X 42 /execute as @e[tag=foo] at @s store result score @s[tag=A] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=B] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=foo] X run say hiExpected behavior: In the last 3 lines, A and B to update the score of each respective pig only, and the final line updates both scores.
Actual behavior: The first 2 of the last 3 lines fail and only the final line updates both scores.
Reproduction steps for if/unless score:
/summon armor_stand ~ ~ ~ {NoGravity:1b,Marker:1b,Tags:[A],CustomName:"\"A1\""} /execute at @e[tag=A] run summon armor_stand ~ ~ ~1 {NoGravity:1b,Marker:1b,Tags:[A],CustomName:"\"A2\""} /scoreboard objectives add X dummy /scoreboard objectives setdisplay sidebar X /scoreboard players set @e[tag=A] X 1 /execute as @e[tag=A] at @s positioned ~ ~ ~1 run say @e[distance=..0.1] /execute as @e[tag=A] at @s positioned ~ ~ ~1 if entity @e[tag=A,distance=..0.1,limit=1] run say hi /execute as @e[tag=A] at @s positioned ~ ~ ~1 if score @e[tag=A,distance=..0.1,limit=1] X = @s X run say hiThe third to last line is just to ensure the setup is correct, expected (and actual) output is
[A1] A2 [A2]The second to last line is to demonstrate that 'execute..as..at..if entity' works with a particular selector, it correctly outputs "[A1] hi".
The final line fails "No entity found". It should succeed exactly as the previous line does, since the scores match (all are 1).
Code analysis
Code analysis by Brian McNamara can be found in this comment.
The bug
This is basically
MC-121934, but only for certain cases. Currently known to be affected:
- /execute store (result|success) entity
- /execute store (success|result) score
- /execute (if|unless) score.
Reproduction steps for store, provided by @Brian McNamara:
/summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","A"]} /summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","B"]} /scoreboard objectives add X dummy /scoreboard objectives setdisplay sidebar X /scoreboard players set @e[tag=foo] X 42 /execute as @e[tag=foo] at @s store result score @s[tag=A] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=B] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=foo] X run say hiExpected behavior: In the last 3 lines, A and B to update the score of each respective pig only, and the final line updates both scores.
Actual behavior: The first 2 of the last 3 lines fail and only the final line updates both scores.
Reproduction steps for if/unless score:
/summon armor_stand ~ ~ ~ {NoGravity:1b,Marker:1b,Tags:[A],CustomName:"\"A1\""} /execute at @e[tag=A] run summon armor_stand ~ ~ ~1 {NoGravity:1b,Marker:1b,Tags:[A],CustomName:"\"A2\""} /scoreboard objectives add X dummy /scoreboard objectives setdisplay sidebar X /scoreboard players set @e[tag=A] X 1 /execute as @e[tag=A] at @s positioned ~ ~ ~1 run say @e[distance=..0.1] /execute as @e[tag=A] at @s positioned ~ ~ ~1 if entity @e[tag=A,distance=..0.1,limit=1] run say hi /execute as @e[tag=A] at @s positioned ~ ~ ~1 if score @e[tag=A,distance=..0.1,limit=1] X = @s X run say hiThe third to last line is just to ensure the setup is correct, expected (and actual) output is
[A1] A2 [A2]The second to last line is to demonstrate that 'execute..as..at..if entity' works with a particular selector, it correctly outputs "[A1] hi".
The final line fails "No entity found". It should succeed exactly as the previous line does, since the scores match (all are 1).
Code analysis
Code analysis by Brian McNamara can be found in this comment.
The bug
This is basically
MC-121934, but only for certain cases. Currently known to be affected:
- /execute store (result|success) entity
- /execute store (success
|result) score- /execute (if|unless) score.
Reproduction steps for store, provided by @Brian McNamara:
/summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","A"]} /summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","B"]} /scoreboard objectives add X dummy /scoreboard objectives setdisplay sidebar X /scoreboard players set @e[tag=foo] X 42 /execute as @e[tag=foo] at @s store result score @s[tag=A] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=B] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=foo] X run say hiExpected behavior: In the last 3 lines, A and B to update the score of each respective pig only, and the final line updates both scores.
Actual behavior: The first 2 of the last 3 lines fail and only the final line updates both scores.
Reproduction steps for if/unless score:
/summon armor_stand ~ ~ ~ {NoGravity:1b,Marker:1b,Tags:[A],CustomName:"\"A1\""} /execute at @e[tag=A] run summon armor_stand ~ ~ ~1 {NoGravity:1b,Marker:1b,Tags:[A],CustomName:"\"A2\""} /scoreboard objectives add X dummy /scoreboard objectives setdisplay sidebar X /scoreboard players set @e[tag=A] X 1 /execute as @e[tag=A] at @s positioned ~ ~ ~1 run say @e[distance=..0.1] /execute as @e[tag=A] at @s positioned ~ ~ ~1 if entity @e[tag=A,distance=..0.1,limit=1] run say hi /execute as @e[tag=A] at @s positioned ~ ~ ~1 if score @e[tag=A,distance=..0.1,limit=1] X = @s X run say hiThe third to last line is just to ensure the setup is correct, expected (and actual) output is
[A1] A2 [A2]The second to last line is to demonstrate that 'execute..as..at..if entity' works with a particular selector, it correctly outputs "[A1] hi".
The final line fails "No entity found". It should succeed exactly as the previous line does, since the scores match (all are 1).
Code analysis
Code analysis by Brian McNamara can be found in this comment.
The bug
This is basically
MC-121934, but only for certain cases. Currently known to be affected:
- /execute store (result|success) entity
- /execute store (result|success) score
- /execute (if|unless) score.
Reproduction steps for store, provided by @Brian McNamara:
/summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","A"]} /summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","B"]} /scoreboard objectives add X dummy /scoreboard objectives setdisplay sidebar X /scoreboard players set @e[tag=foo] X 42 /execute as @e[tag=foo] at @s store result score @s[tag=A] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=B] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=foo] X run say hiExpected behavior: In the last 3 lines, A and B to update the score of each respective pig only, and the final line updates both scores.
Actual behavior: The first 2 of the last 3 lines fail and only the final line updates both scores.
Reproduction steps for if/unless score:
/summon armor_stand ~ ~ ~ {NoGravity:1b,Marker:1b,Tags:[A],CustomName:"\"A1\""} /execute at @e[tag=A] run summon armor_stand ~ ~ ~1 {NoGravity:1b,Marker:1b,Tags:[A],CustomName:"\"A2\""} /scoreboard objectives add X dummy /scoreboard objectives setdisplay sidebar X /scoreboard players set @e[tag=A] X 1 /execute as @e[tag=A] at @s positioned ~ ~ ~1 run say @e[distance=..0.1] /execute as @e[tag=A] at @s positioned ~ ~ ~1 if entity @e[tag=A,distance=..0.1,limit=1] run say hi /execute as @e[tag=A] at @s positioned ~ ~ ~1 if score @e[tag=A,distance=..0.1,limit=1] X = @s X run say hiThe third to last line is just to ensure the setup is correct, expected (and actual) output is
[A1] A2 [A2]The second to last line is to demonstrate that 'execute..as..at..if entity' works with a particular selector, it correctly outputs "[A1] hi".
The final line fails "No entity found". It should succeed exactly as the previous line does, since the scores match (all are 1).
Code analysis
Code analysis by Brian McNamara can be found in this comment.
The bug
This is basically
MC-121934, but only for certain cases. Currently known to be affected:
- /execute store (result|success) entity
- /execute store (result|success) score
- /execute (if|unless) score.
Reproduction steps for store, provided by @Brian McNamara:
/summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","A"]} /summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","B"]} /scoreboard objectives add X dummy /scoreboard objectives setdisplay sidebar X /scoreboard players set @e[tag=foo] X 42 /execute as @e[tag=foo] at @s store result score @s[tag=A] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=B] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=foo] X run say hiExpected behavior: In the last 3 lines, A and B to update the score of each respective pig only, and the final line updates both scores.
Actual behavior: The first 2 of the last 3 lines fail and only the final line updates both scores.
Reproduction steps for if/unless score:
/summon armor_stand ~ ~ ~ {NoGravity:1b,Marker:1b,Tags:[A],CustomName:"\"A1\""} /execute at @e[tag=A] run summon armor_stand ~ ~ ~1 {NoGravity:1b,Marker:1b,Tags:[A],CustomName:"\"A2\""} /scoreboard objectives add X dummy /scoreboard objectives setdisplay sidebar X /scoreboard players set @e[tag=A] X 1 /execute as @e[tag=A] at @s positioned ~ ~ ~1 run say @e[distance=..0.1] /execute as @e[tag=A] at @s positioned ~ ~ ~1 if entity @e[tag=A,distance=..0.1,limit=1] run say hi /execute as @e[tag=A] at @s positioned ~ ~ ~1 if score @e[tag=A,distance=..0.1,limit=1] X = @s X run say hiThe third to last line is just to ensure the setup is correct, expected (and actual) output is
[A1] A2 [A2]The second to last line is to demonstrate that 'execute..as..at..if entity' works with a particular selector, it correctly outputs "[A1] hi".
The final line fails "No entity found". It should succeed exactly as the previous line does, since the scores match (all are 1).
Code analysis
Code analysis by Brian McNamara can be found in this comment.
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
[Mojang] Nathan Adams
Testing reveals this is actually
MC-121934for store. Description needs to be updated.Here are repro steps:
/summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","A"]} /summon minecraft:pig ~ ~ ~ {NoAI:1b,Tags:["foo","B"]} /scoreboard objectives add X dummy /scoreboard objectives setdisplay sidebar X /scoreboard players set @e[tag=foo] X 42 /execute as @e[tag=foo] at @s store result score @s[tag=A] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=B] X run say hi /execute as @e[tag=foo] at @s store result score @s[tag=foo] X run say hiIn the last 3 lines, EXPECT the A and B to update score of each respective pig only, and final foo line to update both. ACTUAL is that A and B lines fail, but final line does update both scores.
Here are the repro steps for the 'score' version of the bug:
/summon armor_stand ~ ~ ~ {NoGravity:1b,Marker:1b,Tags:[A],CustomName:"\"A1\""} /execute at @e[tag=A] run summon armor_stand ~ ~ ~1 {NoGravity:1b,Marker:1b,Tags:[A],CustomName:"\"A2\""} /scoreboard objectives add X dummy /scoreboard objectives setdisplay sidebar X /scoreboard players set @e[tag=A] X 1 /execute as @e[tag=A] at @s positioned ~ ~ ~1 run say @e[distance=..0.1] /execute as @e[tag=A] at @s positioned ~ ~ ~1 if entity @e[tag=A,distance=..0.1,limit=1] run say hi /execute as @e[tag=A] at @s positioned ~ ~ ~1 if score @e[tag=A,distance=..0.1,limit=1] X = @s X run say hiThe third to last line is just to ensure the setup is correct, expected (and actual) output is
The second to last line is to demonstrate that 'execute..as..at..if entity' works with a particular selector, it correctly outputs "[A1] hi".
The final line fails "No entity found". It should succeed exactly as the previous line does, since the scores match (all are 1).
After poking through the decompiled code, I think the problem is that various 'scoreholder contexts' for entity selectors are throwing exceptions, rather than simply returning empy collections and failure results. Exceptions should not be used for 'expected failures' such as 'selector that targets no entities', as it breaks the overall control flow through an execute subcommand loop. It might be non-trivial to find all such exception-sources in the source code via inspection, however an appropriate exception handler at the 'root' of commands (e.g. whatever existing handler is printing out the red "No entity was found" message in chat) that logs the stack traces of these caught-exceptions could be used to help find all the call stacks which throw exceptions inappropriately, so they may be fixed over time.