TransWikia.com

/locate command gives incorrect coordinates

Arqade Asked by TenNineAce on December 16, 2020

I recently tried a seed that should have had a woodland mansion close to spawn, but after looking for it for several hours, I gave up and used /locate. It gave me coordinates that fit what I saw in the seed showcase, but the mansion was most definitely not there.

I went into spectator mode and found a large mineshaft right below (which was also mentioned in the seed video; everything but the mansion lined up) but when I tried /locate Mineshaft I got coordinates extremely far away.

I have used locate successfully in other worlds without re-launching minecraft, and I was definitely in 1.11 every time I loaded this world. Other than this oddity the world doesn’t seem corrupt or anything.

Am I somehow using /locate wrong? Or is this a problem with /locate/my world/both? Is it relevant that I was on peaceful difficulty?

One Answer

From what I've seen in the other answers here, it seems to have been a one-off thing. Since you say you generated the world in 1.11, I will assume that version is not the issue. It could well be a world generation bug, as arise from time to time. Try perfectly replicating the conditions for the world creation and when you tried using /locate. If it happens again, post the exact circumstances here. Also report the issue here. If it doesn't repeat, then forget about it. It may be fixed later.

Answered by DeadpanDudeiii33334i4i4i4i4i4i on December 16, 2020

Add your own answers!

Ask a Question

Get help from others!

© 2024 TransWikia.com. All rights reserved. Sites we Love: PCI Database, UKBizDB, Menu Kuliner, Sharing RPP