When the server sends very long output, MUSHclient halts display of the current output part-way through until the next new message arrives from the server. This makes it look like MUSHclient is broken (I mean, it kind of does mean that).
This is the shortened packet debug for displaying the output from one command on Aardwolf ("board ideas" then "note list"):
Incoming packet: 1296 (9639 bytes) at Wednesday, January 06, 2021, 11:37:10 AM
Incoming packet: 1297 (10000 bytes) at Wednesday, January 06, 2021, 11:37:10 AM
Incoming packet: 1297 (10000 bytes) at Wednesday, January 06, 2021, 11:37:11 AM
Incoming packet: 1297 (10000 bytes) at Wednesday, January 06, 2021, 11:37:12 AM
Incoming packet: 1297 (10000 bytes) at Wednesday, January 06, 2021, 11:37:13 AM
Incoming packet: 1297 (10000 bytes) at Wednesday, January 06, 2021, 11:37:14 AM
Incoming packet: 1297 (10000 bytes) at Wednesday, January 06, 2021, 11:37:15 AM
Incoming packet: 1297 (10000 bytes) at Wednesday, January 06, 2021, 11:37:17 AM
Incoming packet: 1297 (7928 bytes) at Wednesday, January 06, 2021, 11:37:19 AM
Incoming packet: 1298 (10000 bytes) at Wednesday, January 06, 2021, 11:37:21 AM
Incoming packet: 1298 (10000 bytes) at Wednesday, January 06, 2021, 11:37:23 AM
Incoming packet: 1298 (10000 bytes) at Wednesday, January 06, 2021, 11:37:26 AM
Incoming packet: 1298 (10000 bytes) at Wednesday, January 06, 2021, 11:37:29 AM
Incoming packet: 1298 (10000 bytes) at Wednesday, January 06, 2021, 11:37:32 AM
Incoming packet: 1298 (1668 bytes) at Wednesday, January 06, 2021, 11:37:36 AM
<MUSHclient pauses here waiting for a new message before continuing to display this one>
The whole message is quite long: https://p.teknik.io/Simple/sV3Vg
Calling Simulate while the output is blocked doesn't help. Display of the message output won't continue until a new message arrives. |