This site makes extensive use of JavaScript.
Please enable JavaScript in your browser.
Live
PTR
10.2.7
PTR
10.2.6
Beta
Extended Raid Lockouts and Resets...
Post Reply
Return to board index
Post by
Rayner
Ok, so my guilds raid leader brought something up and I want to make sure it pans out.
say we kill 6/12 bosses In icc10... we call it a Night and extend the lockout...
We come back on Wednesday and try the next boss, but never get close to downing him/her.
Would we then be able to remove the Extended lockout and start a fresh raid?
or would we all get saved?
Post by
Toldu
You'd be saved
Guess I've been corrected.
Post by
Yall
You can drop the extended lockout off...
My guild was at 11/12, but didn't get any tries on the LK that week. Next week, we tried the LK and failed a whole week, at the end 9 of us decided to do ICC10 normal (keeping 1 with a 11/12 save, for further LK tries the week after that)
As long as you don't down anything new, you're not getting saved.
Post by
Bruunpala
Only the one who extends the lock out in the first place, will be saved.
Post by
239153
This post was from a user who has deleted their account.
Post by
Yall
Ok, so my guilds raid leader brought something up and I want to make sure it pans out.
say we kill 6/12 bosses In icc10... we call it a Night and extend the lockout...
We come back on Wednesday and try the next boss, but never get close to downing him/her.
Would we then be able to remove the Extended lockout and start a fresh raid?
or would we all get saved?
Only the raidleader needs to extend. My guild's 10man was stuck on Lich King for about 3 weeks. What we would do, is the raidleader would extend the lockout, and zone in. Then, the rest of us could simply zone in to the extended lockout instance. We wouldnt see any save notification or anything like that, and didnt need to extend the lockout ourselves. We would only get saved if we downed a boss. So on the weeks where we didnt manage to down Lich King, the rest of us were still free to pug a fresh run for badges. I
believe
that our raidleader would get saved being the one who extended it, but for us that wasnt a problem as she couldnt raid later in the week anyway.
Nop, even the raidleader doesn't get saved. As I said above, we could just take the extended lockout off. (I was the one extending, so I know 100% sure)
Post by
203406
This post was from a user who has deleted their account.
Post by
141313
This post was from a user who has deleted their account.
Post by
203406
This post was from a user who has deleted their account.
Post by
Bruunpala
Ok, so my guilds raid leader brought something up and I want to make sure it pans out.
say we kill 6/12 bosses In icc10... we call it a Night and extend the lockout...
We come back on Wednesday and try the next boss, but never get close to downing him/her.
Would we then be able to remove the Extended lockout and start a fresh raid?
or would we all get saved?
Only the raidleader needs to extend. My guild's 10man was stuck on Lich King for about 3 weeks. What we would do, is the raidleader would extend the lockout, and zone in. Then, the rest of us could simply zone in to the extended lockout instance. We wouldnt see any save notification or anything like that, and didnt need to extend the lockout ourselves. We would only get saved if we downed a boss. So on the weeks where we didnt manage to down Lich King, the rest of us were still free to pug a fresh run for badges. I
believe
that our raidleader would get saved being the one who extended it, but for us that wasnt a problem as she couldnt raid later in the week anyway.
Nop, even the raidleader doesn't get saved. As I said above, we could just take the extended lockout off. (I was the one extending, so I know 100% sure)
I believe if he had gotten saved to a new Icc10, you wouldnt be able to continue on LK the following week, wich then would lead to the problem.
I think the way it works is that the game saves your last used/saved to dungeon's ID for the extend... hell i haven't done Naxx10 in a long time but it still shows among my raid IDs.
Captcha says: "Ikkay" ?
Post by
487010
This post was from a user who has deleted their account.
Post by
Porcell
Note that hardmode attempts will trigger a save. Example from this past week, we had downed all of the 10 man Hardmodes except for Sindagosa and LK. We extended and went in, no one gets a save message. We burn an attempt on Sindagosa, and after the wipe runback we all got "Zone out or be saved" dialog boxes.
Otherwise, no one should be getting saved to an extended raid until you either down a boss or use up a Hardmode attempt off the counter. Even the raid leader who extended can always zone out, go to their Raid Lockout window, and select "Unextend" and still be clean.
Post by
Davidson
There is a lot of misinformation in this thread.
If you extend the lockout, this is what will happen.
On Tuesday, everything resets.
However, the raid leader's raid will not reset.
He can zone in first and then everyone else follows.
You will not be saved to this raid until a new boss is killed.
If you guys fail on killing anything, you can zone out.
The raid leader can then unextend his lockout.
You then zone back in to a brand new raid.
Post by
Bruunpala
The thing about extending is that you can keep trying to down new bosses, so it doesnt matter that the RL will unextend it... the raid would then have to clear everything again, wich ofc gives loot and such, and isnt a bad idea if you can do it in a day or 2. But when my guild was doing the last 2 bosses before lich king we had Putri and Sindy up, cuz they werent guarenteed kills. We then spend 1 week on PP and Sindy and would extend again for LK. Now the next week could look like this:
We go in and wipe all 7 days on LK and decides to go for a fresh run, tuesday night (I am on EU servers), and the Raid Leader "Un-Extends" his lockout and gets saved for this 9/12 clear. We then extends for the week after to find Sindy and PP waiting for us = we "waste" a week of clearing them 1 week ago.
Now if the RL didnt "Un-Extend" we can take another person who: needs loot, needs emblems, is the RL's Alt, basicly anything to fill the last spot. The RL then still has the 11/12 save and can extend for the 2nd time granting the raid another 6-7 days to kill LK.
Imo, "Un-Extending" is a bad thing unless you are sure you can clear the bosses you allready downed once, in a day or so, and then you would'nt really needed to extend in the first place making it all useless.
Therefore... Dont extend unless you are serious + knows wtf you are doing. Fact!
Now, may you all have a nice evening cuz I'm supposed to show up for a raid in less then 1hour, and I'm pretty darn hungry.
Post by
DaCyclops
My guild decided to let me tag along to ICC10 as DPS for their first 4 bosses to help me get badges one week. It was nice, got a few. Next week, they extend, I do another ICC10 group. Week after that, they ask if I want to join in an attempt on the Lich King on the Wednesday. I walk in, and whack him a few times. We fail a few times. Bit later in that week, I join another ICC10 group that was saved to the first two bosses. Moment I zone in, it asks me if I am okay with being saved.
I participated in the same Raid ID twice, with a week's gap, and didnt get saved the second time, because we didnt down a boss. Yet was asked the moment I entered a new ID.
taking Davidson's text... I believe it is more accurately the following.
On Tuesday, All Raid ID's are reset to Inactive. Any new Raid ID created are to be considered "reset" at 0 bosses for this example.
The Raid Leader can opt to Extend his Raid ID's from the past week from his "last raids done" list. He can then zone in first and then everyone else that follows will enter the extended Raid ID.
When you enter an Extended Raid ID, your character is checked for on the Raid ID's list. If it is not there, it will prompt you to accept being saved right away.
If any bosses have already been killed since the last reset, it will prompt you to accept being saved right away.
If any bosses are killed while you are in there it will save you.
Being 'saved' is the process of WoW writing your character onto the Raid ID, and the Raid ID onto your "last raids done" list
The raid leader can choose to un-extend his Raid ID as long as no bosses have been killed since the last reset. This will just set it back to inactive like the weekly reset does.
I would believe the same info would apply to heroics and the 3-day lockout raids, just replace "Tuesday" with "every day" or "every third day".
Post by
Porcell
On Tuesday, All Raid ID's are reset to Inactive. Any new Raid ID created are to be considered "reset" at 0 bosses for this example.
The Raid Leader can opt to Extend his Raid ID's from the past week from his "last raids done" list. He can then zone in first and then everyone else that follows will enter the extended Raid ID.
When you enter an Extended Raid ID, your character is checked for on the Raid ID's list. If it is not there, it will prompt you to accept being saved right away.
If any bosses have already been killed since the last reset, it will prompt you to accept being saved right away.
If any bosses are killed while you are in there it will save you.
Being 'saved' is the process of WoW writing your character onto the Raid ID, and the Raid ID onto your "last raids done" list
The raid leader can choose to un-extend his Raid ID as long as no bosses have been killed since the last reset. This will just set it back to inactive like the weekly reset does.
When you enter an Extended Raid ID, your character is checked for on the Raid ID's list. If it is not there, it will prompt you to accept being saved right away.
That is the only line that isn't true. Anyone can enter an extended raid. They will not be saved until a boss is downed or a heroic attempt counter is consumed.
Like you said here: "Week after that, they ask if I want to join in an attempt on the Lich King on the Wednesday. I walk in, and whack him a few times. We fail a few times. Bit later in that week, I join another ICC10 group that was saved to the first two bosses. Moment I zone in, it asks me if I am okay with being saved."
It didn't matter that you were already "saved" to that raid ID from the previous week. Replace yourself with any random person and they wouldn't have been saved either. We've extended for Lich King before, brought in a Boomkin (Who was not with us for the previous week's clear) for 15 attempts and didn't down Lich King. The next day the Boomkin was able to join a different fresh 10 man ICC.
The bottom line is that if a raid is "Extended," NO ONE will be saved to that instance until a boss is downed or a heroic attempt is used. It doesn't matter who the person is, whether they were in on the original raid or not, or someone just fresh out of trade chat.
I guess I should note that if I extend a raid that has, for example, Sindragosa and Lich King active, and then raid kills Sindragosa, that is now an "active" raid ID. If someone were to drop group and you picked up a fresh person, that fresh person would be saved to that raid ID instantly. Even though it was extended, it became "real" once that boss was downed, even though the fresh person wasn't in the raid when it occured.
Post Reply
You are not logged in. Please
log in
to post a reply or
register
if you don't already have an account.