← Back to team overview

mudlet-makers team mailing list archive

[Bug 782840] Re: deleteArea sometimes doesn't actually delete the area

 

Whoops - please ignore my last comment. I realized this bug has been
fixed (just getting used to launchpad).

Note:

The code:

for name, id in pairs(getAreaTable()) do
    deleteArea(tonumber(id))
end

(Still) doesn't necessarily delete all areas. This is because
getAreaTable returns a table of {[ area name, area id ]}. So if there
are multiple areas with the same name, only one of those areas will be
deleted because getAreaTable returns a table where the area name is
unique.

-- 
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


References