I've been telling myself I'm going to stuff in all the affliction triggers soon...but Nexus is making that thoroughly unenjoyable...

One problem I'm having is that, for instance, I trigger the word 'confusion' for the diag line, but then the same word will appear in the middle of some other unrelated thing, like someone stumbling in 'confusion' from the Pool (traveling back from the nexus world). Luckily, I'm only linking my triggers to echo lines that tell me the affliction and the cure shortcut...but is there any way to avoid this problem? I use {<} at the beginning of the line...

Any other advice for this entire process would be appreciated too...I'm really just planning on going through the existing lists and typing them all in, echoing back the cures...

i'm not exactly sure about that but i have the same problem. I think it has something to do with the DIAG starting new lines and I don't know how to trigger things in new lines either. the example you gave uses confusion in the first line so that's why it responds to that.

Pattern: {<}confused.{>}

Script: outr pennyroyal>>eat pennyroyal

That means that the word has to be both the beginning and end of the line to work. Won't work everywhere though. And there's some kinds of triggers that I don't think you can work out without just including more words from the actual confusion trigger.

As Shiri suggested, it would be useful to match both the start and the end of a line.

Another option might be to store all of your diagnose triggers in a group that is turned on by the diagnose trigger line 'You are:', and then subsequently turned off by the successful curing of an affliction. This should prevent them from firing during the general course of the game. However, depending on your queuing, it might limit you to only attempting to cure one affliction per diagnose.