NEED immediate GM help!

#0 - July 12, 2010, 8:06 p.m.
Blizzard Post
Need immediate GM help please :/

Sunwell Gate (the 4th) is once again up, for the fourth week in a row.

Just don't want to wait 4 weeks for something that can take 30 seconds to fix ><

It just keeps happening.


Very VERY annoying.

Don't want it to reset tomorrow and be screwed over a week by a bug in the mechanics.


the Raid ID is: 4530035 STAGHELM horde
#7 - July 12, 2010, 11:01 p.m.
Blizzard Post
Sorry for the delay, Andromath. The issue should be resolved on Staghelm.

If you or anyone in your group has been inside the instance in the last 30 minutes you'll need to perform a soft reset for our change to take effect.

To perform a soft reset, follow these steps:

-Have the entire party/raid exit the instance.
(Please note that players who remain inside the instance, even those who are logged out, will prevent this workaround from functioning as it should)
-Wait at least 30 minutes while every raid member remains outside of the instance.
-Re-enter the instance only after 30 minutes have elapsed.

When you re-enter the instance after completing the soft reset, all scripted events that your raid has not yet completed should now be reset and you should be able to continue raiding where you left off.

#9 - July 12, 2010, 11:55 p.m.
Blizzard Post
Q u o t e:
Is there something players are doing unintentionally that causes this? Is it related to DPS being too high for the instance? Maybe being high enough lvl to walk by some mob packs without aggroing them, when the instance was designed to be completed by lvl 70's that wouldn't have been able to avoid them? Is it something like this that is breaking the scripting?


Not that I'm aware of, Mogrigg. These script events are fairly complex, which is why we are normally not able to interfere with them. Though in this case we have a command that we can issue that resolves the gate issue for the realm. Unfortunately the gate has a chance to remain closed if the realm is reset, which usually happens with maintenance. From what I have found our Developers implemented a resolution to the issue around 3.3.3 but it wasn't as lasting as they would have liked so they are looking into a better resolution.