This is probably the strangest problem I've ever had with Mushclient.
I can only assume this has something to do with memory in Mushclient.
It usually starts occuring when my history buffer has reached around 5000 lines.
What happens is when the game sends me a large amount of data (viewing a mud script ~ 20+ lines), the output is different from what it really should be. I don't really know how to explain it too well. Mud script comes with line numbers, so I'll kinda show an example. The skewed output is usually in the last 5 lines of the script...
1) a
2) b
3) c
4) d
5) e
1) a
2) b
3) c
9) i
Here's why it isn't a problem with the game: The next line to come from the mud, no matter how long, fixes the output. If I select the output (ctr-a, or shift click drag)
then the output also fixes itself.
The obvious solution is to change my buffer to less than 5000 lines, but I was wondering if there is a better soltuion. I kinda like/need my buffer :>
Thanks,
Matt
I can only assume this has something to do with memory in Mushclient.
It usually starts occuring when my history buffer has reached around 5000 lines.
What happens is when the game sends me a large amount of data (viewing a mud script ~ 20+ lines), the output is different from what it really should be. I don't really know how to explain it too well. Mud script comes with line numbers, so I'll kinda show an example. The skewed output is usually in the last 5 lines of the script...
1) a
2) b
3) c
4) d
5) e
1) a
2) b
3) c
9) i
Here's why it isn't a problem with the game: The next line to come from the mud, no matter how long, fixes the output. If I select the output (ctr-a, or shift click drag)
then the output also fixes itself.
The obvious solution is to change my buffer to less than 5000 lines, but I was wondering if there is a better soltuion. I kinda like/need my buffer :>
Thanks,
Matt