Forum Settings
       
Reply To Thread

Damage Caps?Follow

#1 Mar 13 2008 at 11:10 AM Rating: Good
***
1,634 posts
Ironically - There was a post about this and I experienced it for the first really noticable time last night.

We got a 70 Pally and she rounded up all of SM Cathedral. I Blizzed. I'm hitting for like 36 to 40 until some of the mobs die.

So a few questions:

1. What's the Max Bliz can do?
Meaning per tic
When does this Damage Cap kick in? 4, 5, 7, 10 mobs? How many?
2. Is there a way to boost it? (Is it stackable with +Damage or +Frost stuff)
3. Does anyone else thing that it's sort of unfair?
4. Does the same exist for other/all AOE attacks?
#2 Mar 13 2008 at 11:32 AM Rating: Good
**
428 posts
Ironically again, I believe certain Pally AoE attacks have no cap. But don't quote me on that...

Also I believe the dmg cap is on dmg per tick, not # of mobs, though the two are obviously directly correlated in an AoE attack.

What is the purpose of an AoE dmg cap anyway? How often does it really matter?

Edited, Mar 13th 2008 3:35pm by AynLoD
#3 Mar 13 2008 at 3:22 PM Rating: Good
Citizen's Arrest!
******
29,527 posts
AynLoD wrote:
What is the purpose of an AoE dmg cap anyway? How often does it really matter?


I believe non-AoEers complained. Though I could be wrong.
#4 Mar 13 2008 at 4:16 PM Rating: Good
***
1,245 posts
Borsuk wrote:
Ironically - There was a post about this and I experienced it for the first really noticable time last night.

We got a 70 Pally and she rounded up all of SM Cathedral. I Blizzed. I'm hitting for like 36 to 40 until some of the mobs die.

So a few questions:

1. What's the Max Bliz can do?
Meaning per tic
When does this Damage Cap kick in? 4, 5, 7, 10 mobs? How many?
2. Is there a way to boost it? (Is it stackable with +Damage or +Frost stuff)
3. Does anyone else thing that it's sort of unfair?
4. Does the same exist for other/all AOE attacks?



1ab. Somewhere near 3600 if you mean the highest rank.

1c. The Damage Cap kicks in when you have enough mobs that the potential amount of damage you would do exceeds the particular spell's damage cap. In the case of this Blizzard, the damage cap would kick in when you would do enough damage in a single tick of Blizzard to exceed 3600 damage. If you normally do 300 damage to each mob per tick of Blizzard, you'd need to be casting it on more than (3600/300=) 12 mobs for the damage cap to be noticed.

2. Nope.

3. Not unfair, persay, but could be much improved to scale with damage. There's a purpose to them.

4. Based on what I've seen, I'd think so, but that's inductive logic. All 7 Mage AoE spells have damage caps, and I've seen listed Seed of Corruption's damage cap, and have personally tested a Shaman and posted the Fire Nova totem's and Magma totem's damage cap.

Quote:
Ironically again, I believe certain Pally AoE attacks have no cap. But don't quote me on that...

Also I believe the dmg cap is on dmg per tick, not # of mobs, though the two are obviously directly correlated in an AoE attack.

What is the purpose of an AoE dmg cap anyway? How often does it really matter?


1. I'll have to see/ask/test the cap for a Pally's Consecration. I'd assume that it has a cap, because shaman and warlock AoEs have caps. Also, make sure you're not confusing an AoE attack with reflective damage. Reflective damage is applied to each mob individually when they hit your character, and is not considered an AoE attack. Also know that multitarget abilities, those with a limited amount of possible targets but affect more than one, are not the same as AoE, which is area of effect and is not limited to the number of targets they may affect.

A paladin's Consecration is an AoE attack. Retribution Aura does reflective damage. Avenger's Shield is a multitarget ability.

2. The damage cap is on total damage per application of the spell. Arcane Explosion applies its damage only once. Blizzard applies it 8 times. A shaman's Magma Totem does it 10 times. A warlock's Hellfire does it 15 times.

It is correct to say that damage caps are not based on the number of mobs, but it's in direct correlation when concerning AoE attacks.

3. The purpose of AoE damage caps is to stop Faxmonkey from being as awesome as he can be.

Level 60 Faxmonkey before Damage Caps.

http://www.youtube.com/watch?v=z_27aMytL5c

It's balance.





Edit: Also, feel free to reply to this thread: http://wow.allakhazam.com/db/class.html?wclass=7;mid=120519595498664243;num=10;page=1

It's on the same subject as this original post and would belong in there.

Edited, Mar 13th 2008 8:32pm by Raglu
#5 Mar 13 2008 at 8:38 PM Rating: Decent
there have been changes to mob behavior as well... attack start speed and movement rates have been tweaked such that what you could do on an epic mount in the old days is much harder to do now without getting dazed off your mount.

i don't disagree with damage caps, but i'm simply disgusted by seed of corruption. mages need more efficient AOEs in general, and it would be nice to be able to "fire and forget" an AoE. specifically, they need to remove the blizzard talents and make them automatic and lamestrike has needed a buff since release.

it's ******** that 99% of kara guilds, for instance, consider it absolutely necessary to have one or two warlocks to make illhoof possible.
Reply To Thread

Colors Smileys Quote OriginalQuote Checked Help

 

Recent Visitors: 126 All times are in CST
Anonymous Guests (126)