I didn't understand what you meant by "custom trigger handling" -- does this refer to onProcessTrigger(), onReceiveKey(), and the like?
Yep. Basically the parent script has to iterate through each of the multiscripts and see if any want to handle each call.
I'm in the dark about regex pattern matching for each script. Storing and referencing a regular expression string per-script seems straightforward, but how the resulting regex is used by Scripter to work with FARR is not clear to me. If someone already has a clear idea of what to do, I'd be happy to hear it
Again basically the parent script needs to take each RAW search, and iterate through each of the multiscripts and see if any of them should handle it based on their own regex match.
As far as UI is concerned, a simple starting point might be a dialog box appearing via Scripter's "Configure Advanced Plugin Options" button. However, does it seem doable to achieve per-script configuration via the Plugin Manager dialog box (at least eventually)?
I think we are on the same page.. basically when user says to do advanced config of the parent manager script, it should show a page of options. this page might look like a checklist box of each multiscript plugin found, where individual scripts could be enabled or disabled.
If individual plugins wanted to have their own options.. there would be a few choices.. you could have a button next to each multiscript to show *ITS* options, or maybe a simpler method would involve each mutliscript providing some html text with some form inputs that would be for that scripts options, and the multiscripter would present all form htmls on one page. And then let the multiscript save all the variables using the new UserVars option in FARR.
This is the most confusing and advanced part of multiscripts and i think for now these options ideas can just be ignored for version 1.
Do you think script management would be a matter of tracking an enabled/disabled value per script? Is there an issue with asynchronous processing? How might enabling/disabling a script be affected by this?
I really don't see any issue here -- all you are doing is telling the mutliscript supervisor to ignore certain scripts and not even bother to call them with a chance to match search or trigger result.. shouldnt be a big deal.