Cody

I agree with @@unknown ...that encasing villagers for now is a good workaround.

When villagers are in their beds, encase them in glass. Here's what I did.

B = Bed (takes up 2 blocks)      F = Fence      S = Slab      FS = a fence post, with a slab on it               G = Glass

B FS FS B FS FS

B FS FS B FS FS
G            G

1. Put a bed down. Let the villager sleep.
2. On the side's of the bed, put down two fence posts, with slabs on top of them.
3. Put glass, all the way to the ceiling on the front of the bed.

You can break the middle glass in the front to interact with them if you need to.

The fence posts + slabs stacked on top prevent anything from bumping into the villagers. It's like a protective bubble. The cats are the worst offenders for moving villagers I think.

EDIT: I was actually incorrect! Here's how I know villagers won't burn in lava if they are pushed due to this bug.

1. I dug a hole 2 wide, and 4 blocks long in the ground.

2. Created a lava moat around the hole, 4 blocks down.

3. Placed a bed at the bottom of the 4x2, with a villager.

4. Wait for the villager to sleep at night. Then I jumped down and bumped it.

5. Villager got pushed through the lava.

6. Wait until morning, the villager doesn't come back.

7. Break the bed you first put down.

8. Put down another bed.

9. You will see green sparkles for the villager re-binding. Even though you can't see it. (It was the only villager I spawned)

10. Save and Quit Game, reload the game, and the village is there, and alive.

11. Villagers wont burn in lava. (or so it seems)

[Original Post]

I have had some concerns about my villagers becoming burned by lava nearby. I have a village surrounded by a moat of lava.

Since this update, a few villagers have caught on fire. My librarian disappeared after being trapped in his house. I think he might of caught on fire and died.

Does anyone know if villagers bumping into lava will kill them? I need to go into creative mode later and check.

I am not 100% sure why they were on fire, but it's a good guess.

Hello Cody again, i have recently found out a way to get your world back if it has been corrupted by this bug.

What i did was press the edit button on the new corrupted world that was 0.01mb and then it told me it couldn’t sync the world, however i clicked on the edit button again and it let me edit the world. It said the seed was -1 which it definitely wasn’t before. I then made a copy of the world and it not only made a copy of my original world but it also brought back the world itself!

I’ve been playing on the world for a few days now and the bug hasn’t re-occurred. If you have been affected by this bug then I heavily recommend trying the steps above if you want to get your world back!

Just experienced this bug today, as far as I’m aware this bug has existed for over a year and nothing has been done to prevent it. Mine and my friends world was deleted from my worlds list and a much smaller world named dQyGXWGICwA= which was 0.01mb had replaced it, which is very different from the 500mb world that it was originally. This new world was also dated 01/01/70, and whenever I try to open it my game crashes.

However a copy of the world that was over 100mb did survive which is unlike others who have experienced this bug, but that backup world is to outdated for me and my friends to even want to play on, as so much progress would have been lost. We would rather start another new fresh world however we fear the bug may happen to that world too.

I just feel like me, my friends and MANY others have been scammed of their time, especially me and my friends who put months into that world only to have it corrupt to a bug that is OVER A YEAR OLD. Incredibly discouraged to play the game I love due to a game breaking bug that seems to be ignored by Minecraft’s development team despite this bug affecting many for over a year now.

Confirmed for MC 1.14.2 Pre-release 1

This bug still exists in 1.14.2 Pre-release 1

This problem is started from 1.14 snapshot

i saw this issue in only some of the 1.13 snapshots

I dont know why but its crashing the server every single time

but its not crashing the game all the times...

Same here, I know it's still in BETA so I know there will be bugs, but please fix the invisible intities before full release. Seeing just a chest top or a drowned head is kind of annoying.

Still not fixed, I had a max render distance of 22 myself and now it only maxes at 6. I'm on beta 1.2.5.0 And I'm running on Android 6.0.1. It's been 4 weeks and keep getting a email it's resolved but it isn't. FIX IT! It is really frustrating when youre trying to be nice and all you get is automatic crap.

Still present in 15w31c.

This bug is only half-fixed; the survival bug shown here still exists in 14w32d (it still takes the whole stack instead of just one item from the stack).

I'm experiencing this, too. It seems to be caused by armor stands. As soon as I place one down, it kicks me; every attempt to login after that also immediately kicks me.

I don't see how this could be intended. Since the armor stand is basically a larger item frame, you'd expect them to act the same, but they don't.

Comparisons between item frames and armor stands in 14w32b:

• Creative: http://gfycat.com/BothShowyIzuthrush

• Survival: http://gfycat.com/SlimyYellowishAntarcticgiantpetrel

When you supply a time, it checks if it is between 1 and 1,000,000. If it is, it is then multiplied by 20 to, I assume, convert it from seconds to ticks. The thing is that the "clear" argument doesn't accept the time you supply. When you do "/weather clear 1000000" it does 4 things:

1: set rainTime to 0
2: set thunderTime to 0
3: set raining to false
4: set thundering to false

Basically, it acts the same as "/toggledownfall" because it doesn't start a timer that has to end before the game tries to change the weather again.

For a bit more information, here are the other two weather options:

"rain"

1: set rainTime to user-supplied time
2: set raining to true
3: set thundering to false

"thunder"

1: set rainTime to user-supplied time
2: set thunderTime to user-supplied time
3: set raining to true
4: set thundering to true

I went looking, and when I searched things like, Pausing, Time, ect., I could only find a thing with minecraft PE. I looked down in recent issues, but did not find any like this, so I made this.

It does say "required" in the error message, so one would think that the tags you supply must be there and not that the block should only have those tags. Besides, what about checking for certain items in a chest with 27 individual slots to test for? That seems like an awful lot of text to see if a chest has a named diamond sword in a specific slot.

I found this Bug Aswell I had a Helmet with Auqa Affinity on then i saw the White then i took it off and i saw the white again

Ok. Sorry for my mistake there, first time sending a report, haha.

This is not a bug, this is a feature that has been in since way back, at least beta 1.4. Obsidian is not hard to get any more.