Take the 2-minute tour ×
Arqade is a question and answer site for passionate videogamers on all platforms. It's 100% free, no registration required.

I was trying to build an automatic cobblestone generator using pistons, and while I think the machine should work, it instead causes the Universe to implode game to crash.

The stone is created from water and lava mixing next to a "top" piston, this then uses a repeater to transfer power through the stone when it created and activate the piston - pushing it directly downwards. A few levels down is the "output" piston, which uses the same trick detect when a block has been pushed down in front of it, and will then push it sidewards out of the machine.

The top piston has an override "off" switch in it's loop, which works as a start/stop override for the whole machine.

When I switch the machine on Minecraft crashes - I can just hear a piston going and then "Saving Chunks" and darkness...

Luckily, it seemingly crashes in a recoverable way, my world is still playable after a restart, but with a few "phantom" blocks clogging up the machinery...

So, what's going on and how do I fix it?

Oh, and I'm running version 1.9pre3 with no modifications.


Images of the machine:

Top Piston Construction:

enter image description here

Bottom Piston Construction:

enter image description here

"Phantom" Blocks:

enter image description here

share|improve this question
1  
+1 just for the sheer ingenuity of your design. –  John the Green Oct 22 '11 at 22:20
    
It's probably just a bug in the pre-release. I'll do some testing in 1.8 later to see if it also happens here. I have no idea why it would be happening though, someone would probably have to check the code or something. –  Mr Smooth Oct 22 '11 at 22:23
    
Nice use of "smart pistons"! I'm not sure why you're crashing and why there are phantom blocks, but I have a feeling @MrSmooth is correct in that it's a 1.9-related bug. –  Kevin Y Oct 22 '11 at 22:26

2 Answers 2

up vote 2 down vote accepted

Turns out I had a wiring error that was causing the bottom piston to be triggered immediately when an incoming block arrived, instead of being delayed by the repeater.

This is because the repeater next to the piston was on top of a block and this block was short circuiting and delivering power directly in to the piston itself, instead of it flowing through the repeater and along the wire around the back of the piston.

I can only assume the machine was trying to push one block in two directions at once (or something similar) and this was causing the game to crash (this, arguably is a bug, the machine should just jam up or something). Not sure about the phantom blocks though, presumably they're an artefact of how the game tracks blocks being pushed.

The solution then, was to remove that block and place the repeater on ground level - correctly delaying the current.

enter image description here

share|improve this answer
    
This is odd. My testing didn't have any repeaters to slow down the current at all, it was instant like you say was the problem, but mine worked perfectly. –  Mr Smooth Oct 24 '11 at 8:38
    
shrug Could just be a 1.9r3 bug, could be we've built them just a slight bit differently and mine has a issue because of it, could be Minecraft just hates me... who knows... it works (for now) so I'm not going to touch it again for a bit :/ –  DMA57361 Oct 24 '11 at 8:52

This is a bug in the 1.9 pre-release (not sure if just pre-release 3, or all of them).

As you can see here:

enter image description here

It's working as you intended it to in 1.8.1

share|improve this answer
    
Thanks for testing, and +1 for effort, there could well be a bug, but I've found a wiring error/work around that I can fix to make the machine work as expected. –  DMA57361 Oct 23 '11 at 8:29

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.