mudlet-makers team mailing list archive

[Vadim Peretokin <vperetokin@xxxxxxxxx>]

Public bug reported:

One person consistently is not getting the map they should be with
loadMap:

(mapper): Map downloaded, loading it in...
(mapper): Map loaded fine - enjoy!
(mapper): Locking all wormholes...
(mapper): Locked 0 known wormholes.
(mapper): Unlocking all sewer grates...
(mapper): Unlocked 0 known sewer grates.
(mapper): Marks from the old map migrated successfully.

The output is from a script that download a common map file, a file that
includes wormholes as special exits. The same code downloads and finds
300+ wormholes fine. The code checks the loadMap() return value to say
whenever it loaded or not - so loadMap is returning true when the new
map data actually is not getting loaded in.

** Affects: mudlet
     Importance: Undecided
         Status: New

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

Title:
  loadMap() in certain cases does not actually load the map

Status in Mudlet the MUD client:
  New

Bug description:
  One person consistently is not getting the map they should be with
  loadMap:

  (mapper): Map downloaded, loading it in...
  (mapper): Map loaded fine - enjoy!
  (mapper): Locking all wormholes...
  (mapper): Locked 0 known wormholes.
  (mapper): Unlocking all sewer grates...
  (mapper): Unlocked 0 known sewer grates.
  (mapper): Marks from the old map migrated successfully.

  The output is from a script that download a common map file, a file
  that includes wormholes as special exits. The same code downloads and
  finds 300+ wormholes fine. The code checks the loadMap() return value
  to say whenever it loaded or not - so loadMap is returning true when
  the new map data actually is not getting loaded in.

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