mudlet-makers team mailing list archive

[Heiko <1132260@xxxxxxxxxxxxxxxxxx>]

For the time being I simply reorder the trigger list after
package/module import. We can think about Chris's solution again when
temp trigger priorities have been implemented, but for now this is much
easier and won't cause any problems.

** Changed in: mudlet
       Status: Fix Committed => Won't Fix

** Changed in: mudlet
       Status: Won't Fix => Fix Released

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

Title:
  Perm triggers created after temp triggers run after temp triggers

Status in Mudlet the MUD client:
  Fix Released

Bug description:
  Temp triggers normally run after perm triggers, however but not if the
  perm trigger was created later. For example, when you reinstall a
  package or a module, its perm triggers will be running after existing
  temp triggers.

  This creates an issue where perm triggers rely on the original MUD
  colors to do their work, which temp triggers later modify. If those
  perm triggers start running after temp triggers, they won't work.

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