Abnormal behavior of redstone above an IC block
LadyCailinBot opened this issue ยท 13 comments
CRAFTBOOK-2437 - Reported by pmpmpm
Hi,
A picture will speak perfectly:
http://s7.postimage.org/u3rkssom3/2013_02_22_23_46_15.png
As you can see, the lever is down, but the redstone doesn't light up. Of course, if the level is pulled manually and not by the IC, the redstone is lit.
Same with any IC, as far as I can tell.
Thanks for reading.
Comment by me4502
The issue with this is, if its set up to work, the ic block will randomly change data values..
Comment by me4502
Because to update a block, the ID or data has to be changed. (With bukkit)
Comment by AlexMedia
I'd like to +1 on this matter.
I have made this test setup: http://xkcd.nl/eLW/s-318025e5e40c - one vanilla MC, one with a ST Wireless Receiver, and a ST Wireless Receiver with a redstone lamp underneath it. When I flip the levers, these are the results: http://xkcd.nl/eNX/s-352a2798faf3
Apparently, adding a redstone lamp causes a block update which in turn causes the piston underneath the receiver block to extend. What's puzzling (to me, as an end user) is that this setup used to work flawlessly in the past, that is, until the server admins upgraded to a more recent server version (together with an upgrade to MC 1.4.7).
Comment by pmpmpm
Since the IC does not change any data around, and does not make an update on blocks, it seems logical.
Err, what would be the wrong thing if the IC would cause the blocks around to update or what? Sorry, I'm no modder, I don't know the internal system of Bukkit...
Comment by me4502
The issue is, bukkit has no way of updating a block without modifying its type/data.
Comment by AlexMedia
But it used to work in the past... Has CraftBook changed? Has Bukkit changed?
Comment by me4502
Craftbook used to randomly change the data of the block the IC sign is on, which caused a block update. But it also caused issues for wool, stone bricks, half slabs, stairs, sandstone, etc.
Comment by AlexMedia
Aha, I did not know that. I can understand that that is an undesirable side effect.
Comment by me4502
Actually, it turns out bukkit did change. Stopping it from pulsing data didn't break it.
Comment by me4502
As an update, a PR to fix the bug has been submitted to bukkit by a person.