If i type in this Command to give every ArmorStand(CAS) a score when they succesfully do a command it only saves it in the ArmorStand data that is the nearest to the command bock which is doing the execute command.
execute @e[name=CAS,type=ArmorStand] ~ ~ ~ stats entity @e[name=CAS,c=1] set SuccessCount @e[name=CAS,c=1] Successi want to to customcrafting and my commands are the following:
scoreboard players set @e[name=CAS] Success 0execute @e[name=CAS] ~ ~ ~ testforblock ~ ~ ~ minecraft:dropper -1 {Items:[{Slot:0b,id:"minecraft:sandstone",Count:1b}]}execute @e[name=CAS,type=ArmorStand] ~ ~ ~ stats entity @e[name=CAS,c=1] set SuccessCount @e[name=CAS,c=1] Successexecute @e[score_Success_min=1] ~ ~ ~ say Heyo1execute @e[name=CAS,score_Success_min=1] ~ ~ ~ blockdata ~ ~ ~ {Items:[{Slot:0b,id:"minecraft:air",Count:1b},{Slot:1b,id:"minecraft:air",Count:1b},{Slot:2b,id:"minecraft:air",Count:1b},{Slot:3b,id:"minecraft:air",Count:1b},{Slot:4b,id:"minecraft:air",Count:1b},{Slot:5b,id:"minecraft:air",Count:1b},{Slot:6b,id:"minecraft:air",Count:1b},{Slot:7b,id:"minecraft:air",Count:1b},{Slot:8b,id:"minecraft:air",Count:1b}]}it just says Heyo1 for testing reasons.
If you wanna see how the command blocks are built look at the photo.
thank you if you can help me!
Attachments
Comments 8
The problem is probably that you run another /stats command before the testing command:
execute @e[name=CAS,type=ArmorStand] ~ ~ ~ stats entity @e[name=CAS,c=1] set SuccessCount @e[name=CAS,c=1] SuccessThe /stats command does not seem to fail when saving an already existing stat on the same objective
This means that this command succeeds, which causes the following commands to run as if a sandstone block was in the dropper
Could you please add the numbers to the actual commands in the description then, because I don't quite get which command gets executed when.
Note: The way you are currently doing this seems pretty problematic as repeating command blocks do not act like chain command blocks. This means if you place a repeating command block facing down and below it another repeating command block, the lower one will still run first. Rather use a chain command block for that.
Also settings all the chain command blocks to conditional might causes problems as it could fail for one dropper and then eventually would also stop running the command for the other droppers. As you track the success state with the /stats command you would not need conditional command blocks there I think, but I might be wrong.
Please do not mark unreleased versions as affected.
You don't have access to them yet.
--- This action was performed automagically. If you believe this was done erroneously, please :light_bulb_on: raise an issue.