Hi,
I run MUSHclient on OS X unconventionally, and lately I've noticed some weird hiccups that I was wondering if anyone had any idea how to solve.
There are two issues that I've noticed, and I'm not sure if they're related.
1. MUSHclient disconnects itself from the world on receiving large amounts of text at once. I am using NC and a .txt to test this. The amount of lines it will render before it drops seems to be arbitary, but is very low -- most of the time it won't even print out 20% of the text file I'm running into it before it disconnects. On running a 1000 line text file, it will render usually between 60 and 300 before it closes the connection.
2. MUSHclient has hiccups where it will delay displaying text to me when I receive smaller amounts of spam (when I am actually playing my game). That is, it will lag and receive text in 'blocks' rather than going line by line, often with multiple seconds before the screen updates.
I know my use case isn't how I'm supposed to be running MUSH, but does anyone have any idea why this might be happening? I am testing in a world without any plugins or aliases or triggers, on default settings. This occurs -both- when I run MUSHclient with WINE, and also when I run it in a Windows virtual machine on Parallels. I don't have anyone else on OS X w/ MUSH that I can ask to test this as well, but I know my friend on Linux WINE does not have either of these problems. I am fairly certain that the problem lies somewhere in how I'm using MUSH, since my testing methods worked fine in Mudlet and Parallels Mudlet without any issues.
I run MUSHclient on OS X unconventionally, and lately I've noticed some weird hiccups that I was wondering if anyone had any idea how to solve.
There are two issues that I've noticed, and I'm not sure if they're related.
1. MUSHclient disconnects itself from the world on receiving large amounts of text at once. I am using NC and a .txt to test this. The amount of lines it will render before it drops seems to be arbitary, but is very low -- most of the time it won't even print out 20% of the text file I'm running into it before it disconnects. On running a 1000 line text file, it will render usually between 60 and 300 before it closes the connection.
2. MUSHclient has hiccups where it will delay displaying text to me when I receive smaller amounts of spam (when I am actually playing my game). That is, it will lag and receive text in 'blocks' rather than going line by line, often with multiple seconds before the screen updates.
I know my use case isn't how I'm supposed to be running MUSH, but does anyone have any idea why this might be happening? I am testing in a world without any plugins or aliases or triggers, on default settings. This occurs -both- when I run MUSHclient with WINE, and also when I run it in a Windows virtual machine on Parallels. I don't have anyone else on OS X w/ MUSH that I can ask to test this as well, but I know my friend on Linux WINE does not have either of these problems. I am fairly certain that the problem lies somewhere in how I'm using MUSH, since my testing methods worked fine in Mudlet and Parallels Mudlet without any issues.