So, right now, packets with errors in them get turned into line-breaks, which will typically be the wrong behavior (since we have to assume that errors are evenly distributed, and line-breaks make up a very small percentage of total information being sent). Perhaps it would be better to replace them with a special, non-displaying character that the end user can trigger off of, allowing them to handle those errors as they see fit.Vadi wrote:I think the packet issues get translated into linebreaks because Mudlet gives up and has to display whatever data it got in leiu of a proper GA or a linebreak, and it can't just display half a line and add more later.
Thanks so much for looking into this Jor'Mox!
Granted, the ideal solution would be to fix whatever is going on that is causing the errors in the first place, but that seems relatively hard as compared to something like what I'm proposing. And, my proposal would have the added advantage of being more or less invisible to the end user a significant amount of the time, especially since from the data in the replays, these packets are actually junk packets getting interpreted as real data, as opposed to replacing actual data coming from the server. He has multiple instances of the same data being displayed, with the junk bits in different places, and in every case, if you just cut those bits out, it would match the duplicates exactly.