It is not the correct way to write a book. And it does not work anyway because of the same issue. Please try something yourself before proposing as a resolution.
Please reopen the issue. Also, please explain why was it marked as invalid.
Still an issue in 1.5.1
Rather than in the future, can you do it asap? I'd rather play with low fps but transparent clouds..
The upper torch powers both upper and lower piston, so they turn off simultaniously, but it is obviously a bug that the golden block is left in place. Pistons cannot move extended pistons, so the upper piston is handled as if it has already retracted, but then it should have moved the block.
@xfallxcuav, yeah it's the same. normally powered pistons cause update on diagonally powered ones and due to some underlying processing order it results in such pattern.
Still present in 13w06a
What do you mean, Dinnerbone? Shift + Double click works almost as Shift + Click but for all of the items of a type. That means that you can process the first click as normal, but if the second click arrives shortly in the same spot, repeat the same action for the whole set of items. Not to mention that using Shift + Right click is also an option.
Indeed, still present in 13w05b. You have to wait for it for like 10 minutes, but it's there. Same with buttons, I beleive...
Bug is still present in 13w05b
Looks like redstone torches still receive random block updates.
In multiplayer, though, the issue probably lies in block update limit which can get part of your redstone updates postponed to the nex tick.
New easy method of recreating this bug - build a vertical half-slab wiring along X axis like in second screenshot, placing a torch next to that wiring from a certain side at a certain height is likely to produce this crash. If you are able to reload into the world you will observe invalid redstone signal travelling down, which is probably the real cause of the crash.
Nor can you place the new snow blocks on these, as of 13w05b
Tip for the reporter: Make a new report, include the last screenshot only and name the bug "Change of redstone signal strength applied to the input B of a comparator doesn't updtate the output". If I understand you correctly, that is.
Mustek please learn the game features, the comparator doesn't have to update itself, but the change of redstone signal is supposed to update comparator. On the other hand, it's the bug reporters fault in naming the bug incorrectly, but if you take pride in your position as a mod, you would have noticed that after checking the bug description and changed the name.
Chunk linking tool would be cool too. For instance, a special block: once chunk is loaded that block would ensure that one specific neigbor chunk is loaded as well. This would be useful for machinery that doesn't exactly need to be loaded all of the time, but is bigger than one chunk and needs to be loaded simultaniously in order to properly work.
Seriously? Mods, there are two bugs pointing to each other as duplicates.
GrygrFlzr: How do you know what that means? Please reopen.
Still present in 13w05a
Yes, it is.