mudlet-makers team mailing list archive

[Stephen Lyons <slysven@xxxxxxxxxxxxxxx>]

I think this is confirming something I suspected with the current code
in that for a newly downloaded XML map file it does not put the "rooms"
into the "areas"...!

I suspect the Debian packager is a little conservative on the builds
that they package but I suspect that the "current" "release_30" code on
the GitHub repo will fix this if you "save" the new map and then "load"
it in again - the new "auditing" code will notice that the rooms are not
in the areas that they are supposed to be and will "fix" things when the
new map is reloaded normally.

As a work around you may get away with things if you write a script that
iterates through all the rooms and moves each room from the area it is
supposed to be in, to a different area and then back to the original
area - you may get an  error message for each room when it is moved from
the original area about the room not being "in" that area but try it and
see if that fixes things...

** Changed in: mudlet
   Importance: Undecided => High

** Changed in: mudlet
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1597298

Title:
  mudlet map cannot handle new Lusternia map

Status in Mudlet:
  Confirmed

Bug description:
  When I login to Lusternia there is a note saying the map needs to be
  updated. I go into Options->Preferences->Mapper and click Download.

  After a while the map is downloaded. However the Map (Alt+M) is blank.
  Either closing and opening the map or even restarting mudlet does not
  make the rooms and exits appear.

  The info display showing what room should be shown does appear and is correct for the room I am in.
  This is mudlet 3.0.0 delta using the Debian package on a Debian GNU/Linux system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1597298/+subscriptions