Official PVE Progression Thread

[Envy]

you understand this puts a dangerous precedent regarding azuregos down the line? if more and more guilds decide to wait by the line until azu is low, by the end there wont be any guild engaging azuregos and everyone will just idle around until either enough people leave, or they get bored and go do something else.

A dangerous precedent? Really? If one wants to do that, he will, getting a silly cross is of no importance in the end, the only thing people want is to loot the corpse.
Now that everyone is either mad or simply jealous, we might want to talk about something way more important. The fact that Azuregos (and every other outside mob for that matter) doesn't regen its HP while on the way back to its spawn but once he's back in place. Making it easy to tag a mob low on HP.
This bug (because you all know that it's a bug) is actually the only reason such things are possible.

Such things:
- For a guild of the same faction to actually make a mob reset (the way it's working at the moment is wrong, you can't just take the aggro of a mob & then make it reset for everyone, this is ridiculous.) As long as someone is in the aggro list, it shouldn't ever happen.
- For anyone to simply profit from the fact that a boss/mob doesn't regen while going back in his place but rather when he's reached it. And this problem is the only reason why we kill the poor fellow so easily, despite being so many of both factions. We can just 'steal' it whenever we want (and I'll remind you that, that's exactly what you did at the beginning of the fight, so don't try to play the victims here.)

These bugs should be fixed ASAP.
And they're the only reason why we can't have proper fun on worldbosses as of now. And, yeah, anyone that actually played on retail (not feenix, not E.D.) knows that what I'm saying is true.
Think about this before blaming others for doing exactly what you tried to do five minutes earlier (and failed to do.)

I hope this gets fixed quickly, it'll bring back some fun in doing outdoor bosses...

[Momoh]

^ Correct. Also, what Lazermon and Twizz previously mentioned is spot on.

As for your claims Kutshi, you'll have to go long and far to actually accomplish something like that, especially considering I watched about ten players with <Phoenix> tag sitting on their mounts on the north edge, doing nothing but observing Azuregos going from ~90% to 10%. Multiple other players in our two raids confirmed the same thing.

Incorrect. All of us in the raid engaged as soon as he was neutral, whereas all of you were idle in the hill untill you had Slo reset him for you. Enough with the blatant bullshit already.

Regardless, key point is if you start to colude with set guilds and leaving another in the dark, only to start pointing fingers when you find out they wont simply follow your orders because of lack of transparency, you're only going to run into more trouble in the future. Think about it, this is the first of many world bosses and this was his 2nd death and people are already salty as fuck instead of working together and accepting that another horde guild got it over the opposing faction.

[DeeMarie]

Horde looted it, it's that simple. Whether that was fair or not because of bugs/guilds not helping, is another discussion. If NOPE couldn't down him solo, I doubt you could. Grats on the loot, but sorry it wasn't your kill.

[nervous]

remove the grizzly on the front page, and just mark it down for the horde. saying anyone got a "kill" on azuregos at any point thus far is beyond retarded.

with the amount of raid guilds floating around, we don't need unnecessary bloat to the progression page. let's stick to 40 mans.

[Twizzerious]

The funniest thing of the whole situation is which guilds are being greedy in the matter.

During the first azuregos kill, alliance have said that <NOPE> did not cooperate with the alliance faction opposition against the horde. Instead, they sat back in attempts to snipe tags. They never helped <MCST> or any other alliance guild when they had the tags. They backed off and allowed horde to push through and reset him. On the horde side, <Convulsion> also refused to aid when either <Grizzly> or <Dreamstate> or even the pug raid got the tag. They screamed and screamed to reset and not to attack the boss allowing alliance to push through and reset.

Second azuregos kill, <Pheonix> sits on the side lines waiting for a chance to tag not aiding in the defense against alliance.

All the while <Grizzly> fights (on both kills) for the horde tag no matter who's it is, assisting their brethren horde for the kill and doing all in their power to make sure alliance doesn't get the tag. Even to the extent of merging our forces with dreamstate.

And yet, <Grizzly> are the bad guys in every situation. People really need to open their eyes on subjects and not follow like lamb to the slaughter. I understand the hive mind is strong but jesus christ.

[Azi]

Barely touch Azuregos. Claim a guild only kill. Organise a major circlejerk about it on forums. Well played, Phoenix.

[Imbaslap]

does it mean Azu does not respawn randomly between 1(3) to 7 days? Makes it easy to camp/US can get it kinda all the time if it's respawning after midninght for EU on sunday.(monday)

it means that its a fixed timer and it needs to be corrected. as of right now, azuregos's respawn timer is Not working correctly and spawns only on sunday around 2200 server time.

also in retail vanilla, every server crash or server maintenance would reset the respawn timer back to 0, delaying the respawn of the dragon. (this is unreasonable on a server that crashes everyday)

grats on a dragon kill by the way,
Devs, start looking into a fix for the respawn timer. :^)

[jdizzell]

The funniest thing of the whole situation is which guilds are being greedy in the matter.

During the first azuregos kill, alliance have said that <NOPE> did not cooperate with the alliance faction opposition against the horde.

Why is <NOPE> obligated to cooperate with any guild for any kill? If you feel that they are then you obviously can not get any kills on your own.

remove the grizzly on the front page, and just mark it down for the horde. saying anyone got a "kill" on azuregos at any point thus far is beyond retarded.

Agree 100% no guild has a kill yet on Azu and I think there shouldn't be any guild listed until Azu properly regains his health on reset.

[Cataclysm]

you understand this puts a dangerous precedent regarding azuregos down the line? if more and more guilds decide to wait by the line until azu is low, by the end there wont be any guild engaging azuregos and everyone will just idle around until either enough people leave, or they get bored and go do something else.

A dangerous precedent? Really? If one wants to do that, he will, getting a silly cross is of no importance in the end, the only thing people want is to loot the corpse.
Now that everyone is either mad or simply jealous, we might want to talk about something way more important. The fact that Azuregos (and every other outside mob for that matter) doesn't regen its HP while on the way back to its spawn but once he's back in place. Making it easy to tag a mob low on HP.
This bug (because you all know that it's a bug) is actually the only reason such things are possible.

Such things:
- For a guild of the same faction to actually make a mob reset (the way it's working at the moment is wrong, you can't just take the aggro of a mob & then make it reset for everyone, this is ridiculous.) As long as someone is in the aggro list, it shouldn't ever happen.
- For anyone to simply profit from the fact that a boss/mob doesn't regen while going back in his place but rather when he's reached it. And this problem is the only reason why we kill the poor fellow so easily, despite being so many of both factions. We can just 'steal' it whenever we want (and I'll remind you that, that's exactly what you did at the beginning of the fight, so don't try to play the victims here.)

These bugs should be fixed ASAP.
And they're the only reason why we can't have proper fun on worldbosses as of now. And, yeah, anyone that actually played on retail (not feenix, not E.D.) knows that what I'm saying is true.
Think about this before blaming others for doing exactly what you tried to do five minutes earlier (and failed to do.)

I hope this gets fixed quickly, it'll bring back some fun in doing outdoor bosses...

I agree to a 100% that while a mob is evading he should be regenerating health, not when he is back to his original position. This is how it worked on blizzlike servers

However, saying that it doesn't put a dangerous precedent is ignorant. Until it gets fixed, more and more guilds will do this. The reason I bring it up is not because I am mad or jelly over losing loot, it's because we as a guild want HORDE to get the kills. Every time HORDE guilds don't help each other out and instead hope for, and in some cases assist in, azuregos resetting while low during HORDE tag, we risk losing it to the alliance. That is all.

But as you said, it's every guilds choice. Just gotta hope that more guilds dont start doing the same shit because that'd ruin the "world pvp experience" that is azuregos. For everyone.

[Jduffs]

On the horde side, <Convulsion> also refused to aid when either <Grizzly> or <Dreamstate> or even the pug raid got the tag.

LOL okay man. Thats why Grizzly reset our tag multiple times during the first kill, and was nowhere to be seen other times we had the tag. It wasnt until the end (>50% hp) did the Horde really start working together.

On topic: If you're saying that it only matters if Horde or Alliance get the kill because it is a joint effort then fine. But to refuse Phoenix because of "muh horde" whilst crediting Grizzly with the first kill is hypocritical.