The pull radius of Rush of Agony needs fixing

OnGodiDoDis · May 30

This set has been a problem for many months now and very little has been done to make it less toxic. One of the biggest issues is that the game allows for multiple chained pulls because this set does not grant CC immunity to those affected. As with every "pull" set, there is always a counter argument to "not zerg" or to not "stack on flags".

This is a screenshot of Rush of Agony just as it pulls nearby players. The hardly visible, bright orange line connecting me to the yellow player is the chain. I was neither
zerging, stacking on flags, or anywhere near close to that player. The pull range of this set is way beyond the effective damage radius. It needs to be fixed. Dark Convergence had its pull radius adjusted to match its damage radius. Do that to rush of agony. The utility that this set has, beyond dealing, damage is absolutely ridiculous. Now imagine dealing with a ballgroup with 4 people running this set. This is what we are dealing with in Cyrodiil and I don't understand the stubbornness of refusing to adjust sets like these, or even the audacity to keep introducing new ones. Ball groups are more than capable of killing everyone without pull sets, so why make it easier for them? Once again, being in large groups should impose penalties on their members. Having pull sets disabled for large groups should be one of those penalties. You did it for torc of the ayleid king in bgs and no cp. You can do it for large groups as well.

cuddles_with_wroble · May 31

One of the biggest issues is that it pulls based on where you were when the gap closer was cast and it doesn’t take into account where you are when the chain actually connects to pull you

OnGodiDoDis · June 2

Here is another example of the overtuned pull radius. The bright yellow/orange dot right above my head is the tip of the chain, meaning it has registered me to be within its pulled radius although it has not yet reached me in this frame. The person that pulled is the one with the missing health, so they were very far away. We need more time to react to the pull. The time window from when we see/hear the chain to when we get pulled is almost instantaneous.

OnGodiDoDis · June 2

cuddles_with_wroble wrote: »

One of the biggest issues is that it pulls based on where you were when the gap closer was cast and it doesn’t take into account where you are when the chain actually connects to pull you

Yes, I think I have noticed something weird with the calculations of the system. I have also been pulled WHILE I am rolling, meaning the pull not only doesn't grant CC immunity, it ignores DODGE. I don't know of anything else in the game that ignores dodge.

Durham · June 2

They do not read the forums and they do not care about PVP balance atm. This set has been a bane in PVP for a year now. It has caused more people to leave PVP than anything I have seen since the unkillable DK Vampires back in 2015.

If Im killed in PVP, it's usually because of this set. Lag + streak sometimes Im pulled from as far as 22 meters away. Usually, some nightblade with 22-25k health is pulled with me, and I get a good case of Vicious death! Im insta killed by proc damage mostly and then Im tea bagged by the person that did less than half their damage using their abilities, and over 50% is from sets and proc damage.

This game is Proc v Proc atm. What gets you killed are new players that come in with 20k health (Great game design)

Durham · June 2

There are also cases of cross alliance proc teaming

Thumbless_Bot · June 2

Durham wrote: »

They do not read the forums and they do not care about PVP balance atm. This set has been a bane in PVP for a year now. It has caused more people to leave PVP than anything I have seen since the unkillable DK Vampires back in 2015.

If Im killed in PVP, it's usually because of this set. Lag + streak sometimes Im pulled from as far as 22 meters away. Usually, some nightblade with 22-25k health is pulled with me, and I get a good case of Vicious death! Im insta killed by proc damage mostly and then Im tea bagged by the person that did less than half their damage using their abilities, and over 50% is from sets and proc damage.

This game is Proc v Proc atm. What gets you killed are new players that come in with 20k health (Great game design)

They've said they are going to address the set in due time... about 3 months ago maybe. This is at least acknowledgement that the set is not working right but they also indicated that they understand, even when it works as intended, its cracked. I cant find the thread but its here... somewhere.

OnGodiDoDis · June 3

Another big issue is that this set favors night blades (once again). The same problem arose with Caluurion's. Of course, any class could use Caluurion's but its proc condition could only be abused by NBs. The same goes for Rush of Agony. NBs are able to sneak up on groups of players, kill them, and then run away just to do it again in 30 seconds. There are so many failed attempts at taking a keep with groups when we get bombed by 2 people. Players should not be allowed to cloak while wearing this set. We need to be able to kill them the same way they do to everyone else. There is a drastic imbalance in power that favors NB bombers using this set.

OnGodiDoDis · June 7

Another issue with this set it that it allows people to keep bombing over and over again with the help from the Combat Frenzy passive, granting them 20 ultimate per each person killed. This results in an endless cycle of bombs by the same few people over and over until they completely wipe the opposition. This has been the dominant style of gameplay for years. You build ultimate, you press two buttons and wipe a few people, you cloak and hide to build ultimate, and you do it again until you win. This is the exact same brain-dead playstyle that ganking accomplishes. The entire nightblade playstyle has been ruined by encouraging perma-cloak builds, and it has ruined the cyrodiil experience along with it. These types of sets would not be as problematic if we had time to react or if we had reliable means to counter them. The root lies in the fact that NBs can use these sets while cloaked.

Joy_Division · June 9

Thumbless_Bot wrote: »

Durham wrote: »

They do not read the forums and they do not care about PVP balance atm. This set has been a bane in PVP for a year now. It has caused more people to leave PVP than anything I have seen since the unkillable DK Vampires back in 2015.

If Im killed in PVP, it's usually because of this set. Lag + streak sometimes Im pulled from as far as 22 meters away. Usually, some nightblade with 22-25k health is pulled with me, and I get a good case of Vicious death! Im insta killed by proc damage mostly and then Im tea bagged by the person that did less than half their damage using their abilities, and over 50% is from sets and proc damage.

This game is Proc v Proc atm. What gets you killed are new players that come in with 20k health (Great game design)

They've said they are going to address the set in due time... about 3 months ago maybe. This is at least acknowledgement that the set is not working right but they also indicated that they understand, even when it works as intended, its cracked. I cant find the thread but its here... somewhere.

No they didn't. They said that even after their "fix" you're still going to get pulled through walls. That is not addressing the issue. They are ignoring the most complained about aspects of the set. That is a more accurate assessment of their commentary.

Thumbless_Bot · June 9

Joy_Division wrote: »

Thumbless_Bot wrote: »

Durham wrote: »

They do not read the forums and they do not care about PVP balance atm. This set has been a bane in PVP for a year now. It has caused more people to leave PVP than anything I have seen since the unkillable DK Vampires back in 2015.

If Im killed in PVP, it's usually because of this set. Lag + streak sometimes Im pulled from as far as 22 meters away. Usually, some nightblade with 22-25k health is pulled with me, and I get a good case of Vicious death! Im insta killed by proc damage mostly and then Im tea bagged by the person that did less than half their damage using their abilities, and over 50% is from sets and proc damage.

This game is Proc v Proc atm. What gets you killed are new players that come in with 20k health (Great game design)

They've said they are going to address the set in due time... about 3 months ago maybe. This is at least acknowledgement that the set is not working right but they also indicated that they understand, even when it works as intended, its cracked. I cant find the thread but its here... somewhere.

No they didn't. They said that even after their "fix" you're still going to get pulled through walls. That is not addressing the issue. They are ignoring the most complained about aspects of the set. That is a more accurate assessment of their commentary.

Can't argue with this. I would like to say I hope they take all feedback into consideration inclu8dng yours, mine and the feedback from people that love the set.

RaidingTraiding · June 15

yeah they said they were going to fix the desync issues with it. I highly doubt it, the desync issues in the game now are everywhere it's not just a problem with this set, although this set causes the most issues. So if they hope to fix the desync they'd have to fix desync in general. sorry but that's not happening. And the desync isn't really the only problem here no matter what they tell you. the actual set even if it worked properly is bad for pvp. like others have said this set alone has caused more people to leave than anything else in the history of the game. i played in greyhost last friday, and even with subclassing out, during primetime it was still hard to find good fights. kind of ridiculous that it can get that dead in the main campaign. even blackreach on fridays usually was poplocked with tons of fights and this last friday it was 1 bar across the board. nobody likes playing against something with no counterplay, and whoever just tells you to "just hold block" is just an abuser of this set. good luck blocking with all the desync and lag.

AngryPenguin · June 15

They know. The issue has been brought up since before the set was even released.

If they cared it would have been fixed within a couple months of RoA release.