About Triggers

Triggers are commonly used to coordinate jousting AOEs or red-text warnings. A trigger is simply a regular expression matcher. You can match any text that appears in your eq2 logfile. In many encounters a single player (or a couple of players) will receive a red-text warning or detriment that nobody else can see. A trigger with broadcast enabled can be used to detect the event and inform everyone else through the server connection.

Trigger Editor

The Trigger editor looks like this.  When you select a Zone, all triggers for that Zone are displayed in the listbox below.

Adding a Category

Right click the Category section and select Add Category

In the dialog, enter the name for the new category

Adding a Zone

Right click the Zone section and select Add Zone

In the dialog box, enter the name of the Zone:

The zone name MUST match the actual zone text when you enter it. The filename will be appended with a “.xml”, it is not necessary to enter it.

Trigger List

This listbox shows all of the triggers you have defined for a zone.

Adding a Trigger

Once you have a zone selected, you can right-click the triggers list to add a new trigger:

  • Enabled – You can disable detection of this trigger by toggling Enabled
  • Broadcast – If this is checked, whenever the trigger is detected, it will send notification to all connnected clients.
  • Display Timer – Display a timer for the trigger
  • Name – the name of the trigger
  • Timer (sec) – the interval between first detection and next expected detection.  NOTE: there is some wiggle room here (9 seconds) for early detection.
  • Warn At (sec) – at what point during the countdown to alarm.  Setting this to Zero will disable the Warning.
  • Remove After (sec) – when to remove the Timer progressbar after the Timer duration has ended
In the example above, the Belkreiz Blazeclaw Curse is a singe-player detected red-text emote. This has broadcast enabled so everyone will know they have the curse coming. The highlighted trigger is the joust for Malteor Flamecaller. This red-text appears in everyone’s log file, and does not need to be broadcasted.

Importing a Trigger

A new context menu option is available to import a trigger from ACT. See Importing Triggers from ACT for details.

Trigger Configuration

This is where you enter in your regular expression to match.  You can do grouping as well, which can then be referenced in the detection/warning/macro sections.

Trigger Options

When speech is enabled, the name of the trigger will be pronounced, saying “TriggerName hit”. If the name is too long, or sounds odd, you can override how it is pronounced here.

Infection Configuration

  • Remedy – What Remedy is Required to cure this infection
  • Remedy Color – Sets the color of the infection text in the alert window
  • Remedy Success – What is done to cure the infection (item, cure curse, etc)

Delta Configuration

Detection Options

By default, the chat window will be updated with the text “TriggerName hit TargetName”, you can however tell it to write something else (like GET OUT). You can also override what it “speaks.” Alternatively you can play a custom sound file (mp3/wave/etc).

Warning Options

This works just like the detection options, but this is what is performed when the warning interval is reached.

Macro Settings

This is much like the detriment call macro extension for ACT, but is capable of doing much more.

  • Detection File – specify where to write the file.  Make sure to include the full path.
  • Write To File Text – this is what will be written to the macro file, using regex grouping and builtin variables.

Macro Example

When Maalus puts the bad curse on someone, the macro could do this: useabilityonplayer {TARGET} cure curse rsay Curing {NAME} from {TARGET} Set the detection file to: maalus.txt When the pattern is detected, it will create a macro file which you can then hotkey inside EQ2. maalus.txt will contain: usabilityonplayer Player cure curse rsay Curing Curse of Devastation from Player In EQ2, if you have a hotkey setup to invoke the script: /do_file_commands maalus.txt It will cure them!