From time to time I find that MUSHclient will just hang and have to be force-quit for no obvious reason, after opening the world configuration dialog and looking at something like triggers, timers or aliases. This is using a world file that has worked perfectly in the past.
The reason appears to be that it happens when "unusual" data is on the Clipboard. I particularly notice this when using VirtualBox to run MUSHclient, and there is a problem with sharing the clipboard with the host operating system.
To cure this, I suggest putting something valid on the clipboard, such as a word of text. In other words, if the client hangs, before starting it again go to a text editor, web browser, email program, or anything that supports text, and copy a word (anything) onto the clipboard.
This should clear the unusual data that is confusing the client, and you can then use it normally.
Alternatively, and a little more proactively, you could force good data onto the clipboard by running a script that does something like this when the client opens:
You can make this happen from the Scripting configuration tab, by putting a function there for World Events -> Open, and put a function into a script file, eg.
Then put "OnWorldOpen" into the World Events configuration, as described above.
If you are not having problems, then you can ignore these suggestions, but every now and then I find this happens, and also find that I forget the reason for it. :)
The reason appears to be that it happens when "unusual" data is on the Clipboard. I particularly notice this when using VirtualBox to run MUSHclient, and there is a problem with sharing the clipboard with the host operating system.
To cure this, I suggest putting something valid on the clipboard, such as a word of text. In other words, if the client hangs, before starting it again go to a text editor, web browser, email program, or anything that supports text, and copy a word (anything) onto the clipboard.
This should clear the unusual data that is confusing the client, and you can then use it normally.
Alternatively, and a little more proactively, you could force good data onto the clipboard by running a script that does something like this when the client opens:
SetClipboard ("hello, world")
You can make this happen from the Scripting configuration tab, by putting a function there for World Events -> Open, and put a function into a script file, eg.
function OnWorldOpen ()
SetClipboard ("hello, world")
end -- OnWorldOpen
Then put "OnWorldOpen" into the World Events configuration, as described above.
If you are not having problems, then you can ignore these suggestions, but every now and then I find this happens, and also find that I forget the reason for it. :)