Coren momentarily changes target to the person he's going to spike.
I don't know if this can be of any use since there's probably no way to differentiate to a someone overaggroing.
The fight is rather easy as it is but there's 2 mechanics of interest to the party.
The elite adds only barrel (works like a disorient / rogue blind) a secondary target (not their current "tank").
So it's in the interest of the group not to overaggro the elite adds (Ilsa / Ursula Direbrew).
When Coren grows big and red he's about to do his spin and stun/disarm.
If the tank is in range for it he will get stunned and the adds drop aggro on the tank for the duration of the stun.
It's short duration but it's usually enough for the elite adds to run to another party member and
subsequently proceed to chain barrel the tank (since he's no longer top threat while he's "stunned").
Parties usually just overpower the event since it's rather easy.. but maybe that info could be of use to undergeared/fresh parties.
I'm using the embedded version (as it comes from files.wowace.com) and the activation is indeed on mouseover
(and the double message, which I didn't realize was a problem tbh :) - clear now with hindsight )
What version of Littlewigs are you using? and did all the bars pop-up, mainly the Littlewigs pyroblast cast bar?
If that question was directed at me, I'm using the latest revision.
Pyroblast warning has been removed per Ulic (see a couple posts higher) so I didn't expect to see any warnings.
Just providing a transcriptor log of the fight in heroic to facilitate adding it back in.
Thank you, I knew something was gonna get fubared with the same boss in two places. I just made an adjustment that fix it.
Your workaround took care of the AceLocale error.
I got a new error with the latest build.
Line 67: local mod = BigWigs:NewModule(boss)
since BigWigs has a module registered for Tempest Keep with the same name.
Applying the same workaround for it that you used for AceLocale seems to have took care of everything.
I changed the line to
local mod = BigWigs:NewModule(boss.."(MT)")
in my local copy and it's working fine.
Left the 'boss' name itself intact since it's used in the engage trigger and health calculations for the warnings.
About the beacons.. first 3 are already out (not summoned) ie encounter starts with Boss and 3 beacons,
so no yell about those.
His engage yell is "I've longed for a good adventure!", and his death yell is "I must bid you... farewell."
My log is good as every beacon that was summoned dies by the end of the transcript, helps with math.
(many parties kill him and being oom die to adds)
So your analysis is 99.9% correct :).
12 adds total (1 beacon killed before it transformed to apprentice the other 11 after).
First 3 start with the boss hence no summoning yell.
Leaves 9, so 3 yells summoning 3 each time.
(not sure if it's 3 at once or in set intervals as you say, will have to ask one of the ranged people)