chain_command_block issues
MC-90257A chain of command blocks may takes more than 1 tick to traverse
Fixed
MC-116372Chain command blocks set to "needs redstone" still executes without signal
Fixed
MC-116388Chain command blocks can clone themselves to create an infinite loop which freezes the server
Fixed
MC-116471Conditional command blocks SuccessCount doesn't update
Fixed
MC-118258Spelling mistakes in the 'Commandblock chain tried to execure more than x steps!' warning message
Fixed
MC-118269Warning message "Command block chain tried to execute more than x steps!" appears even if less / no chain command blocks should run
Confirmed
MC-124447Modifying maxCommandChainLength inside of function or command blocks does not affect currently running chain
Works As Intended
MC-134966Using /setblock to place an "Always Active" command block with a command won't execute the command immediately
Fixed
MC-219963Chain command blocks execute in same game tick, but a discrepancy is observed between two command chains that should act identically
Invalid
MCPE-163425Conditional chain command block on repeat command block with always active sometimes ignores the delay in ticks
Confirmed