mudlet-makers team mailing list archive

[Heiko <883366@xxxxxxxxxxxxxxxxxx>]

Mudlet's trigger engine is far more advanced than TF's. Prioritizing 
triggers in Mudlet is done on the basis of a straight forward visually 
referenceable strict ordering approach. Triggers are being run top-down 
with folders being completely expanded before the next sibling is being 
processed. This parent/child approach is both considerably faster (when 
used in conjunction with the rest of Mudlet's gate and chain features) 
than using old fashioned priority queues as well as conceptually way 
more powerful.
Take a close look at the description of the trigger engine in the manual 
(though this is very incomplete) to get a little insight into the 
potential e.g. trigger gates, complex function based multi state 
triggers, dynamic trigger chains, filters etc..
Going back to priority queues would get Mudlet back to stone age as none 
of the advanced features of Mudlet would be possible.
By the way, priorities make no sense in a complex multi script package 
environment where users take packages that other people have written. 
Mudlet's parent-child strict order approach works very well with 
packages whereas priority queues would fail miserably.

Here's my definitive answer regarding this topic:
Chances of a paradigm shift for the worse = 0%, but if you can contrive 
strong use cases that really do require priority queues and cannot be 
sensibly solved with what Mudlet currently offers, I'll add script only  
priority queue based triggers as an additional feature.

Heiko

Am 30.10.11 06:05, schrieb Garagoth:
> So you agree that some scenarios are impossible.
> Also, how can you arrange triggers so trigger 2 from group 2 firest before trigger 2 from group 1, but after trigger 1 from group 1?
>
> Can you make this an enhancement request?
> Make all triggers priority default to something to maintain backwards compatibility and allow setting a priority via UI and in scripts for script created triggers.
>
> I am trying to migrate some of my scrips from TinyFugue client and
> manageable trigger priority is a must...
>
> G.
>

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

Title:
  Add triggers priority to control match order

Status in Mudlet the MUD client:
  Invalid

Bug description:
  Please add priority for triggers.
  Currently it is unpredictable and not easily changable in which sequence multiple triggers (triggering on the same incoming line from MUD) will execute.
  All triggers should be tried against incoming line in sequence determined by priorities.

  Regards,
  Garagoth.

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