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!
Still want to know if elf bane works the same for grothdar
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!
Waffennacht wrote: »I told you Gina said this about elf bane + Grothdarr like a year ago...
Why no one listen? Lol
Waffennacht wrote: »I told you Gina said this about elf bane + Grothdarr like a year ago...
Why no one listen? Lol
It doesn't actually work with grothdarr, weirdly enough.
Waffennacht wrote: »Waffennacht wrote: »I told you Gina said this about elf bane + Grothdarr like a year ago...
Why no one listen? Lol
It doesn't actually work with grothdarr, weirdly enough.
She just said it was suppose to (like mystery boxes)
@Lexxypwns why, why must you keep improving people?
@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)
@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.
@ZOS_ChrisHey 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!
@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
@Savos_SarenSavos_Saren wrote: »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!
@ZOS_Chris
With that logic- then Elf Bane should apply toward Grothdarr, Domihaus, Maw of the Infernal, and Illambris... correct?
@ZOS_GinaBruno @ZOS_JessicaFolsom
@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.
@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.
Except there’s images all over discord of it doing more damage than you’re saying because you’re not counting damage buffs or penetration.
@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.
Except there’s images all over discord of it doing more damage than you’re saying because you’re not counting damage buffs or penetration.
I'm just using baseline figures.
Of course someone with 6k spell resist is going to take a lot more damage.
The proc is also doesn't interact properly with cp. Only the base damage is buffed/debuffed by cp. You'll always get a damage increase of 1720 per tick, regardless of the points you put in thaumaturge.
So I'd say that there might be something there to the stupid high damage numbers.
Being a Vamp is also going to get you rekt.
Waffennacht wrote: ».@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.
Except there’s images all over discord of it doing more damage than you’re saying because you’re not counting damage buffs or penetration.
I'm just using baseline figures.
Of course someone with 6k spell resist is going to take a lot more damage.
The proc is also doesn't interact properly with cp. Only the base damage is buffed/debuffed by cp. You'll always get a damage increase of 1720 per tick, regardless of the points you put in thaumaturge.
So I'd say that there might be something there to the stupid high damage numbers.
Being a Vamp is also going to get you rekt.
BGs brah, no CP aka Proc sets even more imbalanced
Waffennacht wrote: ».@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.
Except there’s images all over discord of it doing more damage than you’re saying because you’re not counting damage buffs or penetration.
I'm just using baseline figures.
Of course someone with 6k spell resist is going to take a lot more damage.
The proc is also doesn't interact properly with cp. Only the base damage is buffed/debuffed by cp. You'll always get a damage increase of 1720 per tick, regardless of the points you put in thaumaturge.
So I'd say that there might be something there to the stupid high damage numbers.
Being a Vamp is also going to get you rekt.
BGs brah, no CP aka Proc sets even more imbalanced
That's all I play, and I've only ever seen one 5 digit death recap for it.
Waffennacht wrote: »Waffennacht wrote: ».@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.
Except there’s images all over discord of it doing more damage than you’re saying because you’re not counting damage buffs or penetration.
I'm just using baseline figures.
Of course someone with 6k spell resist is going to take a lot more damage.
The proc is also doesn't interact properly with cp. Only the base damage is buffed/debuffed by cp. You'll always get a damage increase of 1720 per tick, regardless of the points you put in thaumaturge.
So I'd say that there might be something there to the stupid high damage numbers.
Being a Vamp is also going to get you rekt.
BGs brah, no CP aka Proc sets even more imbalanced
That's all I play, and I've only ever seen one 5 digit death recap for it.
I was responding to the CP and base damage buff/debuff comment you made. In BGs that's a moot point either way.
The fact it can even get past the 4 digit numbers is mind boggling to me for balance
Waffennacht wrote: »Waffennacht wrote: ».@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.
Except there’s images all over discord of it doing more damage than you’re saying because you’re not counting damage buffs or penetration.
I'm just using baseline figures.
Of course someone with 6k spell resist is going to take a lot more damage.
The proc is also doesn't interact properly with cp. Only the base damage is buffed/debuffed by cp. You'll always get a damage increase of 1720 per tick, regardless of the points you put in thaumaturge.
So I'd say that there might be something there to the stupid high damage numbers.
Being a Vamp is also going to get you rekt.
BGs brah, no CP aka Proc sets even more imbalanced
That's all I play, and I've only ever seen one 5 digit death recap for it.
I was responding to the CP and base damage buff/debuff comment you made. In BGs that's a moot point either way.
The fact it can even get past the 4 digit numbers is mind boggling to me for balance
Skoria is going to put out a similar amount of damage over the same time period, and has far less counterplay, does that make it broken?
Waffennacht wrote: »Waffennacht wrote: »Waffennacht wrote: ».@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.
Except there’s images all over discord of it doing more damage than you’re saying because you’re not counting damage buffs or penetration.
I'm just using baseline figures.
Of course someone with 6k spell resist is going to take a lot more damage.
The proc is also doesn't interact properly with cp. Only the base damage is buffed/debuffed by cp. You'll always get a damage increase of 1720 per tick, regardless of the points you put in thaumaturge.
So I'd say that there might be something there to the stupid high damage numbers.
Being a Vamp is also going to get you rekt.
BGs brah, no CP aka Proc sets even more imbalanced
That's all I play, and I've only ever seen one 5 digit death recap for it.
I was responding to the CP and base damage buff/debuff comment you made. In BGs that's a moot point either way.
The fact it can even get past the 4 digit numbers is mind boggling to me for balance
Skoria is going to put out a similar amount of damage over the same time period, and has far less counterplay, does that make it broken?
Some say yes, fun fact though, skoria requires Dots which in of itself is not accessible to all builds (at least easily), also doesn't provide quite the beneficial one piece. And quite frankly, still is outpaced by Zaan
Waffennacht wrote: »Waffennacht wrote: »Waffennacht wrote: ».@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.
Except there’s images all over discord of it doing more damage than you’re saying because you’re not counting damage buffs or penetration.
I'm just using baseline figures.
Of course someone with 6k spell resist is going to take a lot more damage.
The proc is also doesn't interact properly with cp. Only the base damage is buffed/debuffed by cp. You'll always get a damage increase of 1720 per tick, regardless of the points you put in thaumaturge.
So I'd say that there might be something there to the stupid high damage numbers.
Being a Vamp is also going to get you rekt.
BGs brah, no CP aka Proc sets even more imbalanced
That's all I play, and I've only ever seen one 5 digit death recap for it.
I was responding to the CP and base damage buff/debuff comment you made. In BGs that's a moot point either way.
The fact it can even get past the 4 digit numbers is mind boggling to me for balance
Skoria is going to put out a similar amount of damage over the same time period, and has far less counterplay, does that make it broken?
Some say yes, fun fact though, skoria requires Dots which in of itself is not accessible to all builds (at least easily), also doesn't provide quite the beneficial one piece. And quite frankly, still is outpaced by Zaan
I'd take 1 piece health over 1 piece spell crit any day of the week in PVP.
All I can really say is that if you are dying to someone with Zaan, then 9 times out of 10 they could have been running any other monster set, and still would have gotten the kill.
It's not at all like old Viper and Tremorscale where you had a huge amount of damage loaded onto a single spammable button, with zero counterplay.
Waffennacht wrote: »Waffennacht wrote: »Waffennacht wrote: »Waffennacht wrote: ».@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.
Except there’s images all over discord of it doing more damage than you’re saying because you’re not counting damage buffs or penetration.
I'm just using baseline figures.
Of course someone with 6k spell resist is going to take a lot more damage.
The proc is also doesn't interact properly with cp. Only the base damage is buffed/debuffed by cp. You'll always get a damage increase of 1720 per tick, regardless of the points you put in thaumaturge.
So I'd say that there might be something there to the stupid high damage numbers.
Being a Vamp is also going to get you rekt.
BGs brah, no CP aka Proc sets even more imbalanced
That's all I play, and I've only ever seen one 5 digit death recap for it.
I was responding to the CP and base damage buff/debuff comment you made. In BGs that's a moot point either way.
The fact it can even get past the 4 digit numbers is mind boggling to me for balance
Skoria is going to put out a similar amount of damage over the same time period, and has far less counterplay, does that make it broken?
Some say yes, fun fact though, skoria requires Dots which in of itself is not accessible to all builds (at least easily), also doesn't provide quite the beneficial one piece. And quite frankly, still is outpaced by Zaan
I'd take 1 piece health over 1 piece spell crit any day of the week in PVP.
All I can really say is that if you are dying to someone with Zaan, then 9 times out of 10 they could have been running any other monster set, and still would have gotten the kill.
It's not at all like old Viper and Tremorscale where you had a huge amount of damage loaded onto a single spammable button, with zero counterplay.
I'd prefer crit myself. Not gonna disagree that viper etc was Uber bad. Not gonna say Zaan doesn't have counters, but I will say Dive had counters, Trees had counters, Frag had counters, cloak had counters, etc etc
The proc is also doesn't interact properly with cp. Only the base damage is buffed/debuffed by cp. You'll always get a damage increase of 1720 per tick, regardless of the points you put in thaumaturge.
So I'd say that there might be something there to the stupid high damage numbers.
@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.
@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.