Howdy, Stranger!
Categories
- 4.8K All Categories
- 4.3K Life in Lusternia
- 453 Announce Posts
- 75 Event Posts
- 1.7K Common Grounds
- 589 Q&A
- 83 Combat Overhaul
- 1.5K World Library
- 86 Combat Logs
- 870 Event Scrolls
- 403 Mechanic's Corner
- 329 Ideas
- 314 Last Chance Trading Post
- 478 Life Outside of Lusternia
- 9 Forum News
- 275 The Real World
- 94 Meet and Greet
- 37 The Funnies
- 63 Mafia Hideout
In this Discussion
Oh snap, I think I broke my Mudlet mapper. How do I fix it?
After reinstalling mudlet and downloading the latest mapper script, I downloaded the map and now it seems like there are areas in the game that aren't being displayed. I can still room find the non-displayed rooms, so they exist somewhere ... just not on my display 
If it's broken, break it some more.
0
Best Answer
-
The best way to fix mudlet mapper problems is to reinstall the mudlet map. Find where the map data (xml, etc) is kept in your profile, delete them manually. Close your mudlet and redownload the map again. Should fix most problems.
6
(c) Iron Realms Entertainment 2012.
Answers
I previously played the mac release for Mudlet 2.0-test4 which I downloaded from Sourceforge. I also run M&M and Mudlet Mapper in tangent. All was going well enough UNTIL I decided to download / install Mudlet 2.1 Mac release from the Mudlet website.
At first, Mudlet 2.1 exhibited some minor issues. Mainly I could not use the package (in)/(un)staller feature as advertised. No worries. I manually upgraded to the latest M&M version. It was about this time that I noticed that mudlet mapper wasn't working. There was no error message. In fact, there was nothing when I used my aslias "goto" commands. This was when I decided to update both the mapper & maps.
Long story short, goto commands under the updated mapper would simply pinwheel my computer to eternity. I could not regain control of Mudlet and opted for a force quit each time. It was after several program quits / computer restarts that I decided to downgrade back to Mudlet 2.0-test4.
Alright. So "goto" commands will now display one of two things. Either the "I don't know how to get there from here" error message, or the "We're already at..." message if I happen to be placed right at my target goto destination. For some reason, I feel that this issue involves the map and not necessarily the map script.
Can anyone suggest how I can purge the old map from my computer? Does anyone have any other suggestions how I might go about trouble shooting the issue? It's become a major frustration, which has deterred me from playing Lusternia as of late.
^ This is where my profile is stored. Note that this can be different for everyone depending on their computer username (if they have one) OS, what they named their profile as well as where they installed mudlet. At any rate, the bolded part is the important part. Somewhere in your mudlet folder you should be able to access all the different profiles you have.
Here, there should be a folder called map. Maybe a map.xml file, maybe a mapper.options.lua file. Just delete these files, the map data files should be something like this: 02-03-2013#00-14-46map.dat
I'd personally advise you to try mudlet 2.1 again. There's going to be more problems in the future as both m&m and the mapper scripts get updated with 2.1+ in mind. Once you have deleted all your old map files and re-downloaded/installed a new map and mapper, you should be able to get everything up again. Good luck, Jan.
As per your instructions, I cleared out the old Mudlet maps AND reinstalled 2.1 / downloaded new maps. This appeared to be "THE" solution. I know it sounds so simple, but I can assure you that I tried a variety of approaches leading up to this point. Thanks. And I'm now back in the game!