MCPE-179932/execute unless entity @p run command does not execute when entity is killed
/execute unless entity @p run sub command
When command is entered from a command block it will not execute the sub command when entity test succeeds
Steps to Reproduce: (see screenshot)
1. Set up two scoreboards using the following commands:
/scoreboard objectives add kills dummy
/Scoreboard objectives add killsdisplay dummy
/Scoreboard objectives setdisplay list
2. Set up two chains of command blocks facing up three blocks from each other, with an observer facing out from your impulse command followed by a piece of redstone dust and a comparator facing the opposite direction
First chain:
Impulse Unconditional Needs Redstone
/Scoreboard objectives remove killsdisplay
Chain Unconditional Always Active
/Scoreboard objectives add killsdisplay dummy kills
Chain Unconditional Always Active
/Scoreboard objectives setdisplay list killsdisplay
Second chain:
Repeat Unconditional Always Active
/Testfor @a
Chain Conditional Always Active
/Scoreboard players add @a kills 0
Chain Conditional Always Active
/Execute at @a run scoreboard players operation @p killsdisplay= @p kills
3.One last chain of command blocks:
Repeat Unconditional Always Active
/Testfor @e[tag=Wave1]
Repeat Conditional Always Active Delay in Ticks: 1
/Execute unless entity @e[tag=Wave1] run scoreboard players add @p kills 1
4. Tag a singular entity with /tag @e[r=1] add Wave1
5. Kill entity
Observed Results:
The scoreboard should increase by 1 for whomever was nearest the final command block chain and yet it does not. This was working prior to the 1.20.71 &1.20.72 hotfixes. Upon further inspection, any /execute unless entity @p run subcommand command does not run when the entity or entities specified are killed
Attachments1
Created Issue:
/execute unless entity @p[tag=] does not execute when entity is killed
/execute unless...
When command is entered from a command block no longer works
/execute unless...
When command is entered from a command block no longer works
Steps to Reproduce: (see screenshot)
1. Set up two scoreboards using the following commands:
/scoreboard objectives add kills dummy
/Scoreboard objectives add killsdisplay dummy
/Scoreboard objectives setdisplay list
2. Set up two chains of command blocks facing up three blocks from each other, with an observer facing out from your impulse command followed by a piece of redstone dust and a comparator facing the opposite direction
First chain:
Impulse Unconditional Needs Redstone
/Scoreboard objectives remove killsdisplay
Chain Unconditional Always Active
/Scoreboard objectives add killsdisplay dummy kills
Chain Unconditional Always Active
/Scoreboard objectives setdisplay list killsdisplay
Second chain:
Repeat Unconditional Always Active
/Testfor @a
Chain Conditional Always Active
/Scoreboard players add @a kills 0
Chain Conditional Always Active
/Execute at @a run scoreboard players operation @p killsdisplay= @p kills
3.One last chain of command blocks:
Repeat Unconditional Always Active
/Testfor @e[tag=Wave1]
Repeat Conditional Always Active Delay in Ticks: 1
/Execute unless entity @e[tag=Wave1] run scoreboard players add @p kills 1
4. Tag a singular entity with /tag @e[r=1] add Wave1
5. Kill entity
Observed Results:
The scoreboard should increase by 1 for whomever was nearest the final command block chain and yet it does not. This was working prior to the 1.20.71 &1.20.72 hotfixes
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
/execute unless
...When command is entered from a command block
no longer works
Steps to Reproduce: (see screenshot)
1. Set up two scoreboards using the following commands:
/scoreboard objectives add kills dummy/Scoreboard objectives add killsdisplay dummy
/Scoreboard objectives setdisplay list
2. Set up two chains of command blocks facing up three blocks from each other, with an observer facing out from your impulse command followed by a piece of redstone dust and a comparator facing the opposite direction
First chain:
Impulse Unconditional Needs Redstone
/Scoreboard objectives remove killsdisplay
Chain Unconditional Always Active
/Scoreboard objectives add killsdisplay dummy kills
Chain Unconditional Always Active
/Scoreboard objectives setdisplay list killsdisplay
Second chain:
Repeat Unconditional Always Active
/Testfor @a
Chain Conditional Always Active
/Scoreboard players add @a kills 0
Chain Conditional Always Active
/Execute at @a run scoreboard players operation @p killsdisplay= @p kills
3.One last chain of command blocks:
Repeat Unconditional Always Active
/Testfor @e[tag=Wave1]
Repeat Conditional Always Active Delay in Ticks: 1
/Execute unless entity @e[tag=Wave1] run scoreboard players add @p kills 1
4. Tag a singular entity with /tag @e[r=1] add Wave1
5. Kill entity
Observed Results:
The scoreboard should increase by 1 for whomever was nearest the final command block chain and yet it does not. This was working prior to the 1.20.71 &1.20.72 hotfixes
/execute unless entity @p run sub command
When command is entered from a command block it will not execute the sub command when entity test succeeds
Steps to Reproduce: (see screenshot)
1. Set up two scoreboards using the following commands:
/scoreboard objectives add kills dummy
/Scoreboard objectives add killsdisplay dummy
/Scoreboard objectives setdisplay list
2. Set up two chains of command blocks facing up three blocks from each other, with an observer facing out from your impulse command followed by a piece of redstone dust and a comparator facing the opposite direction
First chain:
Impulse Unconditional Needs Redstone
/Scoreboard objectives remove killsdisplay
Chain Unconditional Always Active
/Scoreboard objectives add killsdisplay dummy kills
Chain Unconditional Always Active
/Scoreboard objectives setdisplay list killsdisplay
Second chain:
Repeat Unconditional Always Active
/Testfor @a
Chain Conditional Always Active
/Scoreboard players add @a kills 0
Chain Conditional Always Active
/Execute at @a run scoreboard players operation @p killsdisplay= @p kills
3.One last chain of command blocks:
Repeat Unconditional Always Active
/Testfor @e[tag=Wave1]
Repeat Conditional Always Active Delay in Ticks: 1
/Execute unless entity @e[tag=Wave1] run scoreboard players add @p kills 1
4. Tag a singular entity with /tag @e[r=1] add Wave1
5. Kill entity
Observed Results:
The scoreboard should increase by 1 for whomever was nearest the final command block chain and yet it does not. This was working prior to the 1.20.71 &1.20.72 hotfixes
/execute unless entity @p[tag=]does not execute when entity is killed/execute unless entity @p run command does not execute when entity is killed
/execute unless entity @p run sub command
When command is entered from a command block it will not execute the sub command when entity test succeeds
Steps to Reproduce: (see screenshot)
1. Set up two scoreboards using the following commands:
/scoreboard objectives add kills dummy
/Scoreboard objectives add killsdisplay dummy
/Scoreboard objectives setdisplay list
2. Set up two chains of command blocks facing up three blocks from each other, with an observer facing out from your impulse command followed by a piece of redstone dust and a comparator facing the opposite direction
First chain:
Impulse Unconditional Needs Redstone
/Scoreboard objectives remove killsdisplay
Chain Unconditional Always Active
/Scoreboard objectives add killsdisplay dummy kills
Chain Unconditional Always Active
/Scoreboard objectives setdisplay list killsdisplay
Second chain:
Repeat Unconditional Always Active
/Testfor @a
Chain Conditional Always Active
/Scoreboard players add @a kills 0
Chain Conditional Always Active
/Execute at @a run scoreboard players operation @p killsdisplay= @p kills
3.One last chain of command blocks:
Repeat Unconditional Always Active
/Testfor @e[tag=Wave1]
Repeat Conditional Always Active Delay in Ticks: 1
/Execute unless entity @e[tag=Wave1] run scoreboard players add @p kills 1
4. Tag a singular entity with /tag @e[r=1] add Wave1
5. Kill entity
Observed Results:
The scoreboard should increase by 1 for whomever was nearest the final command block chain and yet it does not. This was working prior to the 1.20.71 &1.20.72 hotfixes
/execute unless entity @p run sub command
When command is entered from a command block it will not execute the sub command when entity test succeeds
Steps to Reproduce: (see screenshot)
1. Set up two scoreboards using the following commands:
/scoreboard objectives add kills dummy
/Scoreboard objectives add killsdisplay dummy
/Scoreboard objectives setdisplay list
2. Set up two chains of command blocks facing up three blocks from each other, with an observer facing out from your impulse command followed by a piece of redstone dust and a comparator facing the opposite direction
First chain:
Impulse Unconditional Needs Redstone
/Scoreboard objectives remove killsdisplay
Chain Unconditional Always Active
/Scoreboard objectives add killsdisplay dummy kills
Chain Unconditional Always Active
/Scoreboard objectives setdisplay list killsdisplay
Second chain:
Repeat Unconditional Always Active
/Testfor @a
Chain Conditional Always Active
/Scoreboard players add @a kills 0
Chain Conditional Always Active
/Execute at @a run scoreboard players operation @p killsdisplay= @p kills
3.One last chain of command blocks:
Repeat Unconditional Always Active
/Testfor @e[tag=Wave1]
Repeat Conditional Always Active Delay in Ticks: 1
/Execute unless entity @e[tag=Wave1] run scoreboard players add @p kills 1
4. Tag a singular entity with /tag @e[r=1] add Wave1
5. Kill entity
Observed Results:
The scoreboard should increase by 1 for whomever was nearest the final command block chain and yet it does not. This was working prior to the 1.20.71 &1.20.72 hotfixes. Upon further inspection, any /execute unless entity @p run subcommand command does not run when the entity or entities specified are killed
![[MCQA] Bartłomiej Słodkowski](../../../data/avatars/users/18941.svg){kind=small}
Your report does not contain enough information to understand or reproduce the problem.
Please add the following information to the Description, as shown here:
Try following your steps to make sure you include everything and can still reproduce the issue yourself.
Screenshots and videos are helpful, but should not be used as a replacement for the above information
This report has been temporarily resolved as Awaiting Response. It will automatically reopen when you add information. Please follow the format shown and include all sections (steps, observed, expected). Reports that do not contain all of the requested information and complete steps to reproduce the issue may be closed as Incomplete. For more information please read the Bug Tracker Guidelines.
Many players find this Bug Report Creation Form useful for filling in all helpful information.
Updated with additional details and information
Please attach a copy of the world with all the command blocks and setup necessary to reproduce the bug, as this will facilitate the process of testing for others.
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response.
Is this still an issue in the latest version? If yes, could you please add it to the affected versions (or mention it if you are not the reporter)?
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📓 Project Summary – 📧 Suggestions – 📖 Minecraft Wiki