Mark Poole
Assigned
Reported
Comments
I noticed in pre10 that new worlds were ok, /locate had no lag and returned accurate coords as in structures were actually there. Old worlds, those I created in earlier 1.13 snapshots, had no lag anymore but /locate returned coords where structures were not there. 1.13 also seems ok thus far in my limited testing with a new world.
Still present in 18w11a, /locate to a Mansion returns 'Could not find that structure nearby' and badly lags the client for several seconds. It's also consistent with EndCity and consistent through a dozen single player survival worlds I've created and tested on.
Noticed the same in recent 1.13 snaps. This is also true for End Cities, /locate says 'Could not find that structure nearby' and Minecraft then lags badly for a few seconds before it returns to normal. Seems to work for some structures but consistently not for 'Mansion' and 'EndCity' at least.
No, 1.12.2 was fine. I didn't try to bring a 1.12.2 generated world into 1.13 snapshots or even 1.13. I was merely trying to point out that the issue, at least for me, looks to be resolved. Thanks!