It provides free damage from any melee attack. PvPers despise free damage. In a game that relies so heavily on different stats contributing to your total damage, it's considered pretty cheesy to have a set that provides such a considerable boost to your burst damage.
I run 5xTBS, 5xViper, 1xKena, 1xBloodspawn.Trials Guilds don't use 5-piece Proc sets. They tend to use Night Mother's Gaze, Twice-Born Star, etc.
Those are sets that boost stats up, allowing for hogher sustained DPS.
imnotanother wrote: »It provides free damage from any melee attack. PvPers despise free damage. In a game that relies so heavily on different stats contributing to your total damage, it's considered pretty cheesy to have a set that provides such a considerable boost to your burst damage.
This is not the only set that allows for more damage, is it?
Cheesy? Damn tell that to any Trial Guild who picks the team by DPS test times.
Are all of the 5th bonuses on 5 piece sets considered "cheesy" for whatever boost they provide?
imnotanother wrote: »Ok, I can see where some of the frustration may come from. But in the end, the set is working as intended and not broken?
I could design an armor set that, say...whenever I light attack, everyone within a 1 mile radius dies instantly. If it did just that, it would certainly be working at intended. Just because something is working as intended does not mean it is balanced.imnotanother wrote: »Ok, I can see where some of the frustration may come from. But in the end, the set is working as intended and not broken?
I could design an armor set that, say...whenever I light attack, everyone within a 1 mile radius dies instantly. If it did just that, it would certainly be working at intended. Just because something is working as intended does not mean it is balanced.imnotanother wrote: »Ok, I can see where some of the frustration may come from. But in the end, the set is working as intended and not broken?
There is no what if or but about it. Just because a set has no bugs and functions as the description text says does not mean it is balanced. It was an example to prove a point. Just because Viper...does whatever it is viper is supposed to do doesn't mean it's balanced. Now is Viper was, for whatever reason, doing a % more damage than the tooltip said because of a typo in the code, then sure.imnotanother wrote: »I could design an armor set that, say...whenever I light attack, everyone within a 1 mile radius dies instantly. If it did just that, it would certainly be working at intended. Just because something is working as intended does not mean it is balanced.imnotanother wrote: »Ok, I can see where some of the frustration may come from. But in the end, the set is working as intended and not broken?
Uhh what set does that, Champ? Lets not turn this discussion into "what ifs and buts"
Skagsmasha wrote: »Bcuz you're using a "known" broken proc set... Expect the salt to be poured on!!!
There is no what if or but about it. Just because a set has no bugs and functions as the description text says does not mean it is balanced. It was an example to prove a point. Just because Viper...does whatever it is viper is supposed to do doesn't mean it's balanced. Now is Viper was, for whatever reason, doing a % more damage than the tooltip said because of a typo in the code, then sure.imnotanother wrote: »I could design an armor set that, say...whenever I light attack, everyone within a 1 mile radius dies instantly. If it did just that, it would certainly be working at intended. Just because something is working as intended does not mean it is balanced.imnotanother wrote: »Ok, I can see where some of the frustration may come from. But in the end, the set is working as intended and not broken?
Uhh what set does that, Champ? Lets not turn this discussion into "what ifs and buts"
When people say 'broken' they don't mean that the set is not functioning properly - more often than not, I've found, they mean that it is imbalanced.
Edit: Don't focus on the example, focus on the point I made. Geez.
imnotanother wrote: »Skagsmasha wrote: »Bcuz you're using a "known" broken proc set... Expect the salt to be poured on!!!
See, I have/had no idea it is broken. How is it broken? I am completely unaware. Is there a link to a ZOS staff member officially stating that it is broken?
starkerealm wrote: »There is no what if or but about it. Just because a set has no bugs and functions as the description text says does not mean it is balanced. It was an example to prove a point. Just because Viper...does whatever it is viper is supposed to do doesn't mean it's balanced. Now is Viper was, for whatever reason, doing a % more damage than the tooltip said because of a typo in the code, then sure.imnotanother wrote: »I could design an armor set that, say...whenever I light attack, everyone within a 1 mile radius dies instantly. If it did just that, it would certainly be working at intended. Just because something is working as intended does not mean it is balanced.imnotanother wrote: »Ok, I can see where some of the frustration may come from. But in the end, the set is working as intended and not broken?
Uhh what set does that, Champ? Lets not turn this discussion into "what ifs and buts"
When people say 'broken' they don't mean that the set is not functioning properly - more often than not, I've found, they mean that it is imbalanced.
Edit: Don't focus on the example, focus on the point I made. Geez.
Yeah, but your example was so ripe for mocking.
In fairness, you had a legitimate point. A poor example, but a legitimate point.
The set is broken in the context of being a balancing issue.
starkerealm wrote: »There is no what if or but about it. Just because a set has no bugs and functions as the description text says does not mean it is balanced. It was an example to prove a point. Just because Viper...does whatever it is viper is supposed to do doesn't mean it's balanced. Now is Viper was, for whatever reason, doing a % more damage than the tooltip said because of a typo in the code, then sure.imnotanother wrote: »I could design an armor set that, say...whenever I light attack, everyone within a 1 mile radius dies instantly. If it did just that, it would certainly be working at intended. Just because something is working as intended does not mean it is balanced.imnotanother wrote: »Ok, I can see where some of the frustration may come from. But in the end, the set is working as intended and not broken?
Uhh what set does that, Champ? Lets not turn this discussion into "what ifs and buts"
When people say 'broken' they don't mean that the set is not functioning properly - more often than not, I've found, they mean that it is imbalanced.
Edit: Don't focus on the example, focus on the point I made. Geez.
Yeah, but your example was so ripe for mocking.
In fairness, you had a legitimate point. A poor example, but a legitimate point.
The set is broken in the context of being a balancing issue.
imnotanother wrote: »Skagsmasha wrote: »Bcuz you're using a "known" broken proc set... Expect the salt to be poured on!!!
See, I have/had no idea it is broken. How is it broken? I am completely unaware. Is there a link to a ZOS staff member officially stating that it is broken?
starkerealm wrote: »There is no what if or but about it. Just because a set has no bugs and functions as the description text says does not mean it is balanced. It was an example to prove a point. Just because Viper...does whatever it is viper is supposed to do doesn't mean it's balanced. Now is Viper was, for whatever reason, doing a % more damage than the tooltip said because of a typo in the code, then sure.imnotanother wrote: »I could design an armor set that, say...whenever I light attack, everyone within a 1 mile radius dies instantly. If it did just that, it would certainly be working at intended. Just because something is working as intended does not mean it is balanced.imnotanother wrote: »Ok, I can see where some of the frustration may come from. But in the end, the set is working as intended and not broken?
Uhh what set does that, Champ? Lets not turn this discussion into "what ifs and buts"
When people say 'broken' they don't mean that the set is not functioning properly - more often than not, I've found, they mean that it is imbalanced.
Edit: Don't focus on the example, focus on the point I made. Geez.
Yeah, but your example was so ripe for mocking.
In fairness, you had a legitimate point. A poor example, but a legitimate point.
The set is broken in the context of being a balancing issue.
Admittedly I probably should've just used Viper as an example, but I try to go to extremes for examples - I've found it helps people understand the point I'm trying to make. But, blah, I always forget people can veer off course and focus on the example...my badstarkerealm wrote: »There is no what if or but about it. Just because a set has no bugs and functions as the description text says does not mean it is balanced. It was an example to prove a point. Just because Viper...does whatever it is viper is supposed to do doesn't mean it's balanced. Now is Viper was, for whatever reason, doing a % more damage than the tooltip said because of a typo in the code, then sure.imnotanother wrote: »I could design an armor set that, say...whenever I light attack, everyone within a 1 mile radius dies instantly. If it did just that, it would certainly be working at intended. Just because something is working as intended does not mean it is balanced.imnotanother wrote: »Ok, I can see where some of the frustration may come from. But in the end, the set is working as intended and not broken?
Uhh what set does that, Champ? Lets not turn this discussion into "what ifs and buts"
When people say 'broken' they don't mean that the set is not functioning properly - more often than not, I've found, they mean that it is imbalanced.
Edit: Don't focus on the example, focus on the point I made. Geez.
Yeah, but your example was so ripe for mocking.
In fairness, you had a legitimate point. A poor example, but a legitimate point.
The set is broken in the context of being a balancing issue.
He doesn't even seem to have read most of my posts. Not my fault *sobs in corner* Oh well.
imnotanother wrote: »So I've be wearing a 5 piece set of Viper for the last 8 months or so. I used to do trials a lot and the crew was all about DPS.
Now I haven't changed my gear since last April, so I guess I might be out of the loop (took a couple months off).
I only wear PVE gear because that is all I do. Every once in awhile I am challenged to a duel. But if I heavy attack and Viper procs, I usually get a salty whisper about my lack of skill and my worthlessness.
Am I missing something?
I feel like it is quite fair to wear any gear that is available. But is this set broken?
Dagoth_Rac wrote: »imnotanother wrote: »Skagsmasha wrote: »Bcuz you're using a "known" broken proc set... Expect the salt to be poured on!!!
See, I have/had no idea it is broken. How is it broken? I am completely unaware. Is there a link to a ZOS staff member officially stating that it is broken?
Yes, ZOS have stated on numerous occasions that they are aware that proc sets are a problem in PvP. This thread, in particular:
https://forums.elderscrollsonline.com/en/discussion/301699/proc-sets/p1
Comment #59 is from Gina where she confirms it is a problem and they are working on solutions. In the next Update, they are removing the ability of Viper (and other proc sets) to do critical damage, in an attempt to reduce the burst damage. Rich talks about that here:
https://forums.elderscrollsonline.com/en/discussion/310623/update-13-sneak-peak-notes/p1
A lot of players are of the opinion that a blanket removal of critical damage from all set bonuses is a lazy fix that ruins a lot of sets that do not have the burst potential of Viper, Selene, Tremorscale, Velidreth, etc. But those are arguments about the solution. No one is really arguing against proc sets being more powerful than intended in PvP. That is kind of a given.
I think this is more of the problem then what the other poster said.starkerealm wrote: »Or it could just be that the proc sets are cancer, that's an option too.
Skagsmasha wrote: »Bcuz you're using a "known" broken proc set... Expect the salt to be poured on!!!
imnotanother wrote: »It provides free damage from any melee attack. PvPers despise free damage. In a game that relies so heavily on different stats contributing to your total damage, it's considered pretty cheesy to have a set that provides such a considerable boost to your burst damage.
This is not the only set that allows for more damage, is it?
Cheesy? Damn tell that to any Trial Guild who picks the team by DPS test times.
Are all of the 5th bonuses on 5 piece sets considered "cheesy" for whatever boost they provide?