-
Bug
-
Resolution: Awaiting Response
-
None
-
1.20.72 Hotfix
-
Unconfirmed
-
Windows
/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