It's not something I'm used to seeing myself, however something I am used to seeing is, some DPSer or a pet gets aggro due to positioning, and then immediately a HoT tick fires, and the facepulled mobs go directly for the healer instead of the person with the face.

We've been seeing this an awful lot in ToC recently, particularly when melee DPS gets affected by mind control and moves to a position where they cause proximity aggro when the MC wears off.

Did someone use Mirror Images?

Each case for us was during a trash pull, so I doubt it, though I can't say no with any real confidence. Either way, if a Mirror Image had actually wandered over to another un-aggroed group (or in one case, boss) and started firing at it, we would have noticed. It would also be pretty unusual behavior, even for Mirror Images before whatever patch that was supposed to reduce their weird habit of running off to attack something else you're in combat with (e.g., mage on Feugen and an image running over to hit Stalagg). However, if you're asking because there's some known issue with Mirror Images having unusually large passive aggro radii or something similar, that would be good to know.

Mirror Images have a history of mystery pulls (they'd pull Vezax while handling the trash if used in that room) thus the question.

I searched and was unable to find this information if someone already posted it. I realize the choice to extend is individual, but wanted to verify that if one person keeps an extended lockout they can keep pulling players in who have had IDs since the week of the lock out being extended. For example week 1 we spend 90% in ToC and GToC, clear a couple bosses in Ulduar. Week two stumble and spend it all in ToC and GToC, week 3 clear ToC and GToC and have time to work on Ulduar. Do we need only one toon from the week 1 Ulduar to keep extending while others could run an off night Ulduar in week 2, or would those who ran a different Ulduar on an off night week 2 be unable to join the extended Ulduar from week 1?

Unable to join. It does not provide two instances in a week. It's strictly new OR old.

If you "keep" your RaidID it is kept only for yourself. The other 9-24 people will refresh on Tuesday (unless they also decide to keep it).

Until you zone in (or kill a boss? Not sure, didn't test) you can release this saved ID later in the week as if you had allowed it to expire normally. So if you saved it, finished clear, and forgot to unlock, you're not hosed. You have forgiveness to unlock unless you have actually continued usage.

Now if you saved ID and the other 9 did not. 5 go run a fresh 10man with friends and kill bosses. They get a new raidID. You invite them to a raid. You zone in with 4 who have done nothing this week - to last week's raid. The other 5 zone in to this week's raid where they already killed things.

As long as someone isn't locked to anything that week, they will be able to join your extended lockout. So it should be possible to extend an ulduar from week 1 to week 3, and have everyone (except for the one person who is extending) do a different ulduar in week 2.

Best practice is actually to zone in a lvl 80 alt to get saved, and extend the lockout on that character, and let the entirety of the raid reset to give you the fullest amount of options and prevents you from having to make a decision any earlier than your next raid night. Everyone can run a fresh instance or use the alt's saved raid.

There's no need to set up an alt, you can extend an instance from the previous week as long as you aren't saved to that instance this week. It will be grayed out on your raid instance list until you extend it.

That was my initial reaction, too, but that still eliminates one possibility: extending a raid ID for use in a later week. If you have, say, last week's raid ID saved on an alt, you can raid normally this week, then go back to the previous ID next week. Would work nicely if you were working on Firefighter, for example, and the following week was going to be short or have weird attendance issues due to a holiday or vacations (e.g., Labor Day!), but you want to get back to working on Mimiron the week after the holiday without wasting 2-3 hours clearing up to him.

Nevermind, I was able to find my answer.

I was under the impression that you could cancel the lock if you didn't kill anything or when you start the first encounter in the heroic TotC.

We didn't get a chance at Algalon 10 last week (scheduling issues), but cleared to Yogg on alts. Rather than yawning through FL and XT to reach Yogg, I've hijacked that raid ID on my main. We logged on an alt, invited my main. I zoned in.

No message, no lock warning, no countdown. At first I assumed normal issues trying to pick up another player's raidID (they may need to zone in first, etc). But, no, I'd inherited cleanly first go - only Yogg was alive in the instance and I have the raid ID.

Haven't checked today to see whether I will get the correct instance when I try.

TLDR: Warning you will be locked is not displaying at least some of the time - it immediately occurs on zone-in with no warning or waiting.

As was I, but unfortunately this wasn't the case. As soon as I entered; I got saved.

I got invited to a Naxx10 that was in progress (two wings down?) for gearing up some guild alts the other day. I zoned in, didn't get any notice that I was going to be saved. I did not check my raid tab, but I did notice that as soon as we killed the next boss I got the message "You are now saved to this instance." I have to do further testing, but it appears that I didn't get saved to the instance until I was present for a boss kill. Anyone else see this phenomenon? I'm certainly going to try and figure out what is going on - seems sort of fishy.

We zoned in for Algalon. Proper instance - only Yogg left. No warning messages for anyone at any point. Several guild members freaked as they weren't paying attention when I explained the game-plan.

As soon as we opened Algalon's door we got the locked message. Again, no warning messages at any point.

Since special requirements have to be met to open Algalon's door it probably dictates that those inside the instance must be tagged with that raid ID. Otherwise, what's to stop a group from continually using alts to clear the first couple bosses, bring in their mains to fight Algalon, wipe/fail and then start all over with new alts and their mains.

Assuming a couple sets of decently geared alts a guild could get several hours per week on Algalon if you weren't saved when opening the door. I'm sure Blizzard doesn't want that and made it so that opening the door saved you; most likely you would be saved anytime you zone in during the one-hour period as well.

Also, /wave

A similar reason probably exists for this as well.

Edit: A good rule of thumb is that under normal conditions you will not be saved to a raid when zoning in even if a boss has been defeated. But if anything has been done to that instance ID to alter it from a normal clear you will be saved without having to defeat a boss; in this case it will probably give you a warning but it doesn't seem that this is always the case. There may very well be some conditional that Blizzard uses to determine whether you get a warning or auto-save (like for Algalon) but there may very well be some conditions that are set wrong or not accounted for.

Indisputably. Engaging Algalon (or opening the door) should lock to an instance. However, the fact we could zone in with everything dead except Yogg/Algalon with no "You will be locked in 60 seconds" message is disturbing. This warning message was a deliberate upgrade (an excellent one) by Blizzard and it now seems at least mostly non-functional.

For 9 of 10 characters they had never, ever had this raid ID (I hijacked it from our alts, as I said). Only my toon had it from zone in Monday (when, again, I got no message I was being locked) and then extend. The other 9 never received a notice they were gaining an active raid ID, this is why some were wigged out to find things already dead (since they hadn't listened to a word I said on vent).

I can only guess that extended IDs play "silly buggers." Everyone temporarily gets the raid ID to zone in to the same instance. But if no one engages/kills a boss you all still have the option to step outside, un-extend, and all go into a fresh instance. I just find the fact that no one is informed what's going on can easily lead to confusion. Raid extension (to your common player) is confusing enough. "Wait, you can extend, but then change your mind? So you could extend, kill something, then get a fresh instance? No? Why not? Either you can un-extend or you can't, what's this halfway business?"

/salute Tin

On the Algalon front at least this may be a change independent of the other new saving rules - I read that it was possible to summon someone who is Algalon keyed to the door to the planetarium in an instance where no one else was keyed, have him open the door, and then leave before the timer ran out on the "this instance is in progress and you will be saved to it" dialog, The above "instantly saved if the door is opened" rule would stop anyone from doing that.

I thought this was interesting in my guilds ToTC NORMAL 25 man Faction Champion kill. Went from near full health (around 18,000) to dead in less then a second due to Blade Flurry spam from the Rogue.

Link to WoL: World of Logs - Real Time Raid Analysis

Printscreen of the last events before death: Imageshack - bladeflurry

That's how Blade Flurry interacts with Fan of Knives. Try not clumping up so much in the future.

Got to talk to a GM today about the issue I stated above. The answer I got (or at least as I understood it) is that if you extend your raid from last week and enter it, you will be automatically saved, no question, nothing. If however you extended your raid from last week and another member enters who wasn't part of that particular save or hadn't extended theirs, they would get a question asking if they want to save themselves or not.

To me, it seems kinda weird because now really the safest way to enter a raid is to extend it as a raid leader and then let someone else to enter first to check if it's right.