mojira.dev

Sebastian Schmidt

Assigned

No issues.

Reported

Comments

They could just bring out an update for 1.6.2 to save the structures, or ship the old generation algorithm with 1.7 and "convert" the chunks to add the data on first load with the new version.

Well, this is not MC-2416. This can be fixed by letting the player chose if he wants to continue searching for spawnpoints or if he wants to keep the "bad" spawn.

MC-2416 can be fixed by adjusting the height of the spawn point.

Fixed in 13w01b.
The image is probably from 13w01a.

@Ruben van Baarle:
No, it's consistent now, it just behaves like repeaters: http://i.imgur.com/yDs1h.png

I can confirm this bug. It causes a stack overflow. I get the same loop between those for methods.

@Jonathan Haas: That's what I'm thinking now. But it's just a snapshot, so ... 😃

Thank you! Now I got it 🙂

Ah, I exchanged B and A. So it's like an analogue inverter. It would be nice if you didn't need a repeater and could use different values for B.

So the toggling is useless and only the block type of the input changes the function?

@Robin: Yes, I can confirm that.

Having to use a pickaxe to get it is no bug, I guess. You should be able to place it like a half slab, so it can float if you place it on the top half of a block.