Aww did a proc sets touch you in the booty?
I'm kidding but just think about if they didn't exist in the current game. Who kills magsorcs most of the time? And why is it mostly just stamblades?
A sorc can outshield every other classes dps besides stamblade because they can fear them and burst their shields and MAYBE then kill them after that.
A world without stamblades running proc sets is a sorcs world until they nerf sorc.
That sounds really nice if you can back up the implication that proc sets are not a problem for game balance.
Also there is such huge irony in you lamenting the death of skillful play while implying proc sets are fine if we just stopped whining and adapted.
But by all means back up your sweeping moral judgments with some facts and reasoning. Just might save us meta slave peasants from being trash.
Youre supposing that proc sets ARE a problem for game balance with no evidence yourself. Its pretty rich you would demand it from me but I'll insert an indisputable fact that might throw a monkey wrench into your logic.
Players wear the armor.
I know right? PLAYERS ARE RESPONSIBLE FOR THE OUTCOME OF HOW THEY PLAY THE GAME.
Its probably not what you wanted to hear but its 100% on you that proc sets are a problem for you. So rather than take responsibility for your shortcomings in this particular vein, you want to impose a game wide change to accommodate your issue.
Thats the epitome of selfishness and to boot you want ME TO PROVIDE PROOF that your issue isnt a problem for game balance. GTFO
https://www.youtube.com/watch?v=ERygtg_el68
My personal ideas for some of the proc-sets (because that´s what some sets needs: Individual treatment, not a global *** fix that won´t solve anything):
* Tremorscale: Rework so that players aren´t considered "tauntable". Increase the damage to compensate so that tremorscale can be somewhat viable in PvE for those tanks that want to do some damage.
* Viper: Make this set an actual proc-set (100% chance every 4 seconds isn´t a proc-set). Make it so that you have 8% chance to do X amount of damage on direct melee damage, can occur every 7-8 seconds.
* Selenes: Reduce the proc-chance and lower the damage significantly.
My personal ideas for some of the proc-sets (because that´s what some sets needs: Individual treatment, not a global *** fix that won´t solve anything):
* Tremorscale: Rework so that players aren´t considered "tauntable". Increase the damage to compensate so that tremorscale can be somewhat viable in PvE for those tanks that want to do some damage.
* Viper: Make this set an actual proc-set (100% chance every 4 seconds isn´t a proc-set). Make it so that you have 8% chance to do X amount of damage on direct melee damage, can occur every 7-8 seconds.
* Selenes: Reduce the proc-chance and lower the damage significantly.
Lol..
Tremor is fine as it is..
Viper should maybe have a 15% chance every 4 second on melee dmg.
Your suggestions make them totally useless.
leepalmer95 wrote: »My personal ideas for some of the proc-sets (because that´s what some sets needs: Individual treatment, not a global *** fix that won´t solve anything):
* Tremorscale: Rework so that players aren´t considered "tauntable". Increase the damage to compensate so that tremorscale can be somewhat viable in PvE for those tanks that want to do some damage.
* Viper: Make this set an actual proc-set (100% chance every 4 seconds isn´t a proc-set). Make it so that you have 8% chance to do X amount of damage on direct melee damage, can occur every 7-8 seconds.
* Selenes: Reduce the proc-chance and lower the damage significantly.
Lol..
Tremor is fine as it is..
Viper should maybe have a 15% chance every 4 second on melee dmg.
Your suggestions make them totally useless.
How exactly are you taunting players? Tremor needs a rework as a set, the snare needs to go from 70% as well, it's a joke.
My personal ideas for some of the proc-sets (because that´s what some sets needs: Individual treatment, not a global *** fix that won´t solve anything):
* Tremorscale: Rework so that players aren´t considered "tauntable". Increase the damage to compensate so that tremorscale can be somewhat viable in PvE for those tanks that want to do some damage.
* Viper: Make this set an actual proc-set (100% chance every 4 seconds isn´t a proc-set). Make it so that you have 8% chance to do X amount of damage on direct melee damage, can occur every 7-8 seconds.
* Selenes: Reduce the proc-chance and lower the damage significantly.
Lol..
Tremor is fine as it is..
Viper should maybe have a 15% chance every 4 second on melee dmg.
Your suggestions make them totally useless.
My personal ideas for some of the proc-sets (because that´s what some sets needs: Individual treatment, not a global *** fix that won´t solve anything):
* Tremorscale: Rework so that players aren´t considered "tauntable". Increase the damage to compensate so that tremorscale can be somewhat viable in PvE for those tanks that want to do some damage.
* Viper: Make this set an actual proc-set (100% chance every 4 seconds isn´t a proc-set). Make it so that you have 8% chance to do X amount of damage on direct melee damage, can occur every 7-8 seconds.
* Selenes: Reduce the proc-chance and lower the damage significantly.
Lol..
Tremor is fine as it is..
Viper should maybe have a 15% chance every 4 second on melee dmg.
Your suggestions make them totally useless.
Even though I´m not stating any specific number my suggestions make them more balanced for PvP. And your suggestion about viper is the same as mine just written in another way......so not sure what you´re ranting about...
Waffennacht wrote: »Aww did a proc sets touch you in the booty?
I'm kidding but just think about if they didn't exist in the current game. Who kills magsorcs most of the time? And why is it mostly just stamblades?
A sorc can outshield every other classes dps besides stamblade because they can fear them and burst their shields and MAYBE then kill them after that.
A world without stamblades running proc sets is a sorcs world until they nerf sorc.
They don't have to absolutely abolish anything. They won't be removed, and they won't be nuked into insignificance, I'm expecting a shield duration type change
murdomac101 wrote: »If they nerf any sets significantly (which I have no problem with) then I think we should get all our tempers and tannins back.
Scyantific wrote: »They either need to add a global cooldown to damage proc sets (because they better not touch stuff like Kena/Ravager), or they need to make all direct damage proc-sets work on a condition (i.e. must be using DoTs for Skoria, weapon skills for Red Mountain/Way of the Fire). As far as Tremorscale goes, pick either the damage or the snare, can't have both on the set.
* Tremorscale: Rework so that players aren´t considered "tauntable". Increase the damage to compensate so that tremorscale can be somewhat viable in PvE for those tanks that want to do some damage.
MurderMostFoul wrote: »
MurderMostFoul wrote: »
Actually yes, it is.
Go run a tank for a bit in PvP. It might be a good change of pace for ya.
Scyantific wrote: »They either need to add a global cooldown to damage proc sets (because they better not touch stuff like Kena/Ravager), or they need to make all direct damage proc-sets work on a condition (i.e. must be using DoTs for Skoria, weapon skills for Red Mountain/Way of the Fire). As far as Tremorscale goes, pick either the damage or the snare, can't have both on the set.
I would like to add a condition to Viper stating that it only procs when the target is CC'd. This would not allow Viper to proc more than you can get CC'd and require impeccable timing.
Scyantific wrote: »They either need to add a global cooldown to damage proc sets (because they better not touch stuff like Kena/Ravager), or they need to make all direct damage proc-sets work on a condition (i.e. must be using DoTs for Skoria, weapon skills for Red Mountain/Way of the Fire). As far as Tremorscale goes, pick either the damage or the snare, can't have both on the set.
I would like to add a condition to Viper stating that it only procs when the target is CC'd. This would not allow Viper to proc more than you can get CC'd and require impeccable timing.
DTStormfox wrote: »Scyantific wrote: »They either need to add a global cooldown to damage proc sets (because they better not touch stuff like Kena/Ravager), or they need to make all direct damage proc-sets work on a condition (i.e. must be using DoTs for Skoria, weapon skills for Red Mountain/Way of the Fire). As far as Tremorscale goes, pick either the damage or the snare, can't have both on the set.
I would like to add a condition to Viper stating that it only procs when the target is CC'd. This would not allow Viper to proc more than you can get CC'd and require impeccable timing.
Incapstrike (stun) > Viper > Selenes/Velindreth > Execute
Still OP
DTStormfox wrote: »Scyantific wrote: »They either need to add a global cooldown to damage proc sets (because they better not touch stuff like Kena/Ravager), or they need to make all direct damage proc-sets work on a condition (i.e. must be using DoTs for Skoria, weapon skills for Red Mountain/Way of the Fire). As far as Tremorscale goes, pick either the damage or the snare, can't have both on the set.
I would like to add a condition to Viper stating that it only procs when the target is CC'd. This would not allow Viper to proc more than you can get CC'd and require impeccable timing.
Incapstrike (stun) > Viper > Selenes/Velindreth > Execute
Still OP
DTStormfox wrote: »Scyantific wrote: »They either need to add a global cooldown to damage proc sets (because they better not touch stuff like Kena/Ravager), or they need to make all direct damage proc-sets work on a condition (i.e. must be using DoTs for Skoria, weapon skills for Red Mountain/Way of the Fire). As far as Tremorscale goes, pick either the damage or the snare, can't have both on the set.
I would like to add a condition to Viper stating that it only procs when the target is CC'd. This would not allow Viper to proc more than you can get CC'd and require impeccable timing.
Incapstrike (stun) > Viper > Selenes/Velindreth > Execute
Still OP
That would be the point... You couldn't proc it again until the target could be CC'd. The burst is working as it should, the issue is the sustain.