Maldura x2 raid zone BROKEN

11-09-2015, 04:28 AM

Really?? 62 million auto attacks in a "reasonably PUGable" zone?? In the first 5 seconds of the Grinder VIII fight we had 4 adds up, and continuously spawning and a ridiculously high rate, increasing all damage everyone was taking. When I was getting hit for 60m+ I had only 4 increments on me. This is clearly not doable by any means.

Gelenor · 11-09-2015, 07:26 AM

Your not showing in eq2u so its hard to now how you are geared. But given the opening solo quests provide upgrades in gear for even AoM raiders and the x2 even has an access quest series that takes you through a new heroic first, I doubt the x2 is intended to be first target in expansion for pugs.

But it is very doable and been killed by many. From our little grab in beta of whoever wants to come.. we wiped first try. So we adjusted to start with the adds and got them down ASAP and then took advantage of the small breaks in between the next spawn cycle to work on named. Once you have the add re-spawn starting again, repeat and bring them down immediately.

In the 59 seconds you had in that fight you should have been able to kill the first 4 adds, and be onto the each of the new spawns as they popped. If you left the adds up in that 59 seconds and just stayed on the named, I can see how nasty it would have been.

11-09-2015, 11:43 AM

Clearly weren't doing it right.

11-09-2015, 10:47 PM

The zone is fine. You may need higher resists, mitigation and/or block chance.

11-09-2015, 10:51 PM

Yeh I like it, it's not quite tank and spank but yet its not overly difficult either.

Anunnaki · 11-09-2015, 11:00 PM

I don't even remember which named that is since the zone was so easy no named stick out to me. This is the definition of a PuG zone.

11-09-2015, 11:00 PM

The numbers tell the story... this was our zerker on the same fight 2 days ago.

[IMG]

Anunnaki · 11-09-2015, 11:11 PM

This is with our Monk. Don't know what to tell you.
[IMG]

Marq · 11-10-2015, 06:10 AM

Could just tell your dps to actually kill the adds (the stacks off them are timed from pop), if you have a lot of single target dps, you will get a ton of adds very fast with nothing dying and it will be impossible to tell which add was the first to pop. Had similar issues with it until ppl actually started swapping to adds and it went down very easy then. Like say Assassin hitting a full FFU chain on mob would prolly pop 3-4 adds near simultanous.

Full burn tank & spank works on very few mobs now it seems.

11-13-2015, 01:56 AM

To clarify this was shortly after a patch to buff up the zone due to people clearing it so easily without the resist buff and such. Roughly a one hour post patch run. We had plenty of dps, adds were dying within 1-3 seconds, but they were spawning faster than that. My resists were 214k each, and 31k mitigation. I had cleared it multiple times previously but they clearly did something during a patch that got fixed post run through for the shown raid.

11-09-2015, 07:26 AM	#2
Gelenor Member Join Date: Jan 1970 Posts: 0	Vondis said: ↑ “This is clearly not doable by any means.” Your not showing in eq2u so its hard to now how you are geared. But given the opening solo quests provide upgrades in gear for even AoM raiders and the x2 even has an access quest series that takes you through a new heroic first, I doubt the x2 is intended to be first target in expansion for pugs. But it is very doable and been killed by many. From our little grab in beta of whoever wants to come.. we wiped first try. So we adjusted to start with the adds and got them down ASAP and then took advantage of the small breaks in between the next spawn cycle to work on named. Once you have the add re-spawn starting again, repeat and bring them down immediately. In the 59 seconds you had in that fight you should have been able to kill the first 4 adds, and be onto the each of the new spawns as they popped. If you left the adds up in that 59 seconds and just stayed on the named, I can see how nasty it would have been.

11-09-2015, 11:43 AM	#3
Rondo9 Active Member Posts: n/a	Vondis said: ↑ “This is clearly not doable by any means.” Clearly weren't doing it right.

11-09-2015, 04:28 AM	#1
Vondis New Member Posts: n/a	Really?? 62 million auto attacks in a "reasonably PUGable" zone?? In the first 5 seconds of the Grinder VIII fight we had 4 adds up, and continuously spawning and a ridiculously high rate, increasing all damage everyone was taking. When I was getting hit for 60m+ I had only 4 increments on me. This is clearly not doable by any means.

11-09-2015, 10:47 PM	#4
ZUES Well-Known Member Posts: n/a	The zone is fine. You may need higher resists, mitigation and/or block chance.

11-09-2015, 10:51 PM	#5
Rondo9 Active Member Posts: n/a	Yeh I like it, it's not quite tank and spank but yet its not overly difficult either.

11-09-2015, 11:00 PM	#6
Anunnaki Member Join Date: Jan 1970 Posts: 1	I don't even remember which named that is since the zone was so easy no named stick out to me. This is the definition of a PuG zone.

11-09-2015, 11:11 PM	#8
Anunnaki Member Join Date: Jan 1970 Posts: 1	This is with our Monk. Don't know what to tell you.

11-10-2015, 06:10 AM	#9
Marq New Member Join Date: Jan 1970 Posts: 0	Could just tell your dps to actually kill the adds (the stacks off them are timed from pop), if you have a lot of single target dps, you will get a ton of adds very fast with nothing dying and it will be impossible to tell which add was the first to pop. Had similar issues with it until ppl actually started swapping to adds and it went down very easy then. Like say Assassin hitting a full FFU chain on mob would prolly pop 3-4 adds near simultanous. Full burn tank & spank works on very few mobs now it seems.

11-13-2015, 01:56 AM	#10
Vondis New Member Posts: n/a	To clarify this was shortly after a patch to buff up the zone due to people clearing it so easily without the resist buff and such. Roughly a one hour post patch run. We had plenty of dps, adds were dying within 1-3 seconds, but they were spawning faster than that. My resists were 214k each, and 31k mitigation. I had cleared it multiple times previously but they clearly did something during a patch that got fixed post run through for the shown raid.