Compass points wrong direction after returning from nether

I can confirm this issue. It has happened to me. I almost lost my house because it pointed to a random location. Not only that but a new portal was created when I came back to the overworld, so I was in a totally different place. I didn't create a new portal somewhere else in the Nether yet I still ended up in the wrong place.

Can confirm.

Affects also version 1.4.5

I believe this can happen even without going to the nether. Sometimes the compass just doesn't work, but then later fixes itself when you die. I haven't been able to pin it down. It's hard to catch because it takes a while after starting a new world to get redstone to make a compass, so won't notice a world is broken right away, but I believe it has something to do with the spawn protection that keeps you from spawning in water. I'm not sure. It's been happening to me a lot and I'm pretty sure I don't even have to go to the nether for it to break and/or fix itself. Very weird. Annoying too since when it breaks often the compass is pointing far away from where you spawned and made a house etc., making the compass far less useful in that world.

Still exists in Snapshot 13w09a.
It's very annoying, because you can't leave the nether through a new portal.

Please do not mark as affecting future versions, as you could not have tested those.

I still get this in 1.5.1 though it happens not just when returning from the nether

Confirmed in 13w16

I noticed that it is irrelevant for the bug whether you carry a compass with you while traveling to the nether, or whether you obtain it later.

Still present in 13w17a.

I'm surprised this bug has been left around for so long; it seems to rarely pose a real problem, but when it does it might hit you hard.

still present in 13w18c

That's the middle of the 0,0 chunk. A default or fallback value that is becoming active unintentionally?

Still present in 1.7.2.

Thanks folks!

It's a HUGE issue for me, I'm almost always traveling. It literally points the opposite direction of my spawn (not bed spawn)

Still present in 1.7.4. Got back from nether and went on a trip....

F3 tells you the direction, so I never really use compases. I do use them to create maps, and it doesn't bother me.

Some people consider it cheating to press F3. (In survival anyway)

Do we break the record for the oldes bug never be resolved?
Seriously 1.3 years!
I just wish mojang does a overhaul to the compass and clock tools (add more functions and more tools) when they fix it.

Yeah, it would be nice to have this one resolved. Usually what I have to do is make a trail of breadcrumbs from my original spawn point to whereever the compass points to after coming back from the nether, but that's kinda annoying.

I would like to see the ability to craft an altimeter as well.

Sorry Jaden, the oldest open bug is MC-4. The dev team is overhauling lots of things, so be patient, as fixes will come.

Thx a lot for your work here. Don't hurry, I can wait. 😃

I have same situation so just do not go to nether with compass

Confirmed it occurs in 1.8. I just built a rail to the wrong spot >.>

Confirmed in 1.8.1 on a private server. I manually set the spawn point back to where it was supposed to be a few times, and thought I was losing my mind because the compass kept pointing back to 8/x/8 – until I found this bug report.

There is still hope for the 1.9 😛

Any news on this for 1.9?

Might be related to MC-46345.

happens on my 15w51b snapshot server

Confirmed for 1.8.9 and 15w51b.

When you travel to a different dimension the client receives a S07PacketRespawn packet (MCP 1.8 names). Because the client does not store all servers for the different dimensions it creates a new WorldClient and copies most of the data from the dimension before, for example if it was hardcore etc. or information contained in the respawn packet. The spawnpoint is however defaulted to the initial spawnpoint which is (8|64|8) because it is neiter contained in the respawn packet nor is it copied to the new WorldClient from the old one.

These might be some possible ways to solve it, that come in my mind right now:

• Adding the spawnpoint in the respawn packet. This information would be unnecessary when the player dies in the overworld, this however already happens for the difficulty, the world type and the game mode.

• Sending a S05PacketSpawnPosition from the server when the player changes the dimension and when the player dies in a different dimension. This creates the same bug described in this report when there is latency and the player does not receive this packet.

Confirmed for 16w02a.

Could you please include the comment from above?

@Marcono1234; ticket-autor here. Do you mean the affected snapshot version? or the comment about the S05PacketSpawnPosition?

I meant the comment about the packets, I probably could have said this more explicit 🙂
However @unknown did this already

Thank you anyways

Affects 16w07a.

Affects 16w07b.

Confirmed for 1.9-pre1

Still Affects 1.9.1-pre3.

Confirmed for 1.9.2

Confirmed for 1.9.3-pre3.

Affects 1.9.4.

Affects 16w20a.

Confirmed for 16w21a.

Confirmed for 16w21b.

Confirmed for 1.10-pre2.

Confirmed for 1.10.

The compass turns 360* if you cross the z=8 line at higher x values than 8 (when it points at 8 8).

When I teleport to 8.0 ~ 8.0, the compass turns when I execute
/tp ~-.0000000000000008881784197 ~ ~
Any lower value doesn't turn the compass no matter how often I execute it.
Is that of any value for the report?

Confirmed for 1.10.1.

Confirmed for 1.10.2.

Confirmed for 1.10.2

@unknown, see the comment above yours

Confirmed fixed for 16w32b (probably 16w32a as well)

This Bug is in the Bedrock Version in Build 1.2.0.20

Then please create a report for it there.