Cloning a command block to an already powered command block now immediatly triggers that command block

Partner Rank: 1 (Critical)

Partner Team Reporting: Jigarbov Productions

Verification builds: 1.19.0.24 - 1.19.0.26

Summary:

Cloning a command block to an already powered command block now immediatly triggers that command block

Impact:

This new command block behavior was not versioned and will result in a multitude of broken content since it was not versioned. This will result in many broken maps, unhappy players that will stop buying stuff because they will think we all just sell broken garbage.

Repro Steps:

Place 2 command blocks

in command block a, put a clone command that copies command block b to a

put a say command in command block b

power command block a with a redstone block

 

Observed Results:

In this repro step, the command block a will run and then command block b will also run. the previous behavior was that the second command block would not trigger until being powered on its own. this will also run in a strange looping behavior where if a block in the chain clones an impulse command block onto the first spot, it will continuously trigger.

Expected Results:

I understand this may have been done as part of bug https://bugs.mojang.com/browse/MCPE-122188 but major command block changes should be versioned in order to maintain backward compatibility with the rest of the catalogue of content.

Screenshots/Videos attached: this results in the following in Papercraft 2 and other pieces of content. a repro world is attached

Regression Builds: 1.18.30

Note: Also since y'all care about parity more these days too, this behavior is not how it works in java edition. When you clone b onto a, it only triggers a and not b until you unpower and re-power the command block. which is how it has been in bedrock until this newest version