When I was trying out the new testforblock command replacement in 1.13-pre2, I set up a scoreboard command, which would track a piece of endstone, and when it was broken, it should decrement the scoreboard by 1 and replace the block. These are the setup commands, with their command block types:
(Impulse, Unconditional, Needs Redstone) scoreboard objectives add nexus dummy Testing
(Chain, Unconditional, Always Active) scoreboard players set Blue nexus 75
(Chain, Unconditional, Always Active) scoreboard objectives setdisplay sidebar nexus
I've been messing around with the setup, and the setup commands work fine. This was just helping me to track if it was working.
Now, here are the main commands, again, with the same organization:
(Repeat, Conditional, Always Active) execute unless block 0 238 19 #end_stone run scoreboard players remove Blue nexus 1
NOTE – with the #end_stone part above, it doesn't make a difference in this case whether the "#" is there or not. Now, the command block chained to it:
(Chain, Unconditional, Always Active) setblock 0 238 19 minecraft:end_stone replace
When I was testing around with the setblock command, that wasn't the problem either. I traced it all the way back to the execute part of the repeating command block. The main problem: The execute part of the command will not give an output. It won't give an error message either. I have given all the commands, and it would be much appreciated if this could be fixed.
Linked issues
Comments 5
I was just testing the waters of upgrading my world to pre3 from 18w16a, which is the most previous, somewhat stable snapshot. MC 129725 seems to not be effecting my world in pre 3, even though it has never been marked as fixed, but my command/ function central computer was absolutely going haywire! (It's a high tech command based adventure map all controlled by a central computer room.
With some investigation I have stumbled upon this being the cause of the problem. Everywhere I use /execute if entity @a[then whatever here] to use as a /testfor is always testing positive. Guess I'll stick with 18w16a until the official release. This would be a huge setback for me if it makes it into the final release. Sure hope they fix this! Voted.
Suggested fix:
Add "ResultCount:" nbt for command blocks and have comparators pull output values from "ResultCount:" instead of {color:#59afe1}"SuccessCount:"{color}.
MukiTanuki, I'm looking to get a chain of command blocks working without needing to use a comparator, and this is still a glitch that must be fixed. But thanks anyways!
I was testing around with the commands some more, and I stumbled across something that kind of works. Here are the commands:
(Repeat, Unconditional, Always Active) execute unless score Blue nexus <= 0 nexus run execute unless block ~ ~1 ~2 #minecraft:stone_bricks run scoreboard players remove Blue nexus 1
(Chain, Unconditional, Always Active) setblock ~1 ~1 ~2 minecraft:stone_bricks replace
The strange thing is that the command block ignores the first score detection statement, and #minecraft:end_stone isn't in the auto-fill list. The second chain command treats the first command block as if it's a conditional, when it's not.
Relates to MC-131773.