Jørn Rønne Gaarde

It happens at the exact Original World Spawn coordinates. Use a compass - it always points to this exact location.

LOL 😃 Little off-topic for this issue, but to prevent wasting more time, consider building a nether transport system - much faster than using rails.

I believe it's common knowledge that just one block of water will nullify any fall damage?

Not using texture packs at all here, bug still happening. Bug isn't consistent, maybe one in five respawns/logins or so.

It happened to me several times, exactly the way Ben Carter describes it - "I’ve dropped to my death at the original spawn point. I then respawn at the last bed I slept in."

This is a fairly gamebreaking bug. Might I suggest you backport the fix from the 1.9 beta and release a 1.8 hotfix to patch this right away? Right now Minecraft is a game of Russian Roulette  😞

Yes, looks like a duplicate of https://bugs.mojang.com/projects/MCPE/issues/MCPE-38374

Having the same problem but on Windows 10 (server and client both). Client experiencing lots of disconnects. Usually ok to rejoin but sometimes client gets stuck at "Generating world, building terrain"

This is a confirmed 0.13 multiplayer bug. If you shift-click to put stuff in Furnace the game doesn't register, ie. Furnace doesn't burn and if you close items are lost. Until fixed, use click and move to use Furnace, not shift-click

The Compass in any version of Minecraft always points towards the World Spawn (where you initially spawned, and where new players will spawn too). Alas it's not a bug as such, but a design decision - although I agree it'd be more practical if it pointed towards the players individual spawn point (the bed where you last slept) :/

The first one is by design: If powered Redstone touches a Redstone Torch, it turns off. You use this feature to make inverters (called a NOT gate). Ie. an iron door is closed and opens if you step on pressure plate, using an inverter it will stay open and close when you step on the plate.

So that's it! I mostly play multiplayer too, (on Win10 client and Win10 server), and I've experienced many times being set on fire in the Nether walking on non-burning netherrack!

No problem 🙂 Thanks for listening - and happy bughunting 🙂

I upgraded Win10 to TH2 (10586.14) on both machines, then copied the new 0.13 world to the server.
When running on the local machine (the Win10 acting as server) there is no problem with the Furnace.
When running on the Win10 client the problem is still there.
Alas it seems this bug only affects Win10 clients, not single player.

And in single and multiplayer both?

It works for you in multiplayer? Hmm, I'll try starting a new world in multiplayer to see if this makes a difference :/

Hmm no, don't have the TH2 update. This is Win10 build 10240.
Did some testing.
Started a new world single player on 0.13. No Furnace problem here.
Started my old usual 0.12.1 world on single player. No Furnace problem here either❓
Started MCPE on my Win10 "server" with my usual old 0.12.1 world, then connected using my Win10 client - this is the way I usually play as my kids play on it too (using iPods). The bug is consistent in this setting, ie. when I right-click to put in Furnace it doesn't register (no smelting, items are lost if you close the Furnace) - and if I just click items and drag to Furnace it works fine.
Could this bug be related to multiplayer only?
I didn't have this problem before 0.13.

Maybe he wants realistic breeding animation? 😉

Until they fix it, don't use shift-click to put stuff in Furnace - use click to pick up, move pointer to Furnace and click to put in. This works every time

I get this bug too with 0.13.
Until they fix it, don't use shift-click to put stuff in Furnace - use click to pick up, move pointer to Furnace and click to put in. This works every time.

I can confirm this bug on Win10 0.13
Don't know why this is listed as a 0.12 issue, because the problem didn't exist before 0.13