![]() |
|
|
|
#1
|
|||
|
Good points there. Certain spells that are often cast on multiple mobs should maybe be excluded from cancellation triggers like mez and root, though early breaks would leave some countdowns ticking. Hmm.
| ||
|
#2
|
|||
|
I almost exclusively use option #1. Reasons
- you can include the target name in the timer. So if for example you are mezzing a Ghost and a Goblin, you can have a mez timer running for each by including the mob name in the countdown timer - Fizzles and interrupts will give you false information if you are using Option #2 - If you are raiding, you can go into Options and filter out non-group spell messages. That will limit the number of extra timers that creep onto your screen. Example of a timer for mez: Trigger text: ^{s} has been mesmerized Timer name: <<Mezzed>> --- {s} Timer duration: 24 seconds Note however that Dazzle gives exactly the same trigger text, which is annoying: Trigger text: ^{s} has been mesmerized Timer name: <<Dazzled>> --- {s} Timer duration: 96 seconds This is the downside of Option 1. There are a couple of other examples too, such as the Lull/Calm/Pacify line all give same message, several necro dots, etc. I find I get more utility out of using option 1, and I just put up with the occasional conflicts. What would be really cool, would be if Gina could span multiple lines for triggers. So if perhaps you could search on ^You begin casting Dazzle and then within a few lines of text, also search for ^{s} has been mesmerized Now Gina could discriminate between Mesmerize and Dazzle, and other similar conflicts. Good luck. | ||
![]() |
|
|