Fulmination procing "On weapon hit" effects.

[Emnel]

First instance of damage in "Fulmination" spell is, unlike in any other spell in the game, an "Attack" rather than "Effect" causing it to proc all "On weapon hit' and "On weapon crit" effects such as all of the weapon enchants, Landry's "Stance: Mage Slayer" and "Miasmic Strikes" talents as well as poison effects and such.

It very much seems like a mistake, bordering on gamebreaking at that since once you get all the weapon enchantment spells running along with few range aspects and/or poisons the damage and utility of it is off the charts. Turns Path of the Damned into a Walk in a Park.

 

[Emnel]

Oh, and due due to the way those Weapon Enchantment procs work Fulmination casts provide absurd amount of Control [Magic] and Lore experience to the buff casters. A single cast hitting 5 enemies just gave my characters who had those enchants on the caster between 1 and 2 ranks of Lore and Control [Magic] with those ranks at level 50 or higher.

 

[Emnel]

Here is the effect just 2 Fulmination in the combat I just found out about it in. It is a Path of the Damned and no other damaging effect was used since the combat started, save 2 autoattacks by my main character. In the log you can see a litany of procs caused by Eb's Fulmination cast.

 

[Obsidian_David]

Hello @Emnel,

Thank you for reporting this. Could you upload a save in which this is occurring for you? It would be very helpful in getting to the bottom of this issue.

Thank you,
David

 

[Emnel]

Actually I seem unable to reproduce the results today. On hit effects seem to once again consistently be applied only by abilities that use Primary Weapon stats as their base for damage. So for example Arcane Assault will proc them, while Terratus' Call, Gravestrike or indeed Fulmination won't. Even in the case of abilities such as Shield Assault only the second proc (one based on weapon's damage) procs on hit effects.

At first I though it has been fixed in today's patch, but I've loaded the Review Build via Steam and it is working on it properly as well. Must have been some kind of glitch that resolved itself on reload or restart of the game (I honestly don't remember if I reloaded the save between noticing it and turning of the game last night).

In hindsight I should have probably started by turning it on and off, but I tend to get excited about those kinds of QA issues and love getting to the bottom of them...

You're probably better off disregarding it for a time being, but I'll attach the save files anyway, in case you want to try and recreate it.

Cheers!