Bugged Instance Gates?

User Chris McDonnald sent us a tip about an issue with a gate in the Mechanar instance in Tempest Keep, Netherstorm. It seems that the gate pictured here has an annoying tendency to lock closed if your party wipes on the final boss. It's been confirmed by Drysc as a known bug here, where Drysc goes on to say that it's not intended, however it requires a client side patch that most likely won't be included in 2.0.7.
Blizzard seems to have a bad track record with implementing gates in dungeons. Anyone remember the door to Baron Rivendare on the undead side of Stratholme? Or the gate right before the Razorgore encounter, just inside the instance in Blackwing Lair, which originally would only reset 2 hours after a wipe? Or the door to Vaelastrasz in Blackwing Lair shortly after it was released, which would jam shut in certain circumstances? Or the gates in the Rend encounter in Upper Blackrock Spire? That's the list I came up with off the top of my head. Why do they need to put these gates in, and why can't they check what's obviously been a problem area in the past (well, except for the Razorgore encounter, which was an intended reset time but someone changed their intention later).
So, a word of warning. Make sure you have a Shaman have an Ankh up, a Warlock have a soulstone up, and a Paladin use Divine Intervention as required, because if your party wipes here, you either get to put in a ticket in order to be transported through or re-clear the dungeon.
Filed under: Instances, The Burning Crusade, Bugs






Reader Comments (Page 1 of 1)
Poddo Feb 12th 2007 8:53PM
I'm never one to be a real "blizzard hater," but isn't this a tad rediculous? How long was BC in beta for? And even if it wasn't an issue in beta and was maybe introduced over the smaller patches, 2.0.5 or something, its not intended to be fixed in 2.0.7??? If this was my game, I would have people on top of this immediately. I mean, its practicly a game breaker. A group of 25 people finally get organized, and clear all the trash in the dungeon, and wipe. And now they're screwed? I'd say: "all hands on deck, lets get that thing fixed and pushed out tomorrow morning." But thats just me I guess..
Baluki Feb 12th 2007 8:55PM
Oooh, I remember when I tried to do the quest for my epic shaman helm in Scholo, if you wiped, the gate would close and you couldn't try it again. That sucked.
And then there's the gate at the end of AQ40 that has never even been implemented. Next to C'thun's room, there's the room with the 3 imprisoned dragons, and a stairway going up to a wall that would let you out right near the other (non-imprisoned) dragons. I imagine that the wall would have opened up once you killed C'thun, or maybe once you killed the Twin Emperors, to give you easy access to C'thun. But they added the teleport to the Twemps room instead.
wowinsider.qsh Feb 12th 2007 9:47PM
Well the intent is obviously to put some space restraints on certain fights, as well as prevent access under certain conditions such as "death-zerging" some bosses when the graveyard is nearby. Unfortunately they can't ever seem to get a gate right on the first try eh?
Monigote Feb 12th 2007 10:04PM
Not that I don't agree with your complaints... but I must say everyone seems to think that all the code that goes into these games is easy? Their bound to make mistakes and with a whole 8 million players doing weird random things in infinite possible ways and infinite combinations of classes/items/gear... There are bound to be a FEW things that don't work...
Prauche Feb 12th 2007 10:17PM
Same SH**, different gate....
Dixonij Feb 12th 2007 10:19PM
@Monigote
I don't doubt that there bound to be smaller things wrong but to have a major instance gate not work... and in content that was put through the beta test like it was... That deserves an immediate look by Bliz to appease your devoted customers.
Tyler Feb 12th 2007 11:00PM
How do you stump a roomfull of blizzard programmers?
Tell them to build a working gate.
Luclan Feb 12th 2007 11:03PM
First off, dont forget the kel thuzad no show that many guilds experienced during the whole naxx race.
A thought occured just now. Blizzard has been looking for ways to slow guilds from beating instances so quickly. They want them to last longer so they dont have bored high end guilds sitting around just waiting to beat the next. Is it possible that *forgive my stupidity* Illidans instance, be accessable only a few times a week? or one time a week? in an attempt to slow us?
I could totally see blizzard saying illidan challenges everyone to the ultimate challenge.......... but you can only have 1 wipe each week. that would blow.
Max Feb 13th 2007 1:41AM
Last nite i was in Mechanar with some friends and unfortunatley we had no rezzer (no pala, no priest, no shaman) cause our healer was a druid....
This forced us to run everytime and we had the gate locked for us....
we had a warlock tho and we gound a workaround to go over that gate....
Soulstone the warlock himself and he can summon ppl through the closed gate. the others just have to go in front of the gate and assist the summon through the gate.....
It worked!!
YonksMan Feb 13th 2007 2:16AM
I've been in (2) different groups in last day or 2 in Steamvaults. We have not been able to use the access control panels to get to the end boss.
I know that this wasn't a problem a week ago (maybe before patch 2.0.6) ... is anyone else having this problem?
Druid dude Feb 13th 2007 12:12PM
Last night, Mechanar. Semi-pug run a friend invited me to them left before we started. With the tank shortage on our server, I figured I wouldn't hang these guys out to dry so stayed in the group.
We started, and it was... not optimal... They weren't horrible, but not great either. And slow. Very very slow. Long waits between pulls for... I have no clue what. After what felt like about 3 weeks, we finally started the last boss. And wiped.
I was so happy when the gate bugged.
Thanks Blizzard! Much love!
Twinny Feb 13th 2007 5:08AM
@9
or just soulstone the priest and get them to res?
Zuuler Feb 13th 2007 7:33AM
@4
Take it from someone who works with code all day, it shouldn't be that hard to program a gate that opens on one condition, and closes on another condition.
Just like it shouldn't be hard to increase the looting distance of all players but not make the looting distance on horde rogues 40 yards.
Just like it shouldn't be hard to fix any bug that shows up within the game. Like that one quest in the bone wastes, the one where if someone fails the quest, no one else can do the quest until the server restarts. Or my personal favorite, we messed up and overpowered the imp so we're going to take all his bonus spell damage away and fix it in some patch, but we won't say what patch.
Which brings up a question. Anyone know if 2.0.7 is going live today or not? I'd like to know so I can start waiting for hours for the download.
bryl Feb 13th 2007 7:35AM
Blue post on the subject :
Sorry about this. This has been hotfixed now however, so the door at the top of the elevator in the Tempest Keep Mechanar should now properly open if players die to Pathaleon the Calculator.
http://forums.wow-europe.com/thread.html?topicId=123382494&sid=1&pageNo=2
multikast Feb 13th 2007 8:44AM
@11
you didn't read. he said they didn't have a priest.
@1
they don't have it planned for 2.0.7 because that was released today. they would not have had time to get it in 2.0.7 and get the other fixes out today. i suspect there may be a 2.0.8 in the near future though.
James Feb 13th 2007 11:31AM
Hehe, I'm the warrior in the group, you can see my garish orange boots on the middle right-hand side of the picture.
Uh, we got a little bored while waiting for the ticket so we all started popping the Spirit Totems and Archmage staff summons. lol
Halicante Feb 13th 2007 1:32PM
@10 This happened to a friend of mine's group. They found a workaround by having someone log off then on again. That person could then use the control panels.
For the mechanar gate, it doesn't bug if no one releases until all the npcs have reset...although it sounds like they've fixed the problem (pffft right), so that will be nice.
Belacroix Feb 13th 2007 1:56PM
Yeah, I've actually heard a workaround is logging out, emptying cache, and logging back in. Haven't tried it yet, but that what this grape has heard.