Custom Blocks: redstone_conductivity component does not update on block state change

What Happens

The “redstone_conductivity” block component is not properly applied to the block or surrounding blocks when a block state changes.

What I expect to Happen

The block should be re-evaluated if receiving a redstone signal, and adjacent blocks should be re-evaluated for propagation of said signal.

Example

In the series of images attached:

1. A block is shown to not conduct a redstone signal as a bottom slab (positions 1 and 3) or a top slab (position 2). Position 4 is a double slab placed through world interaction. Position 5 is a double slab placed by command to ensure it is instantly placed with the double-slab property that should facilitate conductivity.

2. After “reload all”, the redstone_conductivity component for position 4 is re-evaluated and accurate, matching the expectation set by position 5.

3. Interacting with position 3 to create a double slab shows the issue is still present. You can expect that the signal would be properly updated, but only after reloading.

A simple addon is included to show the scripting method I used to modify block states.