Delete for Temporary Trigs&Vars by sequence number

Posted by Roga on Sat 06 Jul 2002 01:22 AM — 7 posts, 21,870 views.

#0
It would be nice if there was a way to delete temporary triggers and variables by sequence number. This would effectively allow whole temporary classes just based on sequence number.

Is there currently a way to selectively delete temporary triggers and variables like this?
#1
This is the same thing that Shadowfyr is requesting. Sorry thought I went through previous posts.

Also,

Thanks for a great mud/mush client!
USA #2
Yeah. It was something I had suggested. It also in after thought was a bad idea. Something more like zmuds 'classes' would be better, since it allows triggers, aliases, or whatever to be placed in a group and disabled/enabled or deleted all at once, without effecting things which may have the same sequence number for instance. This will be possible with plugins, but not in a way that is particularly obvious or simple to use. Especially since even the plugins themselves may need to change the status of a group of triggers and the like, without making a second plugin or deleting itself in the process.
Amended on Sun 07 Jul 2002 02:41 AM by Shadowfyr
Australia Forum Administrator #3
I'll look into that now that I can add more things in the XML file easily.

However plugins are a solution in a way. You can disable an entire plugin, thus effectively disabling a batch of triggers/aliases etc.
USA #4
True, but not a really functional way. ;)

The problem is that inter-plugin communication is shacky for one thing. Magnum is already having a problem with that.

However a bigger problems is this:

Plugin
-triggers
-aliases
-scripting
--script sub that diables the triggers in the plugin (but only some of them).

This situtation is a mjor problem because you can't simply disable the plugin, unless you made the triggers part of a seperate one and then since they exist independantly of each other you can't make changes to the triggers, etc. between them as easilly. This is as I said another case of scope limitations, similar to Magnum's problem of calling a global set of scripts from other plugins. It just won't work, but for now we will need to make do.
Australia Forum Administrator #5
I will add a grouping name to aliases/triggers/timers and let you enable/disable a group.
#6
Thanks Nick! I think this will be a great help.

Roga