Good to know - if I use Mudlet 3 again I will run it from the CLI.

Hmm. It might be worth considering a default file to log exceptions and errors without attaching a debugger so that users can attach a log when they notice something weird... I generally work on web applications, and error logging is a pretty big part of how we monitor for quality.

I highly doubt that the MUD server caused this issue. I am a professional programmer - I don't see text from a terminal could basically crash my entire display.

When I mentioned logs, I was thinking logs of Mudlet. Stack traces and such. That seems much more likely to be valuable.

Is there a log somewhere that I could copy and paste? Couldn't find anything about that in e.g. http://wiki.mudlet.org/w/Known_Issues#R ... udlet_bugs

fyi, running OSX 10.11.5 with Mudlet 3.0.1, the display freaked out and I couldn't click anything - the text from the MUD started showing up in all my other windows which overlayed on it, and so on. Hard to describe and it was rather difficult to do anything, including getting out of it, so I couldn...