Potato MUSH (MUD) Client

Potato MU* Client, by Mike Griffiths, is a popular graphical MUSH/MUD/MOO/MU* client written in Tcl/Tk.

http://www.potatomushclient.com/wpdev/wp-content/themes/spud/images/headbar-text.png

Attributes

Website
potatomushclient.com
Source
Github
Help files
Github Wiki (also powers the in-app helpfiles)

Description

MG: It was originally started as a very basic client by a friend of mine, who named it Potato (so don't blame me for that;) and I've re-written it twice now to expand the features, and (the second time) to clean the code up and update it to Tcl 8.5. Runs on 8.6 as well - untested on Tcl 9 but can't foresee any reason it shouldn't work.

Potato has all the features you'd typically expect in a MUSH/MUD client - telnet support for a number of basic and MU-specific protocols, address book for saved worlds, multiple connections, saved logins, ANSI and XTERM colours, spawn windows. Customisable keyboard shortcuts and hotkeys.

One of Potato's unique features is having dual input windows, allowing you to easily respond to messages while in the middle of writing code or RPing poses.

Runs on Windows, Linux, and MacOS (though I unfortunately don't have access to do updated builds), and has been run on Android previously from source (but again I've not been able to build native executables, and ideally needs a separate skin for smaller mobile devices).

Utilities

There are also a few utilities written in Tcl used for the build process (utilising a slightly modified sdx), for generating msgcat templates for all the languages Potato has been translated into (including marking messages no longer in use in the source code, and giving file names/line numbers for where the message is used for checking context, if needed).

Future projects

I have always intended to write a wrapper which runs the latest version Starkit (or downloads it if one isn't present), so that this can be built into executables for various platforms and then they don't need to be rebuilt for the Tcl code to be updated - I haven't bothered because I wouldn't be able to do the Mac/Android builds if I wrote it (but also haven't tried too hard to find someone who may be able to help with those builds since I haven't written the wrapper...)