mudlet-makers team mailing list archive

[Vadim Peretokin <vperetokin@xxxxxxxxx>]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/757

This issue needs to be closed and there is no appropriate status, so
will set it to "Opinion" just for migration purposes.

** Bug watch added: github.com/Mudlet/Mudlet/issues #757
   https://github.com/Mudlet/Mudlet/issues/757

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

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

Title:
  Code omission: room removal does not remove (TArea *)->exits that exit
  TO that room

Status in Mudlet:
  Opinion

Bug description:
  This relates to but is independent of #1248806 {fast_ &
  ausgaengeBestimmen() don't store TO roomID}.  I think that another
  pair of eyeballs would help but as the summary says, when we delete a
  room we'll need to make sure that if it is the END of an inter-area
  link (as should be recorded as the first pair member of the inner part
  of a TArea's exits member {a QMap structured as: <int {in-area Start
  Room Id}, QPair<int {out of area End Room Id}, int {direction}> >}
  then that entry is removed. Unfortunately this would seem to require a
  scan through every but the deleted room's TAreas' exits...

  In current code, of course, the exits member is not used however I
  understand discussions over map route finding may touch on inter-area
  links of which this is a resource that would be directly relevant.

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