How well do GGG really understand the mechanics of their own game?
|
Apparently you didn't read what I said. I said area of effect damage increases wouldn't apply. The penalty on Melee Splash didn't apply anyway because it's an attack damage penalty.
| |
|
Whats the status on Storm Call and trigger gems? Also there is no Skill feedback for Storm Call... Is this gem just rushed out the door to have some content alongside support packs?
Then with the recent update for 1.03 "With 1.0.2 live on the realm, the team are currently working on two goals: a 1.0.2b update patch that improves some areas of 1.0.2" Doesnt seem like it's even focused on? I keep seeing people saying it's a bug but i have yet to hear what a mod/developer confirm anything. Last edited by TwoCoins#2128 on Dec 2, 2013, 3:19:08 PM
|
|
" It seems like ignite damage from a fire damage crit or other fire soucre with ignite chance should be calculated as its own completely unique entity. Just as you calc your fireball hit damage by the gem level's stated damage range and then apply all your passive mods & mods from supported gems. For ignite, instead of using some gem's stated damage range, you use your base fire damage as the base. Then calc it up by all applicable mods for burning damage, be it +/-% fire, burning, etc. Since igniting a single target mob is not an AoE affect, I imagine AoE mods could not apply to ignite damage directly (obv, could affect the base fire damage when appropriate). |
|
|
I suppose what would be nice is a clear list of the mod tags that apply to the various forms of DoT damage:
1. ignite damage (affects a single mob, caused by fire damage crit or any fire damage with a "chance to ignite") 2. burning damage (from fire trap ground effect, or is this completely identical to ignite damage with the exception that AoE tagged mods affect it?) 3. pierce damage 4. Viper Strike counter damage 5. Poison Arrow cloud damage With a definitive list of mod tags, we can prolly put a lot of this confusion to bed easily. |
|
" I guess I'm unclear on the entire concept of "AoE damage". Unlike a PA poison cloud, a VS Chaos charge seems more like a single-target debuff than a type of AoE damage. So Melee Splash is supposed to convert Viper Strike from a debuff into an AoE effect? Seems like an artificial way to retroactively buff something that didn't need to be crippled in the first place. Fixing this bug is not going to motivate me to link Viper Strike + Melee Splash + Concentrated Effect in order to restore its degen rate back to what it was in 1.0.1. |
|
|
This has already been answered in this thread.
" Melee Splash gives the supported skill an AoE. Viper Strike is a DoT that is then applied by the AoE. It is a bug if the correct damage increases do not apply, regardless of whether or not it will make you use the skill. Last edited by Ellie_GGG#0000 on Dec 2, 2013, 3:44:30 PM
| |
" I heard the fix for Stormcall not working with Cast on critical attack etc. comes with 1.0.2b Source http://www.reddit.com/r/pathofexile/comments/1rp3m3/is_storm_call_bugged_cant_support_with_cast_on/ “Demons run when a good man goes to war" Last edited by Sneakypaw#3052 on Dec 2, 2013, 3:54:53 PM
|
|
" this would be nice |
|
" well thanks for the answer, cant blame people for being confused when confirming things off reddit and not official forums. |
|
|
Ignite Damage = [Base Firedamage] * [More*Less*Effectiveness*0.8*critmulti] * (conc effect*oMddmod)^2 * (inc Firedamage+oIddmod)^2
oMddmod means: "other More doubledipping modifiers" oIddmod means: "other Increased doubledipping modifiers" have updated my formula a bit. Can this be true? ING: "MeneaterMildrid" or "WICKEDSICKmoves"
|
|
