Fix the doors in Kraytoc's Fortress of Rime x4

Reahov wrote:

we did eireen last night and she is fixed. thanks for getting that one done so quickly. it does sound like people are still having problems with the doors though.

Again with the locked doors!!! Third wipe of Kreegar and doors locked... After the the last of the mass healer rezzes after total wipes hour later or so.... Doors unlocked...

My solution...

Move the revive point to the intersection after 2nd name kill!!!

The nefarious locking doors have returned. We wiped once on Kreegar, and found that both sets of doors on Brendegor's room were locked. After we got Kreegar down and Taaltak down, the door unlocked again. If you guys can't get the doors to work correctly, then perhaps consider moving the revive point to the four-way intersection once you've killed Tert Turganpuncher. Thanks.

Friggen doors still broke. I think its time to go, they just don't care anymore,

Bet the locking doors is related to the bug with COV where you will forever be "in combat" if you wipe at all during a zone.

We are still investigating. The more detailed information we have, the easier it will be to track down. We would also like to try and set up some raids, if possible, on the Test Copy server to accompany you.
Send me or Sinhuree a PM for times that might work for you and we try and get one scheduled. Thanks!

Confirming that this is still happening as of last night (3/24). Wiped to Kreeger in a fresh instance. Doors locked.

We always wait for a healer to have thier rez from death aa up, we no longer even bother checking doors anymore.
Also we are always stuck in combat after we kill kraytoc, if we leave the pillars up at the end.
So can't call home, until we are either evac'd or camp out.

2 or 3 pulls end of raid night... then came back next day... doors locked.... again

Khatiru@Butcherblock wrote:

Hi Khatiru,
Could you be a little more specific? Which doors? What was your last pull?
Thanks,

Kraytoc still bugs if you partially kill the pillars, then kill the named (ez-mode).

My guild got up to kreeger, made 2 pulls wiped, ended the raid night with intent to go in next day to take him down since we got him into the 20% range... When we came in to start the next day, the front doors were locked...

Any way you guys can put a transporter that takes you to the first intersection once Tert is killed?

Khatiru@Butcherblock wrote:

Sorry, I was thinking of the wrong instance. NM

Khatiru@Butcherblock wrote:

Looks like we found the issue and it should be getting hotfixed asap.

how about the floor that kills you when you run across it? same problem as with roen theers bridge last expac, been reported in beta, still happens.

Lader wrote:

It's the ramp leading up from the docks to the 4way.

The doors in Kraytoc's x4 are STILL broken. We started a fresh instance tonight, and when we got to Kreegar, the mob bugged out (see below) and we had to choose to lay the fight down, or evac. We evac'd, and found that the first set of doors in the zone were, as usual, locked. Please, for the love of God, FIX THE DOORS! The issues w/ this zone are getting really old.

Now, as for the bug: We've had this happen a couple of times now. Every so often, a dumbfire pet will /yell for help and break the encounter. It doesn't seem to matter if yell access is set to Leader Only. We've had this happen with the paladin mythical pet, and brigand Band of Thugs. We also had the same thing happen on one of the contested x4's in The Hole w/ a templar's hammer. It's therefore not a zone issue, and it needs to be fixed.

Elhonas@Antonia Bayle wrote:

We've seen this happen a few times, too -- even the shaman spirit wolf can do it. But we've never had it break Kreegar tho, just one of his adds, so it hasn't caused any real issues for us so far (tho it does kinda throw people off when it happens hehe!).
For the doors.... Gninja, is it a necessary mechanic for the doors to lock, btw? Could the locking be removed without adversely affecting any of the encounters? Unless the locking is tied into something I'm overlooking, it seems like it would be simpler to just remove them as a variable if they continue to bug out.