Gluth devistate right off the bat

Apparation · 11/05/06, 12:20 PM

Just wondering if anyone else has experienced this. We've had it happen to us twice and are wondering if theres something we can do or not do to avoid it. What happens is we're all running down the hall. The MT1 is just ahead of the raid, he gets to the point where is is JUST about to jump down (not out the tunnel yet), and then gluth proceeds to devistate the raid and laugh at us when we have 5% hp and jump out of the tunnel to our deaths.

It was quite humorous the 1st time. The 2nd time was less funny as it takes us awhile to get everyone through the frogger trap of hell ( /sigh) and buff up.

Quixotic · 11/05/06, 12:28 PM

It's happened to us when the chow didnt despawn properly as the encounter reset. If the chow spawn timer spawns one as he is running back to his reset position he chow will remain up and the decimate timer apparently keeps ticking until you engage and he insta-decimates you.

We had a hunter or two feign and come back up when everyone else died to make sure he didnt spawn another chow.

Rane · 11/05/06, 12:31 PM

Yea, that means the fight didn't properly reset and 1 or 2 zombies are still up. Send a willing victim down the pipe to reset it :)

Insta-decimates make for pretty corpse-waterfalls tho!

♦ Praetorian · 11/05/06, 12:32 PM

1) It's devastate, not devistate.
2) It's decimate, not devastate.

He does it when he didn't fully reset, perhaps because someone zoned back in mid-wipe (and a Gluth wipe can take quite a long time since all he can do is run around and eat people one at a time), such that he's been sitting there ready to Decimate the whole time. Make sure he resets fully and all zombies despawn before anyone zones back in.

Digo · 11/05/06, 1:21 PM

That doesn't quite make sense, since decimate happens when N number of zombies are currently up. It's not on a timer, contrary to what many believe. You can test this by intentionally having him each a bunch of zombies on the engage, then decimate will come much later than the usual, mod-predicted timer of 1:40 or whatever.

• Hamlet · 11/05/06, 1:28 PM

Originally Posted by Digo

That doesn't quite make sense, since decimate happens when N number of zombies are currently up.

Ahh, good call. I always knew the delay was there, but this reasoning somehow makes it seem cooler.

Incidentally, does that mean the required number is a multiple of 3? The delay seems to occur when he gets only one. Have you actually confirmed that the delay is the same if he eats 2 or 3?

---

By the way, how does Decimate affects the Zombie spawning timer? I'm always too busy AoE'ing. In my Gluth RDX bossmod, I put in a timer for first spawns after aggro, just to help the kiting Priests get started. Would be nice to do the same thing after Decimate, when we swap in a new Priest, who doesn't want to be pathing rigtht past the grates when a new set appears. Is it "10 seconds after Decimate?"

• Fogbug · 11/05/06, 1:32 PM

Originally Posted by Digo

That doesn't quite make sense, since decimate happens when N number of zombies are currently up. It's not on a timer, contrary to what many believe. You can test this by intentionally having him each a bunch of zombies on the engage, then decimate will come much later than the usual, mod-predicted timer of 1:40 or whatever.

huh, I never thought of it that way. That makes sense, even if it doesn't explain surprise decimate

Quigon · 11/05/06, 1:58 PM

Back when this encounter was still extremely buggy (read: first week of july to third week) - and well before the mobs despawned... the encounter would often not reset properly. Maybe it reset more for you guys - but for us 50% of the time it would bug out on wipe. So what basically happened was the mobs would be running back to despawn on their grate, and either the timing would coincide poorly with gluth's reset or a new spawn would occur.

But for us almost half the time the encounter would bug. Our solution was to have a hunter feign death (and still is today for reasons above... we know they dont always fix things). Once a wipe happens, we'll have the hunter stand up, and that always properly resets the fight.

When it is bugged like this, you will be decimated the second you fall out of the tube. He is still "primed" and his cooldown has hit 0 - once he's in combat he uses the ability. We've seen this before, and this is our explanation - its possible he was still in combat with someone, but they made it so you can't zone in mid-combat now, and I think you'd notice something like that :)

• Hamlet · 11/05/06, 2:02 PM

Originally Posted by Quigon

but they made it so you can't zone in mid-combat now

Huh?

Quigon · 11/05/06, 2:06 PM

Originally Posted by Arawethion

Originally Posted by Quigon

but they made it so you can't zone in mid-combat now

Huh?

You cannot zone into an instance that is in combat with a boss... its in the patch notes.
Only way this happens is with a bad reset.

#
# Instituted an anti-exploit measure on certain encounters (almost entirely raid bosses). These encounters will prevent people from zoning into the instance while that encounter is engaged. If you attempt to zone into the instance while that encounter is engaged, you will be resurrected at the outside entrance. We will be making adjustments to the entrances to Molten Core and Blackwing Lair to accommodate this change. Combat resurrections, soulstones, reincarnate, etc. will still work fine. This is primarily to combat graveyard rushing in instances.

This incidently happened the 2nd week of July.

If you need elaboration - we were working on Gluth before this patch:

If we zoned in when he was still eating we'd all be in combats still - after the patch, it puts us in EPL.

The bugs we experienced were all from chow being up - chow up = insta-decimate by the time you buff and get there. Theres no zonewide combat pulse when it doesn't reset - his health resets, and no one will notice its bugged unless you /tar, or watch the wipe.
Its a bad encounter reset on the adds... its way less frequent now though. We could repeat this bug readily.

• Hamlet · 11/05/06, 2:18 PM

I guess we've always been do good about not having people zone in at bad times that I honestly even noticed.

If only that were around during the days when the pre-Fankriss trash could bug out horribly and cause a giant mess with your instance.

Does this apply to the Heigan trash?

Quigon · 11/05/06, 2:22 PM

Well zoning in mid-combat with trash is fine, bosses is another matter, they pulse zonewide combat ticks now... I'm not sure if Heigan trash is zonewide (or I'm not thinking straight). Regardless, you CAN zone in during heigan trash, but not during Heigan. As for them bugging out - I don't know... I do know, as probably most people do... if someone comes back online in heigans trash room while you are fighting heigan - every single last mob in the path of that player to you will be chained down on your raid - probably wiping you. So yeah, I'd say that sounds like zonewide combat pulses - but you can still zone in. Meaning theres two types of zonewide combat I guess.

People will simply appear like they zoned in normally, just in EPL - and thats why msot people don't notice it unless they're actually looking for that (it bugs the shit out of me when people zone in early personally - if they get ganked its just wasted time). You'll see it on sapph cause of long phase 2 wipes and such.

Digo · 11/05/06, 2:35 PM

You can actually train Heigan trash to the zone in. Don't ask me how it happened.

We have a couple special kids who got out of their cages.

TL-Seria · 11/05/06, 2:45 PM

If you could train heigan to the zone in, that would be great.

Mosh · 11/05/06, 3:55 PM

We trained Loatheb to Grob's room.