mudlet-makers team mailing list archive
-
mudlet-makers team
-
Mailing list archive
-
Message #02697
Re: [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
>
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1103873
Title:
allow temp*Trigger to auto-remove itself after specified number of
matches
Status in Mudlet the MUD client:
New
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1103873/+subscriptions
References