Stuns conflicting

[Xydrik]

I havenoticed a fewissues with my stuns conflicting.

Stunnerdoesn't hit if the mob has been stunned with my bolt with the stun tech.The stunner ability's sole purpose is to stun and it's stun lasts longer than the stun tech, it should take presedence. As it is nowthere's no reason you would want to use it until after you waited for the effect from the stun techto wear off. This slows down combat.


Numbing Haze doesn't hit if the mob has stunner on it at the time. Numbing haze is a long term stun with a casting delay wile stunner hit's instantly and lasts for a short duration. It would make more sense if you could stun the mob quickly for a short duration and use that time to set up alongertermstun.

Any other stuns not working as expected?

[Jaraiden]

It would make more sense if you could stun the mob quickly for a short duration and use that time to set up alongertermstun.

And for the monsters also, is their AI doing this also?

[Eni]

Same issue with all debuffs. The effect of higher level overwrites the lower ones. special with techs that are weak compared to the level overwriting a little lower abilitys that are much more powerfull is not that nice.

[Xydrik]

It's not always higher stuff overwriting lower stuff... For instance, my numbing haze 5 won't overwrite stunner 2.

[AmonGwareth]

For some reason the weight of Numbing Haze was set to practically 0 which means it would not overwrite anything. I have corrected this in the database (for next patch) so Numbing Haze V should now overwrite Stunner III.

- Amon

[Xydrik]

Thanks Amon[:D]

[imported_tjl]

On a similar note, Immolate (the spell), Burning dmg (the spell tech) and Engulf (the mage ability) have bizarre conflicts as well.

if Immolate V is on a mob, enulf V (which is way better) fails to go on the mob, saying that "target has immolate V on it, failed" or somesuch. All three of those things I listed need to be put in the correct hierarchy. From best, to worst:

Engulf > Immolate > Burning Dmg if they are of the same tier.

It would be ideal if immolate and burning dmg could stack, since that would make two fairly worthless effects combine into one pretty good one... but the most important part is the Engulf needs to work no matter what, its a pretty important ability for a mage.

[AmonGwareth]

well, that gets more complicated... You see, "best" and "worst" are not absolutes and are very subjective. Typically the way we weight something is based on the skill required to use it or the level at which it is obtained.

- Amon

[imported_tjl]

well, that gets more complicated... You see, "best" and "worst" are not absolutes and are very subjective. Typically the way we weight something is based on the skill required to use it or the level at which it is obtained.

- Amon

well you can ask any mage which is "best" and they will all say engulf. why? because its damage ticks are much faster than immolate, and does more damage per tick. engulf is absolutely better for a mage than immolate. Here are the numbers to support my claim:

Engulf V
gained at 84 Mage
84-101 Flame dmg every 3 sec, for 21 sec. (7 ticks) up to 707 dmg possible

Immolate V (unteched)
need level 82 to use
42-58 Flame dmg every 7 sec, for 49 sec. (7 ticks) up to 406 dmg possible

Burning Effect V
5-5 Flame dmg every 4 sec, for 20 sec. (5 ticks) up to 100 dmg possible

[Xydrik]

Back to the topic of stuns conflicting...

Spellbind 2 fails because of stunner 1.

[AmonGwareth]

Well, Spellbind 2 won't fail because of Stunner 1 anymore. It will fail because of Stunner 2 though.

Have altered Engulf so that it is higher than Immolate. Looking into Burning Effect. Not sure off-hand what ability/spell causes that.

- Amon

[imported_tjl]

Well, Spellbind 2 won't fail because of Stunner 1 anymore. It will fail because of Stunner 2 though.

Have altered Engulf so that it is higher than Immolate. Looking into Burning Effect. Not sure off-hand what ability/spell causes that.

- Amon

Thanks for the engulf change [:)]
Burning Effect is a tech that can go on almost all flame spells, and has a % chance to proc.

[Xydrik]

Well, Spellbind 2 won't fail because of Stunner 1 anymore.

- Amon

Amon... You are the man. I'll let you know if i run into anything else.

[PJ]

Okay I've got a big question on the entire issue of which debuff/buff overwrites which.

Once you've determined that two different abilities should conflict. I.e. Rust and Banish Armor. Or Immolate and Engulf. Or Promote Vitality and Earthen Crust. And so on.

Why can't you just make it so the most recent one sticks. I.e. since you can't decide whether rust is better or banish armor is better, just make it so if a mob has Rust on it, and somebody uses Banish later on, Banish will stick. And if a Mob has Banish, and somebody decides to use Rust, Rust will stick.

It would give a smart group the ability to choose which debuff is better for a particular case.

[AmonGwareth]

Because the system does not work that way. Each augmentation is weighted and given keywords. If it encounters a keyword match and is weighted more then it will overwrite.

- Amon

[PJ]

What happens when the weights are equal?

[Eni]

disconcert (80% focus, 80% power, +20% delay) get overwrite by derange (85% power, 85% focus)

[Xydrik]

Speaking of disconcert, I just hit a mob with spellbind and disconcert proc'd and released spellbind.

[AmonGwareth]

Disconcert is received at level 30 Sorcerer so I have adjusted its weight so that it will now overwrite Derange II.

I do not see how Disconcert and Spellbind could interact. Perhaps you meant a different ability?

- Amon

[Xydrik]

Hmmm... just tried spellbind again until disconcert proc'd and spellbind was not affected.

I think what happened is I used stunner 1 and then spellbind. It still said spellbind hit, but I never saw the failure message in the combat log, but that's been a common occurence lately.