@Waffennacht @Sixty5 the thing is, broken OP things don’t get tuned down until everyone abuses them. I’d rather zaan get tuned properly in the next chapter release than the end of 2018...(decrease the damage buff on a per second scale while increasing the length of the proc to retain similar DPS but lower initial burst)
Having played with and against the set, honestly the only change I'd say that is needed is dropping the range from 10m to 8m
As far as the initial burst goes, even if you eat 3 ticks, you are only taking about the same damage as a Skoria proc.
The only classes that don't have an innate way to deal with a Zaan proc are Warden and DK, and in both cases they have strong enough defensive tools to shrug it off anyway.
3 ticks is 2 seconds. That means you need to instantly react and counter it, effectively with a single GCD. That’s too punishing relative to every other set in the game. The next tick does an untenable amount of damage for most builds.
The zaan damage may be manageable in a vacuum but when you can use it to create concurrent damage with your burst it’s obviously a lot
A full channel of Zaan will hit for 16k on a player with 20k spell res, which a lot, I agree. But, if you get out before the last tick, that drops to 12k, and if you break it before the 5th tick, it only hits for 8k.
3 and a half seconds is more than enough to pop a vigor, dodge roll and then whatever else you need to do to get out of there, and then you have 15 seconds where the other person has lost a big chunk of damage.
You drop the tether range 2m and that whole setup becomes even easier to execute.
My personal experience using Zaan is that in most cases when I get the proc off, I'm killing the guy anyway, and Zaan is just adding overkill.
It isn't like Selenes, where I see a proc and can immediately use it to create a window of burst.
And while you can run setups that are built around Zaan and locking down people. Remember that if you run that sort of thing, you are building completely around a single target proc with an 18 second cooldown, so you are hardly going to be dropping people like flies.
The biggest Zaan proc I've seen in my death recap was 10k. And that was the first time I fought it. Since then, it really hasn't been an issue to play against.
Lotus fan. Zaan procs. Zaan tick.
Incap, you’re down. Zaan tick
You get up. Zaan tick
Zaan tick. Lotus fan if you move, otherwise just execute, you’re probably almost dead right?
Repeat Lotus fan. Hey, five ticks, are you dead yet?
Remove these horrible proc sets already.
Stampede for a snare
Dizzying Swing hits, target is stunned
Heavy attack into Dawnbreaker as they get up
Reverse slice for the kill
I've eaten both combos, and been killed by both. If you are eating a full combo from someone, including an ult, it is going to hurt, and chances are it will kill you.
What is it exactly that makes the first that much worse than the second?
@Waffennacht @Sixty5 the thing is, broken OP things don’t get tuned down until everyone abuses them. I’d rather zaan get tuned properly in the next chapter release than the end of 2018...(decrease the damage buff on a per second scale while increasing the length of the proc to retain similar DPS but lower initial burst)
Having played with and against the set, honestly the only change I'd say that is needed is dropping the range from 10m to 8m
As far as the initial burst goes, even if you eat 3 ticks, you are only taking about the same damage as a Skoria proc.
The only classes that don't have an innate way to deal with a Zaan proc are Warden and DK, and in both cases they have strong enough defensive tools to shrug it off anyway.
3 ticks is 2 seconds. That means you need to instantly react and counter it, effectively with a single GCD. That’s too punishing relative to every other set in the game. The next tick does an untenable amount of damage for most builds.
The zaan damage may be manageable in a vacuum but when you can use it to create concurrent damage with your burst it’s obviously a lot
A full channel of Zaan will hit for 16k on a player with 20k spell res, which a lot, I agree. But, if you get out before the last tick, that drops to 12k, and if you break it before the 5th tick, it only hits for 8k.
3 and a half seconds is more than enough to pop a vigor, dodge roll and then whatever else you need to do to get out of there, and then you have 15 seconds where the other person has lost a big chunk of damage.
You drop the tether range 2m and that whole setup becomes even easier to execute.
My personal experience using Zaan is that in most cases when I get the proc off, I'm killing the guy anyway, and Zaan is just adding overkill.
It isn't like Selenes, where I see a proc and can immediately use it to create a window of burst.
And while you can run setups that are built around Zaan and locking down people. Remember that if you run that sort of thing, you are building completely around a single target proc with an 18 second cooldown, so you are hardly going to be dropping people like flies.
The biggest Zaan proc I've seen in my death recap was 10k. And that was the first time I fought it. Since then, it really hasn't been an issue to play against.
Lotus fan. Zaan procs. Zaan tick.
Incap, you’re down. Zaan tick
You get up. Zaan tick
Zaan tick. Lotus fan if you move, otherwise just execute, you’re probably almost dead right?
Repeat Lotus fan. Hey, five ticks, are you dead yet?
Remove these horrible proc sets already.
Stampede for a snare
Dizzying Swing hits, target is stunned
Heavy attack into Dawnbreaker as they get up
Reverse slice for the kill
I've eaten both combos, and been killed by both. If you are eating a full combo from someone, including an ult, it is going to hurt, and chances are it will kill you.
What is it exactly that makes the first that much worse than the second?
First off, stampede just got nerfed, it won’t be contributing much damage to your combo.
Second off, I will usually see you coming. Block. Dodge roll. There are counters. It’s my fault if I don’t. The NB opens from stealth and kills you before you can stand up or react. That’s because of the proc set, and 2-3 button pushes. There’s a big difference.
ZOS apparently didn’t learn from the last time they created instant proc sets, so they did it again. The sign of insanity is doing the same thing over and over, then expecting different results.
@Waffennacht @Sixty5 the thing is, broken OP things don’t get tuned down until everyone abuses them. I’d rather zaan get tuned properly in the next chapter release than the end of 2018...(decrease the damage buff on a per second scale while increasing the length of the proc to retain similar DPS but lower initial burst)
Having played with and against the set, honestly the only change I'd say that is needed is dropping the range from 10m to 8m
As far as the initial burst goes, even if you eat 3 ticks, you are only taking about the same damage as a Skoria proc.
The only classes that don't have an innate way to deal with a Zaan proc are Warden and DK, and in both cases they have strong enough defensive tools to shrug it off anyway.
3 ticks is 2 seconds. That means you need to instantly react and counter it, effectively with a single GCD. That’s too punishing relative to every other set in the game. The next tick does an untenable amount of damage for most builds.
The zaan damage may be manageable in a vacuum but when you can use it to create concurrent damage with your burst it’s obviously a lot
A full channel of Zaan will hit for 16k on a player with 20k spell res, which a lot, I agree. But, if you get out before the last tick, that drops to 12k, and if you break it before the 5th tick, it only hits for 8k.
3 and a half seconds is more than enough to pop a vigor, dodge roll and then whatever else you need to do to get out of there, and then you have 15 seconds where the other person has lost a big chunk of damage.
You drop the tether range 2m and that whole setup becomes even easier to execute.
My personal experience using Zaan is that in most cases when I get the proc off, I'm killing the guy anyway, and Zaan is just adding overkill.
It isn't like Selenes, where I see a proc and can immediately use it to create a window of burst.
And while you can run setups that are built around Zaan and locking down people. Remember that if you run that sort of thing, you are building completely around a single target proc with an 18 second cooldown, so you are hardly going to be dropping people like flies.
The biggest Zaan proc I've seen in my death recap was 10k. And that was the first time I fought it. Since then, it really hasn't been an issue to play against.
Lotus fan. Zaan procs. Zaan tick.
Incap, you’re down. Zaan tick
You get up. Zaan tick
Zaan tick. Lotus fan if you move, otherwise just execute, you’re probably almost dead right?
Repeat Lotus fan. Hey, five ticks, are you dead yet?
Remove these horrible proc sets already.
@Waffennacht @Sixty5 the thing is, broken OP things don’t get tuned down until everyone abuses them. I’d rather zaan get tuned properly in the next chapter release than the end of 2018...(decrease the damage buff on a per second scale while increasing the length of the proc to retain similar DPS but lower initial burst)
Having played with and against the set, honestly the only change I'd say that is needed is dropping the range from 10m to 8m
As far as the initial burst goes, even if you eat 3 ticks, you are only taking about the same damage as a Skoria proc.
The only classes that don't have an innate way to deal with a Zaan proc are Warden and DK, and in both cases they have strong enough defensive tools to shrug it off anyway.
3 ticks is 2 seconds. That means you need to instantly react and counter it, effectively with a single GCD. That’s too punishing relative to every other set in the game. The next tick does an untenable amount of damage for most builds.
The zaan damage may be manageable in a vacuum but when you can use it to create concurrent damage with your burst it’s obviously a lot
A full channel of Zaan will hit for 16k on a player with 20k spell res, which a lot, I agree. But, if you get out before the last tick, that drops to 12k, and if you break it before the 5th tick, it only hits for 8k.
3 and a half seconds is more than enough to pop a vigor, dodge roll and then whatever else you need to do to get out of there, and then you have 15 seconds where the other person has lost a big chunk of damage.
You drop the tether range 2m and that whole setup becomes even easier to execute.
My personal experience using Zaan is that in most cases when I get the proc off, I'm killing the guy anyway, and Zaan is just adding overkill.
It isn't like Selenes, where I see a proc and can immediately use it to create a window of burst.
And while you can run setups that are built around Zaan and locking down people. Remember that if you run that sort of thing, you are building completely around a single target proc with an 18 second cooldown, so you are hardly going to be dropping people like flies.
The biggest Zaan proc I've seen in my death recap was 10k. And that was the first time I fought it. Since then, it really hasn't been an issue to play against.
Lotus fan. Zaan procs. Zaan tick.
Incap, you’re down. Zaan tick
You get up. Zaan tick
Zaan tick. Lotus fan if you move, otherwise just execute, you’re probably almost dead right?
Repeat Lotus fan. Hey, five ticks, are you dead yet?
Remove these horrible proc sets already.
Lotus fan. Block. ??? Profit. Yeah, they may fear you, but then that is a dent in their gank plan. And pretty big assumption that Zaan procs instantly.
Hey everyone!
We'd like to confirm that the Elf's Bane & Zaan combination is working as designed when it comes to the extra ticks, it's not a bug.
It's possible that it could be reviewed further down the line depending on player feedback, but as it stands at present, this is intentional.
We hope this helps!
Hey everyone!
We'd like to confirm that the Elf's Bane & Zaan combination is working as designed when it comes to the extra ticks, it's not a bug.
It's possible that it could be reviewed further down the line depending on player feedback, but as it stands at present, this is intentional.
We hope this helps!
I honestly don’t know what they have in mind when they design these sets. If you’re up against a good player utilizing Zaan that has built around it there is no where you will go, and you’ll certainly eat the full duration on top of the other incoming damage.
WrathOfInnos wrote: »I just tried making a mDK build around this, Zaan did an incredible 4k DPS with elf bane. However, the 3 health enchants on the elf bane jewelry lowered the rest of my skills enough that I could only get about 33k DPS out of it. I did feel very survivable with over 20k health unbuffed. It could be a fun dungeon build, but definitely not the most powerful. Could be interesting in PVP if you can get anyone to stand in your beam for 7s.
Yeah, I had a discussion about it with some mates, and the end conclusion is that it isn't that viable for PVE stuff. Straight magicka food is a fantastic idea to get around the healthy rings issue, but then you are either stuck with running a 4 piece set.
You could always go dual wield Mag DK, which is something I like the sound of, but I'm not sure what set you'd really want to go with.
But I'd say the bigger application is on a PVP build, where you can go full tank, and just abuse Zaan's massive damage when paired with Elf Bane.
Currently I am leaning towards running it on a Magblade, given that they can permanently stick to a target with Lotus Fan, and have access to strong crowd control options in Fear and Cripple.
For the DW mag DK I plan to test 5xBSW, 5xAcuity(front-bar), 2xZaan and 1xMaelstrom firestaff. That’s probably the best setup you can put together.
Problem with mag DK is you’re competing for a melee spot with stamblades and stamdks all of whom do better deeps. And any type of Mageblade will our dps you completely.
War Machine and Master Architect are beyond silly on Nightblade with a 70 ult souil harvest / Incap. They have been blowing everyone out the water since Morrowind.