Enhanced UTF8 Maps / Aardwolf Mushclient r1802
Aardwolf Mushclient r1802 / Enhanced Maps
There have been some Mushclient enhancements made by Fiendish and Nick Gammon (the Mushclient author) to support UTF8 characters for map drawing.
These maps provide a cleaner look then the ASCII maps. Here is a full map of Aylor in UTF8:

Grand City of Aylor - UTF8 Map
Some random map snippets from various areas:

Random Lasertag Maze
Part of Eternal Autumn area
Part of Sho’aram, Castle in the Sand
Finally, a randomly generated maze where the edges wrap to give the impression of an “endless” maze. Looking at this view it’s easy enough to see the pattern, but not on the limited regular 3*3 view:

Endless Random Maze
Downloading the new client:
The latest “official” Aardwolf version of the client can be download from:
The official Mushclient home is:
There are instructions on that page for how to preserve your maps and settings from previous versions of Mushclient. There are also notes on how to stay up to date with changes as Fiendish adds them - we don’t post every version to Aardwolf.com.
Important notes specific to the UTF8 maps
- You have to use a font that supports UTF8. Dina does not. Lucida console and Courier New do.
- You do not need to turn on UTF8 in the Mushclient settings unless you are also echoing the map to your main window. If you do enable it, keep an eye out for possibly trigger issues as there as some changes to allow UTF8 for the mapper but still allow regular extended characters everywhere else.
- There are a few different options to the maps and a version that does double line characters. Type ‘maptype’ for a full list of options.
- The client download defaults to courier new size 9 for the ASCII map because it’s sized for a smaller screen. Lucida Console size 10 works well for me, but right click on the map to try different font-sizes. You can also change maptype there too.
Many thanks to Fiendish and Nick for the client side work needed to support these maps in the client.
PS: Cmud and Zmud do not support UTF8 characters. Nothing we can do about that as neither client is being actively maintained.