Custom block events using both "set_block_property" and "set_block_at_pos" results in mixed behavior

Partner Rank:

3

Partner Team Reporting:

Pixel Squared

Verification builds and Platforms:

ver 1.16.100.56, build minecraft_uwp_dx11_x64_win10_4711101_release

Summary:

Custom block events using both "set_block_property" and "set_block_at_pos" results in the custom block being duplicated at the position defined in "set_block_at_pos" and the property of this newly placed block is altered instead.

Impact:

Unintended behavior that reduces the usefulness of new features.

Repro Steps:

1. Download the attached behavior and resource pack
2. Create a new world with said packs and experimental add-ons enabled.
3. Place a "pixelsq:button" block (/give @s pixelsq:button).
4. Right click on the block.

Observed Results:

Another "pixelsq:button" block is placed one block below the original block, additionally the new block turns green instead of the original block.

Expected Results:

A redstone block is placed one block below the original block and the original "pixelsq:button" block turns green.

Screenshots/Videos attached: Yes/No

No

Regression Builds:

None, this has never worked as intended

Notes:

If more than one event without using a "sequence" is unintended, it should disallow it entirely instead of producing unintuitive results.