Compass points wrong direction after returning from nether
If you take a compass with you into the nether and back, it don't points anymore to the spawn point.
But always to following coordinates in the world:
x:8 y;?? z:8
It't reproducible in any gamemode.
The only solution I found is to close and reopen the savegame.
edit:
If you die (kill yourself) the compass is also fixed
edit2:
it's not such a big issue but still annoying.
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.
Linked Issues
is duplicated by27
MC-9532Nether Portal Complete World Change/DeleteDuplicateMC-15826Compass needle target changesDuplicateMC-17520compass break coming out of netherDuplicateMC-274222 bugs spawn point and weird earth cutaway DuplicateMC-32006biome bug; Re neatherDuplicateMC-36214Compass does not point to spawn point after leaving NetherDuplicateMC-40384Compass pointing to wrong spot after nether travelDuplicateMC-44155Compass North/Spawn PointDuplicateMC-54393Compass doesn't point at the spawn-point after been in the nether.DuplicateMC-68647setworldspawn is not saved permanently.DuplicateMC-75676True spawn and spawn chunks move after returning from the nether.DuplicateMC-77096Compass changes after trip through NetherDuplicateMC-78857Compass doesn't lead to spawn when traveled through NetherDuplicateMC-80213Compass changes where it points when returning from the nether.DuplicateMC-80435Spawnpoint changed after entering the NetherDuplicateMC-88667Spawnpoint getting moved when leaving nether.DuplicateMC-94636Spawn chunks not staying loaded?DuplicateMC-94640Centre of spawn chunks changing on compassDuplicateMC-95442Spawn chunks change after going through nether portalDuplicateMC-96537World Spawn Moves on Entering the NetherDuplicateMC-98881World spawn and Settings changes aloneDuplicateMC-103345Compass points to new location in 1.10DuplicateMC-106006Spawnchunks move after Nether visit.DuplicateMC-107019Compass not working properly after going to nether and back to overworldDuplicateMC-2478Compass direction is incorrect after returning from NetherDuplicateMC-4420Compass randomly points in different direction in the over-world. Sometimes it points to the spawn other times it points elsewhere DuplicateMC-5186Compas got broken.Duplicate
- Fixed
Jaden Wong![[Mojang] Jeb (Jens Bergensten)](../../../data/assets/gravatar/jeb.jpeg)
[Mojang] Jeb (Jens Bergensten)- 77
- 21
- Confirmed
- compass coordinates direction nether spawn
1.4.1 - 1.10.2
1.4.1 1.4.2 1.4.3 1.4.4 1.4.5 1.4.6 1.4.7 13w07a 13w09a 13w09c 13w10a 13w10b 1.5 13w11a 1.5.1 13w16a 1.5.2 13w17a 13w18b 13w18c 13w19a 13w21a 13w21b 13w24a 13w25c 1.6.1 1.6.2 1.6.4 13w38c 13w39b 13w41a 13w41b 13w42a 13w42b 13w43a 1.7 1.7.1 1.7.2 13w48a 13w48b 13w49a 1.7.3 1.7.4 14w02b 14w02c 14w03a 14w08a 1.7.9 14w25a 1.7.10 14w29b 14w30a 14w30b 14w32d 14w33c 14w34a 14w34b 14w34c 14w34d 1.8-pre1 1.8 1.8.1-pre3 1.8.1 1.8.2-pre4 1.8.3 15w31a 15w33b 15w33c 15w34a 15w41b 15w45a 1.8.9 15w51b 16w02a 16w06a 16w07a 16w07b 1.9-pre1 1.9-pre2 1.9-pre3 1.9 1.9.1-pre3 1.9.1 1.9.2 16w14a 1.9.3-pre3 1.9.4 16w20a 16w21a 16w21b 1.10-pre1 1.10-pre2 1.10 1.10.1 1.10.2- 16w32a
Created Issue:
Compass points wrong direction after returning from nether
If you take a compass with you into the nether and back, it points not anymore to the spawn point.
But always to following coordinates in the world:
x:8 y;?? z:8It't reproducible with any gamemode.
The only solution I found is to close and reopen the savegame.Environment
windows vista ultimate x32, 4gb ram
Linked Issues
is duplicated by1
TRASH-5638
Attachments2
is duplicated by
If you take a compass with you into the nether and back, it points not anymore to the spawn point.
But always to following coordinates in the world:
x:8 y;?? z:8It't reproducible with any gamemode.
The only solution I found is to close and reopen the savegame.If you take a compass with you into the nether and back, it points not anymore to the spawn point.
But always to following coordinates in the world:
x:8 y;?? z:8It't reproducible with any gamemode.
The only solution I found is to close and reopen the savegame.
edit:
If you die (kill yourself) the compass is also fixed
![[Mod] CubeTheThird](../../../data/assets/gravatar/cubethethird.jpeg){kind=small}
If you take a compass with you into the nether and back, it points not anymore to the spawn point.
But always to following coordinates in the world:
x:8 y;?? z:8It't reproducible with any gamemode.
The only solution I found is to close and reopen the savegame.
edit:
If you die (kill yourself) the compass is also fixededit2:
If you take a compass with you into the nether and back, it points not anymore to the spawn point.
But always to following coordinates in the world:
x:8 y;?? z:8It't reproducible with any gamemode.
The only solution I found is to close and reopen the savegame.
edit:
If you die (kill yourself) the compass is also fixededit2:
If you take a compass with you into the nether and back, it points not anymore to the spawn point.
But always to following coordinates in the world:
x:8 y;?? z:8It't reproducible with any gamemode.
The only solution I found is to close and reopen the savegame.
edit:
If you die (kill yourself) the compass is also fixededit2:
it's not such a big issue but still annoyig.
is duplicated by
is duplicated by
is duplicated by
If you take a compass with you into the nether and back, it points not anymore to the spawn point.
But always to following coordinates in the world:
x:8 y;?? z:8It't reproducible
withany gamemode.The only solution I found is to close and reopen the savegame.
edit:
If you die (kill yourself) the compass is also fixededit2:
it's not such a big issue but still annoyig.If you take a compass with you into the nether and back, it points not anymore to the spawn point.
But always to following coordinates in the world:
x:8 y;?? z:8It't reproducible in any gamemode.
The only solution I found is to close and reopen the savegame.
edit:
If you die (kill yourself) the compass is also fixededit2:
it's not such a big issue but still annoyig.
is duplicated by
is duplicated by
If you take a compass with you into the nether and back, it points not anymore to the spawn point.
But always to following coordinates in the world:
x:8 y;?? z:8It't reproducible in any gamemode.
The only solution I found is to close and reopen the savegame.
edit:
If you die (kill yourself) the compass is also fixededit2:
it's not such a big issue but still annoying.
is duplicated by
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
is duplicated by
is duplicated by
relates to
is duplicated by
is duplicated by
is duplicated by
is duplicated by
If you take a compass with you into the nether and back, it points
notanymore to the spawn point.
But always to following coordinates in the world:
x:8 y;?? z:8It't reproducible in any gamemode.
The only solution I found is to close and reopen the savegame.
edit:
If you die (kill yourself) the compass is also fixededit2:
it's not such a big issue but still annoying.If you take a compass with you into the nether and back, it don't points anymore to the spawn point.
But always to following coordinates in the world:
x:8 y;?? z:8It't reproducible in any gamemode.
The only solution I found is to close and reopen the savegame.
edit:
If you die (kill yourself) the compass is also fixededit2:
it's not such a big issue but still annoying.
Fixed in 30c.
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
relates to
is duplicated by
is duplicated by
If you take a compass with you into the nether and back, it don't points anymore to the spawn point.
But always to following coordinates in the world:
x:8 y;?? z:8It't reproducible in any gamemode.
The only solution I found is to close and reopen the savegame.
edit:
If you die (kill yourself) the compass is also fixededit2:
it's not such a big issue but still annoying.
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.
is duplicated by
is duplicated by
relates to
is duplicated by
[Mojang] Jeb (Jens Bergensten)![[Mod] Skylinerw](../../../data/assets/gravatar/skylinerw.png){kind=small}
is duplicated by
is duplicated by
Duplicate of MC-679, please use the search function to see if your bug has already been submitted. Currently over 57% of tickets are being closed as duplicate.
Duplicate of MC-679, please use the search function to see if your bug has already been submitted. Currently over 57% of tickets are being closed as duplicate.
Duplicate of MC-679 - If you have not, please use the search function in the future, to see if your bug has already been submitted. If you could not find the original report, please comment with the keywords you searched for.
Duplicate of MC-679 – If you have not, please use the search function in the future, to see if your bug has already been submitted.
This is due to MC-679
Dupe of MC-679
Duplicate of MC-679 - If you have not, please use the search function in the future, to see if your bug has already been submitted. If you could not find the original report, please comment with the keywords you searched for.
Dupe of MC-679
duplicate of MC-679
Please link to this comment in the description
The following is based on a decompiled version of Minecraft 1.9 using MCP 9.24 beta.
The reason for this is the same as for MC-679. When the player enters a different dimension a new WorldClient object is created an most of the data is copied from the previous WorldClient object. Whether or not the difficulty is locked is only send when the player joins a server (or loads a world). When he changes the dimension the method net.minecraft.client.network.NetHandlerPlayClient.handleRespawn(SPacketRespawn) does not set whether or not the difficulty is locked for the new WorldClient.
Does MC-679 describe your issue?
Ok, prepare for something... Could please a mod mark the versions for every bug I tell you here? That would be nice.
I have a world set up for fast bug testing. That means that going into each bug report and saying "Confirmed for 1.10.1" is way more work than actually testing it. So I want to confirm for 1.10.1 with this comment:
MC-4, MC-9, MC-14, MC-87, MC-112, MC-201, MC-212, MC-234, MC-258, MC-460, MC-577, MC-667, MC-679, MC-696, MC-697, MC-849, MC-868, MC-926, MC-957, MC-997, MC-1040, MC-1127, MC-1133, MC-1168, MC-1207, MC-1218, MC-1297, MC-1390, MC-1429, MC-1530, MC-1531, MC-1538, MC-1541, MC-1555, MC-1578, MC-1673, MC-1685, MC-1691, MC-1981 and MC-2023.
All of these are tested in 1.10.1. For some others I have additional information:
MC-711 not testable with my setup because of a crash that's new in 1.10.1.
MC-779: At least some appear outside, didn't test all. What's sure is that no general solution got introduced.
Confirmed MC-1511 for stone button, lever, torch, redstone dust, normal rail, end rod, tripwire hook, ladder and flower pot. Others are untested.
Confirmed MC-1874 for chest, brewing stand, enchanting table and flower pot. Others are untested. It's apparent that there isn't a general solution here either.
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:
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 [Mod] redstonehelper 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.2Douwe Keizer, 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.