mudlet-makers team mailing list archive

[Steven Rose <smr@xxxxxxxxxxxxxxxxxxx>]

I just had a quick look.
It seems that there are two maps that store area data.

One map is called areaNamesMap and this relates areaID's to area names.
The other is called areas and this relates areaID's to TArea.

So what should happen is that both these maps should always have the
same ID's in them (I assume).

But what is happening is that some IDs are in areaNamesMap that aren't
in the area map. The cause of which I haven't narrowed down yet.

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

Title:
  deleteArea sometimes doesn't actually delete the area

Status in Mudlet the MUD client:
  Confirmed
Status in Mudlet 2.0 series:
  Fix Released

Bug description:
  Not sure why, but sometimes it doesn't remove the area from the list.
  It does delete the area though as in you can't get a room list of it
  though.

  lua getAreaTable()
  table {
    'Lake Narcisse': 106
    'Cyrene, the City of (Brewery)': 67
  }
  lua deleteArea(106)

  lua getAreaTable()
  table {
    'Lake Narcisse': 106
    'Cyrene, the City of (Brewery)': 67
  }

  Sample script:
    for name, id in pairs(getAreaTable()) do
      deleteArea(tonumber(id))
    end
    dispaly(getAreaTable()

  Should return {} at the end, but it doesn't.

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