Muriako

Definitely not fixed as of 1.8-pre3.

I am experimenting with moving boats via water streams (EATS road) and have noticed a few things about this issue. Note that a lot of this may vary a bit in normal boating as these tests were all when dealing with moving water streams and not still water blocks.

• The desyncing only seems to happen when a player interacts with the boat

• It does not seem to happen if there is no player in the boat, but if a player jumps into a boat that has been moving in water streams it will desync immediately and severely, even if the player is only in the boat for a split second.

• The desyncing itself does not seem to be related to loading/unloading chunks, though the additional lag may contribute to it

  • It can happen even when the boat never leaves a small area and no chunks are being loaded/unloaded

  • If there is no player in the boat and the chunks are reloaded (Fully reloaded, A + F3 will not work) the boat will go back to its real position and move as expected. There is one situation in which this is not the case and that is if the boat loads in a water stream that is pushing it to a block which it cannot pass, in which case it will start ghosting past the block and snapping back to its original position

  • If there is a player in the boat when the chunks are reloaded (relogging) the boat will start where it is supposed to and then desync immediately and very noticeably

The coordinates for both the player and the boat are technically done correctly somewhere down the line, they just seem to be thrown off on the way to being drawn. This is definitely one of my top hopes for something to be fixed in 1.8, particularly with the new things being added to make traveling around water more worth while and because I would really like to be able to use my EATS road without this happening.