Flip
- b-flip
- b-flip
- Europe/Stockholm
- Yes
- No
MC-6438
Screenshots posted in a zip file, it's uploaded as an attachment in the ticket. Best Regards,Flip
Date: Mon, 7 Jan 2013 06:32:12 -0600
From: jira@mojang.atlassian.net
To: flip_van_hagen@hotmail.com
Subject: [JIRA] (MC-6438) Sand falling too early in 13w01b[Mod] CubeTheThird
updatedMC-6438Sand falling too early in 13w01b
Can you post a screenshot of this setup?
Change By:
[Mod] CubeTheThird
(07/Jan/13 1:31 PM)CHK:
07/Jan/13 7:30 AM
Status:
Open
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Sand falling too early in 13w01bSand falling too early in 13w11a
3 pictures of the sand stacker mechanics. The pictures are labeled part 1 to part 3. If you'd want an even shorter signal (shorten the on period, making the off period longer) add another pulser before part 3 and adjust timing accordingly. I've tried extremely tight timings using several pulsers and still the blocks will break.
For more information: http://www.youtube.com/watch?v=U2BFqmS9kr4
This is the same construction, but with a different timed pulse and without the signal shorteners that I've included in the multiplayer screenshots in the attached zipfile.
Since 13w01b this is not possible anymore. Blocks will break instead of stack.
Still the same in the newest snapshot (13w07a). Would really like to have this fixed. We have many bridges and secret entrances that were made using this concept and they're not working anymore and there's no other way I know of to get the same functionality.
Problem is still existing in snapshot 13w11a.
@Torabi, that's a very black and white view you've got there. Actually Christopher Martin is right about something. It's been reported over 1 year already, and the status is still: Community consensus. To my understanding this means nobody from Mojang has tried to recreate this issue since it's been reported. I've updated it several times and have to say the lack of response and action is noticeable. I did read every comment posted on this issue, as a lot of the world we built was based on these mechanics. From one day to the other, all of it was broken without a working alternative. This actually made me stop playing minecraft for quite a while. It's nice that they're adding stuff like pufferfish and pretty flowers, but it seems game mechanics usually aren't on the priority list.
I've started playing again since last weekend after over half a year break, started out in a new world and will build the sand stacker again as soon as I have the redstone to do it (I don't have spawn rights in our multiplayer world) and will update this post with the results.
Thanks for the explanation.
The video's are designs that push sand up but not retract. It did however help me to find this video in which the 2nd design shown is promising and is what I'm looking for including the clock, but I have to find out if it still works in the current version in multiplayer/survival, it is a bit different from what I did before:
https://www.youtube.com/watch?v=62o3FzBpneY
Its purpose and use could be the same as the design I posted, and I think it seems no problem to chainlink it into rows and so can be used for a variety of functions like retractable bridges and stairs like I did have before.. I'll try it and post it here if it worked. Thanks!
Ok guys, it took some tweaking but I've got it to work. Attached is a zip file with screenshots and a text file with a full explanation on what you need, how to lay it out and the repeater clock timer settings. Using this it's suitable to make a retractable sand elevator, but it's also possible to extend it to the back and use it for functions like retractable sand bridges and stairs, etc.
I would like to thank everybody for their contributions and I'd say I'm happy with this working solution in the current minectaft version (multiplayer/survival). Best Regards, FliP
Hi Christopher. I do understand it's not only there for this purpose, but a lot of applications could be replaced by the mechanism provided, timing however is essential. Please try to recreate what I did (file with instructions is attached) and see how that could replace your original workflow for the applications used, I was very surprised to see it work as well as it did after I adjusted the mechanics and timing and because of the mechanism it doesn't need a stop-piston either to keep the piston from moving. The biggest difference is that instead of blocks being pushed, they're being pulled. I understand the original problem is not fixed, but if there's a working workaround I'll gladly adjust my mechanics and use it.