allow temp*Trigger to auto-remove itself after specified number of matches

Bug #1103873 reported by Garagoth
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mudlet
Opinion
High
Unassigned

Bug Description

Currently to create tempTrigger and then remove it it is necessary to have global variable that stores its id. And then code of temp trigger must use that global variable to killTrigger itself.

Please add parameter that will cause temp*Trigger to auto-remove itself after specified number of matches.

Regards,
Garagoth.

Tags: triggers
Revision history for this message
Heiko (koehnheiko) wrote : Re: [Mudlet-makers] [Bug 1103873] [NEW] allow temp*Trigger to auto-remove itself after specified number of matches

Yes, this is on my todo list.

Am 24.01.2013 09:11, schrieb Garagoth:
> Public bug reported:
>
> Currently to create tempTrigger and then remove it it is necessary to
> have global variable that stores its id. And then code of temp trigger
> must use that global variable to killTrigger itself.
>
> Please add parameter that will cause temp*Trigger to auto-remove itself
> after specified number of matches.
>
> Regards,
> Garagoth.
>
> ** Affects: mudlet
> Importance: Undecided
> Status: New
>
>
> ** Tags: triggers
>

Heiko (koehnheiko)
Changed in mudlet:
importance: Undecided → High
Revision history for this message
Chris (chrismudlet) wrote :

I'd like to have a kill argument as well for triggers, which would auto-delete themself after matching

Revision history for this message
Heiko (koehnheiko) wrote : Re: [Mudlet-makers] [Bug 1103873] Re: allow temp*Trigger to auto-remove itself after specified number of matches

this is on my personal feature list for 2.2 already

Am 08.03.2013 04:32, schrieb Chris:
> I'd like to have a kill argument as well for triggers, which would auto-
> delete themself after matching
>

Revision history for this message
Chris (chrismudlet) wrote :

What is the status of this?

Revision history for this message
Roland Goldberg (phoenixcodes) wrote :

Can we maybe have this for 3.1?

Revision history for this message
Vadim Peretokin (vperetokin) wrote :

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

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

Changed in mudlet:
status: New → Opinion
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.