Exemplar

We extended a 25man this week. Everyone zoned in and immediately received message they were locked. No timers, no questioning, no delays.

Not all of these people were locked to it from last week.

Rock: "We're sub-standard DPS. Nerf Paper, Scissors are fine."
Paper: "OMG, WTF, Scissors!"
Scissors: "Rock is OP and Paper are QQers. We need PvP buffs."

 

◊ Bryne

Was it ToGC25? That has different mechanics as well.

 

Exemplar

Nope, Uld25. We cleared to Yogg the week previous and were working on our first Mace that week (lousy luck on Fragment drops - RNG for the loss).

Rock: "We're sub-standard DPS. Nerf Paper, Scissors are fine."
Paper: "OMG, WTF, Scissors!"
Scissors: "Rock is OP and Paper are QQers. We need PvP buffs."

 

Tinwhisker

I just had a thought. If you had sent any of the keepers down, that will have "changed" the instance in a way that can't be undone (similar to opening Algalon's room). That more than likely means an automatic lock upon entry.

You're a lot of DPS, you know that? You wanna' earn 14 achievement points the hard way?

 

Exemplar

This still makes no sense from a play perspective. Opening Algalon's room locks as soon as the door opens. Extending that raid to a future week will permit either 1 hour on Algalon maximum - either this week or in the future (the hour begins after engage, not door open). The door opener is still locked this week and cannot open another. Whether he opens one next week and 2 raids both hit Algalon that week, it's effectively identical to one this week and one the next. You cannot get extra time on Algalon.

Newly reset week. We zone in - everyone is immediately locked even though we've done nothing that week? Again, makes no sense. Zone in, talk to a Watcher Image to activate them and be locked - makes sense. There are valid reasons to lock on zone in, but all of them should spawn the new 60 second warning and give a chance to bail.

As far as I can tell the 60 second timer is rarely effective. Caveat emptor. Mostly treat zone-in like the old system: assume you'll be locked immediately.

Rock: "We're sub-standard DPS. Nerf Paper, Scissors are fine."
Paper: "OMG, WTF, Scissors!"
Scissors: "Rock is OP and Paper are QQers. We need PvP buffs."

 

Maranora

For what it's worth: I recently (last Thursday?) zoned into Ulduar10 to go stealthy Frost Lotus hunting in Freya's room; I had no ID, and was grouped with one of our raiders (with ID) who was NOT in the Instance. I entered the correct instance, there was a dialog - presumably the lock in dialog - which flashed up for a fraction of a second and was then gone again. I do not know for sure if I was locked to the instance (or just inside it without a lock), and since I didn't care either way, I paid it no further heed. However, it does beg the question: can anyone confirm that the lock-in question comes up anymore at all? Or has it possibly been removed in favour of a "get locked when Something Important occurs while you are in the ini" type mechanism, and unknown behaviour when there is a valid reason to immediately lock on zone in?

NB: I definitely don't have any "click yes" type addons which might have clicked the dialog away automagically.

 

Glayde

Usually if you type /raidinfo you can tell if you're locked to a specific instance.

 

xmod2

Working on a Yogg+1 for drakes for our second group. I wasn't saved on zone in, but got saved once I ported down to Yogg's room. This is 10 man, I was the raid leader and I hadn't engaged the boss.

It could be tied to certain watchers being down, perhaps saved me when the watchers loaded. I would prefer that the watchers reset on a soft reset, which would also solve the problem of having an ID with the wrong watchers down on mace attempts.

I wonder if having one of the elders already killed would cause an instant save as well?

 

Demgar

I was given the "Click yes or leave" dialog last night when entering an Ulduar 25 that had been extended from the previous week by the raid leader. All keepers were killed, but still standing upstairs, and Algalon's room was not opened. No one in the raid reported any weirdness, whether they were part of the original instance ID or not.

 

maddfez

Extended a completely empty Ulduar raid ID last night so our resto druid could get her quest item from the room behind IC for her mace (yes, you can do the quests in the 10 man and we were doing 25 Yogg before Steelbreaker). I was not saved immediately but did get the "you are saved" message when she turned in her quest.

 

Rhaegal

To add to the anecdotal weirdness involved with the raid extensions and lockouts, I've been extending an Ulduar10 with Freya up ID on my druid alt for a few weeks, so I can stealth around picking herbs. Since reading through this thread, I paid attention to whether or not I got saved. I extended the lockout while flying up, zoned in, didn't get any sort of message about it being a lockout in progress (though I have in past weeks, not sure about all of them), and I didn't get saved right away. I randomly got saved almost exactly 3 minutes into picking herbs, though it didn't correspond to picking any single node or anything--I was actually stealthed and tabbed out when I got the "You are now saved to this instance." message. So it didn't even correspond to the 60 seconds I normally would have had to zone out if given the option.

Stand back! I'm going to try SCIENCE!

 

Volrath50

To make things even weirder, I had some truly bizzare lock-in behavior with H-ToC. I joined a group that had done the jousting bit while waiting for a tank, zoned in with the Faction Champions standing in front of the door, had the message that I'd entered an instance in progress flash for a second or so, then I was saved. Which was really weird, since you normally don't get saved until the full encounter is done, not just the jousting, making me the only guy saved to the instance, even though I'd just stepped in. :-/

"As surely as I live forever, when I sharpen my flashing sword and my hand grasps it in judgement, I will take vengeance on my adversaries and repay those who hate me."

 

Rhaegal

This isn't terribly important, but I'm curious. In 3.2.2, they added the option, "I am ready. However, I'd like to skip the pageantry." to the NPC in Trial of the Champion when initiating the jousting event. On some of my characters I get both options, and on others, the new option isn't available. I've been asking around to see if I can figure out what the rhyme or reason for this is, and as far as I can tell, the following are true:

- It's not related to whether or not they're a Crusader. I have two characters with Crusader, one has the option and the other doesn't. Moreover, a friend of mine has a character with the option who isn't even a Valiant.
- It's not related to having completed the achievement to kill all the bosses in the instance. Most of my characters have this achievement and not all of them have the option. Moreover, a different guild mate has the option without having completed the achievement even on normal.
- It's not related to Argent Crusade or Sunreavers rep. Again, two characters exalted with both, one has the option, the other doesn't.

What am I missing? I'm sure it's something obvious, but I can't figure out why I can't always access that option when others in the group can.

Stand back! I'm going to try SCIENCE!

 

Duilliath

Are you group leader?

An thenn tehy wuz al ded. Srsly. (Exodus 1)

 

Rhaegal

In the group I was running with prior to posting that yesterday, multiple people in the group said they had both options.

Stand back! I'm going to try SCIENCE!

 

crimsona

I no longer have any level capped toons to test this theory as I have both options now, but I was under the assumption that the first time that particular toon initiates the event, you have to go through the pageantry (the initial 'quest'), and any subsequent runs will give you the option to skip (the 'repeatable quest')

 

ildon

This seems to be the case. The first time I ran it after the patch on my shaman alt, I didn't have the option, and the tank was angry I didn't give him leader because he claimed group leaders could skip the event. It was the first time I had even heard of it being skippable. Next time on my shaman (not as group leader) I did have the option to skip. Then yesterday I did it for the first time since the patch on my priest, was group leader, and did not have the option to skip.

Seems kind of silly to me. They didn't make you sit through Brann's speech in HoS once per character.

 

Scrufola

My Shaman was never in the coliseum, neither normal nor heroic. The first time I run it with him (not group leader) I didn't have the option to skip the event. One person who had the option skipped the event. The next run, I also had the option to skip the event. You don't have to go through the event to get the option to skip the event.

 

ildon

So then maybe it's killing the Black Knight that flags it as skippable, rather than watching the event or clicking the option, but characters were not "back flagged" for having the achievement. Too late for me to test it either way.

 

syrah

Apologies if this has been answered already, I used the search tool but couldn't find anything.

If a guild clears Ulduar to Yogg in week 1 with raid id 'A', then raids Ulduar but does not extend the raid in week 2 (so obtains Ulduar raid id 'B'), would a someone with Ulduar raid id 'A' be able to start a raid in week 3, extend raid id 'A' to the current week and bring everyone back to Yogg?

 

Harwin

We just did something very much like this, so the answer to your question should be yes.

Week 1 - We had a partially cleared Ulduar instance that we're using to get missing hard modes. Call this instance A.
Week 2 - We helped someone, who had an all-but-Yogg cleared instance kill him to get Val'anyr. Call this instance B. An alt extended A and did not come to B.
Week 3 - We zoned back into instance A and killed another boss.

I think that's what you're asking - and we did it, just be careful.