You shouldn't need to switch away from Mudlet. It works fine for me and several others.
I assume you are referring to these instructions posted by Katherine in a different post:
Katherine wrote:1. download the .dat file from the links Adael posted in another thread. Credit: Groderick and/or Saul?
https:// sourceforge.net/projects/wotmud ... rce=navbar
2. go to mudlet preferences and import the map DAT file
3. download the xml scripts from Adael:.
http: //www .dropbox.com/sh/b5k3mwonr3ap ... P4IUa?dl=0
4. import them as a package, this will add scripts, aliases and triggers to your mudlet profile. The scripts should automatically execute which will cause a map window to appear over the main window.
I believe you actually only need to go to the second link now, as Adael has uploaded the .dat map file along with the others files at that location:https://www.dropbox.com/sh/b5k3mwonr3apb35/AAB4LWJVc42eXLcackyXP4IUa?dl=0
You just need to download all of the files. Then, open Mudlet and (after connecting) go to Settings > Mapper > Press to chose file and load, then navigate to the location where you save the files, and select the WotMUDmap.dat file. Save the changes.
Next, you need to import the scripts and triggers (these are the .xml files in the folder). The link contains a whole bunch of scripts and triggers, but you do not need all of them to get the mapper going. You just need the ones that have 'Mapper' in the file name. For each of those (Mapper Aliases.xml, Mapper Scripts.xml, Mapper Triggers.xml), at the top of Mudlet click on Package Manager, then click Install and navigate to the location of the .xml files. Select the file, and click Open and Ok. Repeat the this process for each of the .xml files that has Mapper in the name.
Then, I would restart Mudlet (make you you tell it to save the profile when exiting), and restart it. Not sure if this step is necessary, but I would do it just in case. Then, log back in, type the 'look' command and the map should move to your location, and you should be good to go from there.
Sometimes the mapper gets confused. If you use the 'look' command it will normally help the map to find where you are. If it still seems confused, you can type 'resetqueue' followed by 'look' and this will usually sort it out.