Usability for trigger/variable/alias

[chrisspanton]

Few things to note here, might be best to break these into separate issues?

• Listing, changing, or creating triggers too prone to firing triggers. Can we disable trigger execution while displaying results of trigger commands?
• Overwriting a trigger/alias/variable provides a link to revert. Handy! Deleting does not. Please add!
• A script editor in the client would really be handy here... too many problems with editing in the command line. ** The command line clears when a trigger executes (all, or just some? Either way...) as a result trying to edit triggers while anything is happening (imagine trying to create triggers while xp in a group, for instance) is nearly impossible.
• no ability to enable/disable triggers/alias/variable without deleting them, which sucks. Imagine creating some triggers for an xp run in a zone, then trying run through that zone to get somewhere without fighting. Or any of a thousand other scenarios... ** Also, a derivative here is that we currently dont have classes or groups for triggers/variables/alias. Imagine that you likely will have a group of things you want to enable/disable all at once.
• Creating trigger/variable/alias is too spammy. Imagine I have an alias that sets trigger/variable/alias from within, and fires on triggers. I dont want all that spam of creation every time my trigger updates a value.
• Variables / Aliases cant be called from the command line. Calling variables is actually odd... is it only a lookup field? Can I reference values in that field for use in actions either in trigger or from within command line? Can I edit the list without re-writing the whole thing? ** this is circular and gets back to value recall. How can I edit a list in triggers, recall values, execute actions, then repeat the cycle? ** example trigger fires to generate list of mobiles in a room. Adds to a variable. Next a trigger fires to attack the first item in the list. Finally, when that is dead another trigger fires to update the list, then kill the next item in the list.
• It would also seems much simpler from a user perspective (maybe this is just me?) to allow value recall of variables in an alias, rather than the mess that currently exists of passing parameters.