← Back to team overview

mudlet-makers team mailing list archive

Re: [Bug 883366] Re: Add triggers priority to control match order

 

The priority is:

All UI items are in the visual order that they're at, including groups
ie:

GroupA
__trigger1
__trigger2
GroupB
__trigger3

Will go off in trigger1, trigger2, trigger3. When you create scripted
triggers, they go off after UI ones, in the order of creation:

GroupA
__trigger1
__trigger2
GroupB
__trigger3
temp* triggers:
__trigger4
__trigger5
__trigger6

Mudlets priority *is* manageable, easier than other clients for the
majority of coders. I'm sorry, but this setup was working for pretty much
everybody so far and this is definitely not a sore point in the client,
while addressing it would bring complications that would bring confusion -
I don't think that given the lack of demand, UI complications this'll
bring, and other factors that need more addressing, that it should be
improved upon at this time.

Addendum: When porting your system over, you could arrange the triggers in
groups visually as it's necessary. In my practice only a few certain
triggers need to be in priority, for a good deal, it doesn't matter. If
you'll be only creating them via the API, then creating them in order will
work as well. In my experience I haven't had the need for shuffling the
matching order of triggers at runtime so that's a non-issue (and if it is,
you could mitigate it with some buffering). I hope you can work that out
because I don't see this as an issue at the moment and it's not a widely
requested feature at all.

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


References