Minecraft Forums

I don't know if any one else is having this problem but one Xbox one and 360 Redstone just doesn't work as it should. sticky pistons push blocks away instead of pulling them to them, and double pistons extenders don't work. sometimes the pistons don't even work. droppers also have problem to give stuff to chest and other droppers. I have turned my Xbox back one and off again but if I do so it might only work for 5 minutes before it stops working again. is this just tu19 problems or something else?

and yes I made a mistake in the heading

Yes I am experiencing the same problems. Especially with the problem where pistons do not extend. I am sure it is just a bug in the update that will be patched with time.

FYI, my sticky pistons work fine and have no problem pulling blocks back. Are you trying to pull back a block of redstone? (It won't.)
I haven't messed with 'double piston extenders'- I don't create anything so complicated that I need them.
It's possible that- for consoles- that's the way they're suppose to work.... OR as Grant said, hang on for a patch.

I've made some daylight sensor lamps that need to pull back a redstone block and it worked fine. A lot of other redstone stuff seems....off.

I can't get pistons to work with redstone torches at all (sticky or regular pistons). Really frustrating for any automatic farms

Well I hope they can fix this soon because with all this new redstone staff I can make thing with, I want to start making some good staff. Thanks everyone for your help
Well I hope they can fix this soon because with all this new redstone staff I can make thing with, I want to start making some good staff. Thanks everyone for your help

i have some solution for the piston not working, sometimes you need to restart your xbox system,the game lag and probablly causing the piston to not working properly,building a auto cocoa farm with the pistons is not really gonna work piston here is really anoying bug,other solution is to wait for the next update on pistons bug fix.

Hey Arnold, you've commented here in an old thread, about a problem that was resolved a long time ago now. As the OP said, this was an issue back in TU19, and we should now be running TU48, so whatever is causing your redstone problem now is unlikely to be the same problem raised by this thread. Hope that helps.