Fix for unintentional instance lockouts in the works

Now if you more or less step in the place, you end up being saved to it.
This can cause a problem if someone in your group forgot that they already ran the instance or raid during the lockout period (a day for heroic instances, a week for all current raids). That person loads an already completed version of the instance. The place has all the trash, all the quirks, except for the bosses. You'll spend a half hour clearing to the first boss, only to discover that he's not there – he's already been killed. And oops, you're saved to the instance too.
"Epic fail," as has been yelled out on my vent when this happens.
And it does happen to the best of us.
But luckily, Ghostcrawler commented today that this is something Blizzard is aware of and they're looking into ways to fix it.
I can hear the cheers from the heroic running crowd now.
Hopefully this is something they'll get out soon. A common suggestion is having a dialog box pop up asking "Are you sure you want to be saved to this instance?" or "This instance already has people saved to it, are you sure you want to continue?"
A solution like that would just be a matter of doing a search of raid IDs amongst the group entering and doing a few other simple comparisons. While I'm sure there are a ton of other considerations to make, the ease at which people seem to be able to come up with ideas to fix this problem is promising that a solution isn't too far off.






Reader Comments (Page 1 of 3)
Ailian Jan 9th 2009 4:37PM
This is EXTREMELY annoying. The other day I got saved to vault 'cause fo this..... yay......
Also: "Ghostcrwaler"? :x
Tonylittle Jan 9th 2009 4:55PM
fo?
Ailian Jan 9th 2009 4:57PM
I c wut I did thar....
scottiedoesknow Jan 9th 2009 4:38PM
Hallelujah!!!
Mattimus Jan 9th 2009 4:39PM
Is that a picture of Deadmines up there?
They need to Heroic up em Deadmines ASAP.
Ailian Jan 9th 2009 4:42PM
I would LOVE to see a Caverns of Time: Elwynn Forest. In where you go back to kill Hogger before he gains his elite status. 40 man raid sounds just about right to take down Hogger. :)
thyrial Jan 9th 2009 4:47PM
Heroic Deadmines should so be a 40 man raid >:D lol
Kiristo Jan 9th 2009 5:16PM
If you really want Heroic DM or Hogger, try a private server. I've seen both, and Heroic SM all in 40-man raid versions. Harder to get a full group, but still doable if it's something you want to experience.
Lemons Jan 9th 2009 6:48PM
They need to do that in a future expansion for serious.
Make a boss that's impossible to kill in the real world but then u go to COT6 or whatevs and kill him the past right b4 he does whatever he did to make him so incredibly powerful, but even then it would be a raid encounter.
That would be shweet!
Oroqen Jan 9th 2009 4:42PM
This happened to my guild this week when heading into Naxx. After ticketing the GM in a 2 hour waiting period ( we downed Vault and OS while waiting) I got the response "this is how it is intended, and if you disagree with the response I can provide you a link to the feedback forums". I knew this couldn't be an "as intended ordeal" and wish GM's would just admit the bug or would simply fix the raid ID's when people spend time and money to play this game.
Spicyness Jan 9th 2009 7:19PM
I had this happen with 10m vault last week. Got locked out by someone in my 25m vault group I theorize. I submitted a ticket and had a GM tell me it was "Working as Intended". Litterally right next to me my girlfriend is talking to a different GM and that GM is telling her that he is sorry, that he can't do anything about it because they can't alter raid ids but that he would pass it up the ladder to someone higher up.
Killer Jan 9th 2009 4:42PM
Didn't it used to be that you had to kill a boss in a raid to be saved to an instance?
I was soloing Gahzranka the other day, as soon as I engaged him the message popped that I was now saved to the instance. Kinda cheesy. Fixit! Blizz
NeoCloud61 Jan 9th 2009 4:42PM
Someone maid a comment in my raid the other night that I found very true.
There's no excuse for "forgetting" that you were saved to an instance/raid. It takes like 2 seconds to check. Heck Blizzard's new calendar tells you when your instance/raids unlock.
When the game remembers for you, it's your own fault for not checking.
That said, I agree that getting saved because of someone else screwing up is annoying and I'm glad a fix is on the way.
Muse Jan 9th 2009 9:17PM
Agreed. And take that extra second to look at the raid instance portal. Does it or does it not have a skull on it?
SnippyMcPhail Jan 9th 2009 4:42PM
It can happen on accident to.... say your group is going to Heroic Naxx and the leader forgets to switch to heroic.... he ran regular already earlier in the week... BOOM you're saved to a cleared regular version.... WOOPS
AyaJulia Jan 9th 2009 4:43PM
My favorite part was where you linked to a forum post that we can't read (yet). :)
But yeah, this is obnoxious. Our guild got saved to Vault Wednesday, and none of us has any idea how; no one went in this week, all the trash was up, and the boss was dead. GM said they're working on it, but they won't reset our raid ids. :( Glad to hear they're going to do SOMEthing.
Vindalla Jan 9th 2009 4:48PM
No... someone in your raid ran it, forgot about it, and is too cowardly to own up to it.
AyaJulia Jan 9th 2009 4:53PM
No, our guildies have all been long-time friends and spend a ton of time together, and multiple people are always on and doing things together. We'd have known if anyone ran the thing in the last day.
smcn Jan 9th 2009 5:43PM
Someone probably zoned in while in a raid for WG itself and got saved without realizing.
As stupid as it is that there isn't a dialog (yet), it's not going to just randomly save you.
NoTomorrow Jan 9th 2009 4:44PM
How about for nostalgia's sake, they make heroics of all old instances? Heroic RFC, SFK (my personal favorate), ST, ZF, etc.
It would be awesome.