Uploaded April 2012 | Updated November 2026, 3 hours ago
I've added a big screen to the setup. Now you can see what the turtle sees! Its actions are really quite sensible when you realize how little it can see. I could detect the block in front to gather slightly more information about other paths (to be precise, the block past a turn - the only thing it can see that's not part of the route), but it wouldn't help much. It would be really helpful if the turtle could detect blocks in other directions, maybe even blocks not directly adjacent.
You might notice that I set it astray at one point. -2 -2 is an unreachable spot just outside the maze. While it's attempting to get there it discovers the entire outer boundary, and then gives up.
Some people have asked me for the code. Actually I deleted it while cleaning up my saves folder. Sorry. :-(
I've added a big screen to the setup. Now you can see what the turtle sees! Its actions are really quite sensible when you realize how little it can see. I could detect the block in front to gather slightly more information about other paths (to be precise, the block past a turn - the only thing it can see that's not part of the route), but it wouldn't help much. It would be really helpful if the turtle could detect blocks in other directions, maybe even blocks not directly adjacent.
You might notice that I set it astray at one point. -2 -2 is an unreachable spot just outside the maze. While it's attempting to get there it discovers the entire outer boundary, and then gives up.
Some people have asked me for the code. Actually I deleted it while cleaning up my saves folder. Sorry. :-(

![Minecraft click position lagging behind [bug MC-67665]
Im uploading this to complement my bug report. https://bugs.mojang.com/browse/MC-67665
Here Im running five versions at once to allow for quick comparisons. All are locked to 60 fps without vsync. Im going through a routine in each:
* Look around horizontally and vertically and see how the selection box updates. 1.7.10 and both suggested fixes track perfectly. 16w38a is behind by a tick. 16w40a merely kills interpolation, so every 20th of a second it jumps to the crosshair and stays there even if the crosshair moves out of that box before the next tick.
* Do the same thing in third person, so you can see the head model and how the selection box is supposed to be obscured. The heads pitch always tracks the crosshair perfectly. In all versions but the one with my second suggested fix the heads yaw is behind, corresponding exactly to the selection box in 16w38a.
* Sprint-fly (unfortunately slow in 1.7.10) while looking in the same direction. In all versions but 16w40a the selection box is right underneath the crosshair. In 16w40a it jumps around and leads the crosshair at times. Thats an artifact of killing interpolation.
* Build a wall and place blocks on it after/during a quick diagonal movement. No matter how I try to time it, 1.7.10 and both of my suggested fixes wont budge. Most of the time it works. If my timing is off the block appears where my crosshair actually used to be, or doesnt appear if I clicked on air. 16w38a and 16w40a are identical: the block appears at the pitch of the current tick but the yaw of the previous tick.
My first suggested fix is like 1.7.10. My second suggested fix doesnt change getLook in case they want to keep current mob behavior (which seems to be an improvement, although I havent investigated it). The one side effect is that the head models yaw now also tracks instantly. In a third permutation you could copy Entitys getLook implementation to EntityPlayer, reverting EntityLivingBases version.
Im not sure how Grum doesnt see whats going on. Then again, this bug has existed for over two years before it got any attention at all. Minecraft click position lagging behind [bug MC-67665]](https://i.ytimg.com/vi/dxr1ypzRLkY/mqdefault.jpg)








