Conditional command blocks SuccessCount doesn't update
Okay, this problem didn't surface in the previous snapshot because conditional command blocks were completely broken. Anyway, the issue is that the SuccessCount tags on conditional command blocks are simply not being updated. This causes the following issues: If you have a chain of conditional command blocks following a repeating command block (always active) done in this manner:
/testfor @a[r=3]
/say hello
/say hello
What happens is that the chat will spam with "hello" from both first and second conditional chain command blocks when a player is within 3 blocks of the repeating command block. When the player exceeds the 3 block range, the second conditional chain command block will continue to execute the command. This hence defeats the purpose of having a chain of conditional command blocks.
Created Issue:
Conditional Command Blocks SuccessCount doesn't update; This makes them pointless.
Okay, this problem didn't surface in the previous snapshot because conditional command blocks were completely broken. Anyway, the issue is that the "SuccessCount" tag on conditional command blocks are simply not being updated. This causes the following issues: If you have a chain of conditional command blocks following a repeating command block (always active) done in this manner:
Repeating command block: /testfor @a[r=3]
Conditional chain command block: /say hello
Conditional chain command block: /say hello
What happens is that the chat will spam with "hello" from both first and second conditional chain command blocks when a player is withing 3 blocks of the repeating command block. When the player exceeds the 3 block range, the second conditional chain command block will continue to execute the command. This hence defeats the purpose of having a chain of conditional command blocks.
ConditionalCommandBlocks SuccessCount doesn't update; This makes them pointless.Conditional command blocks SuccessCount doesn't update
Okay, this problem didn't surface in the previous snapshot because conditional command blocks were completely broken. Anyway, the issue is that the "SuccessCount" tag on conditional command blocks are simply not being updated. This causes the following issues: If you have a chain of conditional command blocks following a repeating command block (always active) done in this manner:
Repeating command block: /testfor @a[r=3]Conditional chain command block: /say hello
Conditional chain command block: /say hello
What happens is that the chat will spam with "hello" from both first and second conditional chain command blocks when a player is withing 3 blocks of the repeating command block. When the player exceeds the 3 block range, the second conditional chain command block will continue to execute the command. This hence defeats the purpose of having a chain of conditional command blocks.
Okay, this problem didn't surface in the previous snapshot because conditional command blocks were completely broken. Anyway, the issue is that the SuccessCount tag on conditional command blocks are simply not being updated. This causes the following issues: If you have a chain of conditional command blocks following a repeating command block (always active) done in this manner:
Repeating command block/testfor @a[r=3]Conditional chain command block/say helloConditional chain command block/say helloWhat happens is that the chat will spam with "hello" from both first and second conditional chain command blocks when a player is withing 3 blocks of the repeating command block. When the player exceeds the 3 block range, the second conditional chain command block will continue to execute the command. This hence defeats the purpose of having a chain of conditional command blocks.
Okay, this problem didn't surface in the previous snapshot because conditional command blocks were completely broken. Anyway, the issue is that the SuccessCount tags on conditional command blocks are simply not being updated. This causes the following issues: If you have a chain of conditional command blocks following a repeating command block (always active) done in this manner:
Repeating command block/testfor @a[r=3]Conditional chain command block/say helloConditional chain command block/say helloWhat happens is that the chat will spam with "hello" from both first and second conditional chain command blocks when a player is withing 3 blocks of the repeating command block. When the player exceeds the 3 block range, the second conditional chain command block will continue to execute the command. This hence defeats the purpose of having a chain of conditional command blocks.
Okay, this problem didn't surface in the previous snapshot because conditional command blocks were completely broken. Anyway, the issue is that the SuccessCount tags on conditional command blocks are simply not being updated. This causes the following issues: If you have a chain of conditional command blocks following a repeating command block (always active) done in this manner:
Repeating command block/testfor @a[r=3]Conditional chain command block/say helloConditional chain command block/say helloWhat happens is that the chat will spam with "hello" from both first and second conditional chain command blocks when a player is within
g3 blocks of the repeating command block. When the player exceeds the 3 block range, the second conditional chain command block will continue to execute the command. This hence defeats the purpose of having a chain of conditional command blocks.
relates to
is duplicated by
is duplicated by
This totally broke my map, I have to go back to 17w15a now. Wait, it's fixed in 17w16b
@SuperT no it's not fixed? conditional was completly broken, now in the current b snapshot they work again but having more conditionals in a row doesnt behave as it should
Can confirm also on 17w16b. Four command blocks, the first doesn't provide the required condition for the 2nd chain command block to trigger, which is fine, but the 3rd & 4th chained conditional command blocks trigger regardless, despite the previous output condition not being met.