Julian Sivertsen

This is not a generic network issue, the client does not send any data to the server while downloading the world, if it takes longer than 30 seconds to download the world data the server will think the client timed out and close the connection.

I don't understand what this bug has to do with either of the linked bugs.  This isn't about using unsupported things like colors, or formatting with third party tools or commands or anything like that at all.  My no mods/no commands/pure survival vanilla written books become unreadable as the bottom text gets pushed down below the bottom of the page.  It still happens in 1.13.2, and this is not some kind of "unfixable" bug.  It's literally just an off by a pixel or so discrepancy between the word wrapping used for rendering text a book and quill and the word wrapping used for rendering text in a signed book.

Someone on a server I play on had this issue when connecting and did a packet capture of it.  From looking at it I've determined that the source of the issue is most likely due to poor connectivity and bandwidth between the server and the client.

The client does not send any data to the server while downloading the world, so if it takes longer than 30 seconds to download the world data the server will think the client timed out and close the connection.  I'm able to reliably reproduce this issue by using netem to simulate a connection with 400kbit bandwidth, 1% packet loss and 200ms latency.

See book-before.png and book-signed.png for a constructed example showing how text can be lost by this bug. The text is

----------------- ii- ------------------
----------------- ii- ------------------
----------------- ii- ------------------







Ooops, way to low now.

Thank you. Sorry for being a bit edgy, this bug almost made me lose several hours of game play on a server I manage, Good backup routines saved the day, though I'm going to be very careful about save-off in the future.

Thank you. Sorry for being a bit edgy, this bug almost made me lose several hours of game play on a server I manage, Good backup routines saved the day, though I'm going to be very careful about save-off in the future.

Wot, I posted this on another issue.

All changes made after that command is used are temporarily queued until the server is closed / stopped, like how RAM works.

Outstanding changes in RAM is either saved or asks me to save it when I shut down my computer. If I unplug my computer, those changes are lost. In Minecraft with save-off, outstanding changes are discarded when I shut down the server, it's also discarded when I kill it. Either your analogy is bad, or it's not working as intended according to you.

In the case of this being intended behaviour, it's still bad. It cause data loss, contradicts expected behaviour, isn't documented anywhere, and it leaves the world in an inconsistent state.

Your comments contradict each other. Which one is it?

The reason I think this is unintended behavior and therefor a bug is that this causes unexpected loss of data, and it's not documented anywhere. The Minecraft wiki entry for stop reads as follows.

Saves all changes to disk, then shuts down the server.

If this truly is intended behavior, then this goes against what I expect to happen, what the person who wrote that expect happens when /stop is issued, and how Sonic explains how /save-off works. In addition this behavior is severely bugged and causes the world to be left in an inconsistent state.

If you add a chest with a stack of diamonds in it between step 1 and step 2. Then in step 3, you take out the stack of diamond from the chest, you will observer in step 5 that you have two stacks of diamonds. Conversely, if you instead put in a stack of diamonds in step 3, then that is lost in step 5.

Can confirm that this is still an issue in Minecraft 1.8.1.