I currently MUD on Aardwolf (www.aardmud.org) and have been experiencing a rather annoying phenomenon since I began using MUSHclient rather than Zmud (a year or two ago, with MUSHclient 3.5). Aardwolf has a fairly large number of features built in to conserve bandwidth and one of those suppresses the prompt unless you actually send or receive information from the MUD. (Send a command, see a channel, get attacked, etc...)
I tend to keep most of the channels off, which results in fairly lengthy periods of no actual output from the MUD. Unfortunately, I've noticed that if the period without any output from the MUD lasts long enough, MUSHclient seems to lose the connection entirely. Though I should recieve occassional messages (notably notification when I have a quest available), the screen will just stay blank, only displaying a disconnect message when I send a command to the MUD. (This actually happens occassionally with only short breaks in the output as well, actually.)
I have created a trigger and script to send a blank line to the MUD every two minutes for the time being. However, that isn't an ideal solution and I don't know if this is actually just a setting that I have wrong somewhere, an isolated problem due to my network configurations (I am assuming this isn't the case since I didn't have the problem with Zmud), or an actual bug with MUSHclient. |