mudlet-makers team mailing list archive

[Chris <1132260@xxxxxxxxxxxxxxxxxx>]

Here are a two potential ways to address this:
1) have another trigger mapping in addition to the mTriggerMapUnit for temporary triggers.  This is the easiest and probably cleanest.
2) implement trigger priorities -- would be a nice feature for players, but would conflict with our visually implemented priorities we have in the trigger layout.

I'm going to go ahead with 1) unless someone gives me a good reason not
to.

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

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