not only they fixed the aegis' bug, but they also nerf it...

[extrapayah]

i am very disappointed with the silence... the change is real, and aegis' users aren't idiot, we don't need to be a genius to realize the change, because how significant it was, and because of the significance, we deserve some explanation here

[Eldorado]

It is quite obvious why they fixed this. Warriors are not intended to clear mobs as fast as mages can. Warriors will be buff but not this kind of buff. Its hilarious why people keep pushing to return something that can ruin the game. Mages waited for years for a decent buff that will not affect class balance much and warrior will never be an excemption for this one. I will just return what other class always tells a mage not to beg for buf and to switch to other class. Hey warrior, make a mage or a rogue, it is part of the game.

[HotStuven]

So you're saying Warriors should just make a Mage or a Rogue? Why not just anex the Warrior character from the game? With all due respect, your argument makes no sense at all. Warriors, even before the Devs stripped the weapon of its ONLY use, made Warriors at least have a nice and steady damage output, enough to stay relevant in Elite maps. Rogues and Mages were still better, but at least Warriors were decent. Now it's depressing how slow and painful it is to kill just one enemy. May I remind you that the Glintstone Weapon has no PvP value whatsoever, unlike your Gun and the Rogue's Bow; Our Aegis was only for PvE, and now it's basically destroyed. STS needs to listen to the majority and make a better decision. At this point, we don't want a new weapon. A new weapon would mean they have to make new ones for Rogue and Mage, as well, which would take months. All we want is our Aegis back to the way it was so we can stay relative to the game.

It is quite obvious why they fixed this. Warriors are not intended to clear mobs as fast as mages can. Warriors will be buff but not this kind of buff. Its hilarious why people keep pushing to return something that can ruin the game. Mages waited for years for a decent buff that will not affect class balance much and warrior will never be an excemption for this one. I will just return what other class always tells a mage not to beg for buf and to switch to other class. Hey warrior, make a mage or a rogue, it is part of the game.

[Hustle]

Any moderator response to this would be greatly appreciated even if it is to inform warriors that the aegis will not returned back to the way it was. The silence before and after the nerf is the most maddening thing about all this.

[Froxanthar]

They unable to reply because they already test to verify the problem & the results is...

Glintstone Aegis is still the same as it were before the updates. Its just our mind playing tricks.

[HotStuven]

They unable to reply because they already test to verify the problem & the results is...

Glintstone Aegis is still the same as it were before the updates. Its just our mind playing tricks.

Our minds aren't playing tricks. As players have already stated before, their runs have been TWICE as slow as before. A run in WT4 that takes 3:00-3:30 mins now takes 4:30-5:00mins. Elite runs went from 12-15mins to 22-25mins. I suggest you watch videos of Warriors playing with Glint Aegis before this huge problem. It's nothing compared to what it is now.

[Hellsunk]

No it isn't, before the update the proc would activate by any hit and now only hits made by basic attack, I have noticed how some warriors didn't see that much difference and it's because they weren't using the right skills for it.

[HotStuven]

No it isn't, before the update the proc would activate by any hit and now only hits made by basic attack, I have noticed how some warriors didn't see that much difference and it's because they weren't using the right skills for it.

This is perfect. Thank you, Hellsunk. If you didn't notice a difference, Frox, it's because you weren't using skills like Windmill.

[extrapayah]

probably froxanthar was trying to be sarcastic

since devs replied like that for previous obvious change...

[soon]

How it was changed to AL Suggestions and Feedback?

If it has been moved to feedback, so it was a nerf? It should have been removed for Technical Issues and Bugs.

[Earlingstad]

If I understood correctly, skill attacks and the Aegis proc itself (instead of only basic attacks) went on to make Aegis work its proc more often (intentionally or otherwise) and this has been changed by sts and that is what the OP's issue is?

That brings me to the next question...do other classes' weapon procs depend only on basic attacks or proc attack and skill attacks too?

[soon]

If I understood correctly, skill attacks (instead of only default attacks) went on to make Aegis work its proc more often (intentionally or otherwise) and this has been fixed by sts and that is what the OP's issue is?

That brings me to the question, do other classes' weapon procs depend only on default attacks or skill attacks too?

This is complicated. First, understand how the aegis works.

1- When you hit an enemy you gain a shield
2- You need to hit 10 enemies to create an explosion
3- Skill hits 3 enemies, even if they were made to hit 4 of them
4- An explosion creates a new shield with 3 hits, provided you have enemies to it

What has changed after the update?

1- The first hit should be done with a normal attack, to gain a shield
2- After that, you can use skill to increase the amounts of hit to generate the explosion
3- If you have 9 hits and uses a normal attack, then the shield explodes and you get a new shield
4- If you have 9 hits and uses a skill, the shield explodes and not get a new shield. We need to return to 1

The problem is at 1 and 4. You need to use normal attack not to break the fast chain of explosions. But this type of attack is very slow and has a short range.


If you are thinking this is very OP. Know that it was made this the beginning for this.

Hey guys, we appreciate the feedback related to this. I'm going to jump in related to the Warrior Mythic weapon in case there is a misunderstanding on how it works.

Each enemy hit applies a stack of an armor buff. Each stack adds 25 Armor, up to 250 at 10 stacks. Each enemy hit means a single strike may hit up to 3, and grant up to 3 stacks all at once. When you reach 10 you tip over and the armor explodes dealing AoE damage to all around and taunting them all to the tank, and the cycle begins again.

The cycle of this proc rate can be very quick, and the AoE damage output does add up, as does the implicit taunting of surrounding mobs.

Is this in line with what you are experiencing playing with this weapon? From a design perspective this is certainly a tanking weapon, and not intended to be used for massive damage. If there are suggestions on changes you'd like to see after playing with it and this knowledge, we're always open to constructive feedback.

Thanks guys!

If it was a moderator who moved here. I wish it were for Technical Issues and Bugs.

[Earlingstad]

This is complicated. First, understand how the aegis works.

1- When you hit an enemy you gain a shield
2- You need to hit 10 enemies to create an explosion
3- Skill hits 3 enemies, even if they were made to hit 4 of them
4- An explosion creates a new shield with 3 hits, provided you have enemies to it

What has changed after the update?

1- The first hit should be done with a normal attack, to gain a shield
2- After that, you can use skill to increase the amounts of hit to generate the explosion
3- If you have 9 hits and uses a normal attack, then the shield explodes and you get a new shield
4- If you have 9 hits and uses a skill, the shield explodes and not get a new shield. We need to return to 1

The problem is at 1 and 4. You need to use normal attack not to break the fast chain of explosions.

So in a nutshell, we need basic attacks to make the proc explosion work. If skill attacks and also basic attacks would contribute towards the proc ocurring, then the proc cycle would be endless isnt it?

[HotStuven]

So in a nutshell, we need basic attacks to make the proc explosion work. If skill attacks and also basic attacks would contribute towards the proc ocurring, then the proc cycle would be endless isnt it?

It wouldn't be endless, but it would be decent. Elite maps don't have big mobs, so it takes a while to chain explosions.

[Earlingstad]

It wouldn't be endless, but it would be decent. Elite maps don't have big mobs, so it takes a while to chain explosions.

If elite maps dont have big mobs, big mobs can be created there. Simple. We can ask for bigger mobs in elite maps.

So what you are asking for is that one weapon should be singled out and made immune to the rules of procing? No other weapon enables skill attacks to contribute to procs. Its unfair for mage and rogue when they only have basic attacks for procing their weapns.

And the Aegisis basically stacking armor and is a tanking weapon, as Carapace has mentioned. Even though it wasdesigned to be a tanking weapon, its AOE damage does add up and thats a bonus.

If we need a solely damage-oriented weapon, we could ask for one for the coming expansion or future event. How is it reasonable to give a weapon so much armor and damage (through very quick and almost endless proc cycles) at the same time? I think sts has thoroughly analysed this and then made changes

[extrapayah]

main complaint is uninformed change

and then, is there any rules that weapon's proc need to be triggered only by normal attacks? elondrian bulwark's heal doesn't work like that, afaik, elondrian bow self-heal also works per any damage you made, and although not a weapon, proc from arcane ring, eggshell, and skull gem work on every skill hit, and if you slot skull gem to a weapon, it's technically become the weapon's proc

and also, you might don't know how frustrating it is to hit enemies with a bulwark, there is little to no assistance in targeting when hitting with melee weapons, best way is to stand still, hitting enemies, but have you ever tried in on rengol maps? not trying to dodge stunning red zones only makes you great clown/sitting duck

[bonjovi3223]

Why is this under suggestions & feedback?

How much more feedback do you want before you fix the aegis? Or...do you even intend to fix the aegis at all?
Where is your response to our feedbacks?
We are not suggesting you to empower this weapon any further.
We are not suggesting you to fix this weapon. We are asking you to fix something that you already gave us in the first place.

[Froxanthar]

It's fair because this weapon/proc are design and meant for PvE only. So we warriors could get an invite to Elites or Planar Tombs. That is the main TARGET of this weapon.

The bad side of this weapon is PvP. Is there any normal human who use Aegis would try to hit range class in PvP using basic attack? Does the attack is a guarantee hit? No, we need our skills to do it. Unlike bows and guns, their normal attack is auto-aim which makes the arrows and bullets can hit the target behind you.

To be exact, both of Glintstone gun and bow procs are good in PvP and PvE while the sword-shield is only good in PvE. Is this the fairness?

[HotStuven]

It's fair because this weapon/proc are design and meant for PvE only. So we warriors could get an invite to Elites or Planar Tombs. That is the main TARGET of this weapon.

The bad side of this weapon is PvP. Is there any normal human who use Aegis would try to hit range class in PvP using basic attack? Does the attack is a guarantee hit? No, we need skills to do it. Unlike bows and guns, their normal attack is auto-aim which makes the arrows and bullets can hit the target behind you.

To be exact, both of Glintstone gun and bow procs are good in PvP and PvE while the sword-shield is only good in PvE. Is is the fairness?

I completely agree with you, Frox.

[Earlingstad]

It's fair because this weapon/proc are design and meant for PvE only. So we warriors could get an invite to Elites or Planar Tombs.

Among other things, maybe the actual reason some of the warriors dont get an invite to pve parties for Elites and Planar Tombs is the fact that they are not maxed out. But they still get very vocal on multiple forum threads attempting at making sts believe in the need for buffs.. sigh.