[Bug] CC:Tweaked does not seem to be able to get bundled cable input colors from MoreRed correctly

[robedpixel]

While using CC: Tweaked version 1.114.2 for minecraft version 1.20.1, computer blocks are unable to get which colored wires are powered in a bundled cable using the getBundledInput or testBundledInput functions

Any calls to getBundledInput with the correct side returns 0, even if any colored wire in the bundled cable is powered

Interestingly though, setting redstone output using setBundledOutput works as expected, only getting input fails

[mthedoodler]

I'm experiencing the same issue in ATM10, which is on Minecraft 1.21.1

More Red is 6.0.0.3

CC:Tweaked is 1.116.1

[RobertLSnead]

Same issue in FTB StoneBlock 4

observations:
(fail) picking up and placing down the computer does detect current changes, but fails to detect any further updates...
(fail) also power cycling the computer works also, but not ideal...
(fail) starting and stopping scripts also seems to work...
(fail) breaking the bundle cable and replacing the cable works, tested with running script...
(success) redstone updates on the connected bundle works, redstone clock under bundle next to computer...

Work around:
if you put a redstone pulse/clock under the bundle that connects to the side of the computer, this will cause/force an update and will register the input to work every time

[RobertLSnead]

here is the script used for testing...

monitor = peripheral.wrap("top")

local function to_screen(text)
    monitor.clear()
    monitor.setCursorPos(1,1)
    monitor.write(text)
end

local function get_bundle(side)
    return rs.getBundledInput(side)
end

while true do
    to_screen(get_bundle("left"))
        
    os.sleep(1)    
end

[SquidDev]

I believe this is because bundled cable output changes do not trigger block updates on 1.20.1/1.21.1 (I assume this is fixed on 1.21.10 with exmachina, I confess I have not looked at that yet?). This used to work fine, because CC:T also used to update redstone on onNeighborChange (which is triggered when setChanged() is called). This was removed in cc-tweaked/CC-Tweaked@676fb5f, as I believed it was redundant. I have partially reverted this change in cc-tweaked/CC-Tweaked@419d823, which should fix this.