spak+ fork vs pierce

Doesn't it seem a little inefficient to use fork instead of pierce?

Spack?

LOL no.


Fork is the best support gem for sporker


READ

This gem will cause any projectiles created by the linked skill to fork. When a projectile hits an enemy and forks, it splits into two identical projectiles that continue on and can hit additional enemies.

base proj damage = 100 (for ease)

Spark+fork= 100*0.70*9=630

Spark+pierce= 70% to pierce indefinitely, picking a number of 3 pierces per proj is realistic, turning into 100*9=900

And 900-630=270 allowing for 2, almost 3 projectiles to fail piercing

"

CrimsonMidget wrote:

base proj damage = 100 (for ease)

Spark+fork= 100*0.70*9=630

Spark+pierce= 70% to pierce indefinitely, picking a number of 3 pierces per proj is realistic, turning into 100*9=900

And 900-630=270 allowing for 2, almost 3 projectiles to fail piercing

Pierce doesn't offer 70% piercing unless it is leveled and has quality added to it. Fork when leveled gets rid of the -30% damage penalty and quality adds in more damage where Pierce merely adds in a higher chance to pierce. I'm also guessing mobs aren't coming at you in neat little rows so the odds of Fork hitting more targets is likely higher. In short, Pierce can add 74% chance to pierce. Fork can add 18% more damage factoring in the -30% that then gets multiplied by other boosts, ie skills points, Lightning Penetration, etc. Also, Pierce ultimately is still three patchs of spark as where Fork now generates two more patches per each initial patch that hits and thus increases the likelihood of each one of them hitting.

First, Fork with levels and quality gives increased damages and the modifier is 30% less damages, so Without_Pause is wrong with the "more damages when leveled" part.

The real problem is the mechanic of percing : I'm almost sure a projectile who already pierce a target can't deal damages to that target again. Which mean your damages are a bit random, because if the same projectile hit the same target, it'll do zero damage and can fail pierce.

Second, don't forget Spark as 3.5s duration, and Pierce doesn't increase it (but Fork reset this timer, because it's a new projectile). Let's say you're in a small room, the same projectile can hit an enemy every second.

It give you :
(1+0.00)*3*(100+100*(0.7+0.7^2+0.7^3+0.7^4)) = 832 total damages. This is the best case, and you can deal anything between 300 & 832 in average, reliant on the target you can hit.

With lvl.20/20% Fork, you've :
(1+0.48)*3*100*0.7*3 = 932 damages. Always.


If you want, we can add some Spell Damages to negate a bit the advantage of Fork on Pierce, because they're going to be additive with the damage increase.
Let's take 100% Spell Damages, and see what you get :

- 600 to 1664 Damages for Pierce.
- 1562 for Fork.

So unless you have a solution for single target damages and small groups, and you only want to use Spark+Pierce on huge pack, Fork is better.

"

Maniaa wrote:

First, Fork with levels and quality gives increased damages and the modifier is 30% less damages, so Without_Pause is wrong with the "more damages when leveled" part.

You basically confirmed what I said while saying I was wrong. Does Fork do more damage as it levels? Yes it does.

fork on spark is far superior