Oh - so the problem isn't that it's bugged, the problem is that it's working correctly, but there its an unexpected interaction with a small set of other abilities that make this proc over and over much more quickly than intended in those cases.
Ok, I get it. Yes, there should be definitely be a 1 sec ICD on this boon between stacks.
Why do you guys make it so difficult? do you have serious reading comprehension? at this point you are BOTH totally wrong and not even contributing to the thread.
1. You went and tested the bug VS NPC MOBS, you CLEARLY haven't read the original post.
2. it DOES multiprocc, SW is the ONE CAUSING IT, NOT THE OTHER WAY AROUND, jesus my brain hurts just from typing this to you, how can you be so daft?
Let me repeat it once again: SW puts out MASSIVE dot amount on the enemy players at a VERY fast pace, at some point, the avalanche stacks built on the ENEMY are REFLECTED back to the WARLOCK are MULTIPROCCED.
There are logs and pictures with timestamps and highlighted multiprocs, now go do your test properly when YOU are the attacker (spec to fury) and come back with the results.
Not sure why I'm replying here, but... First off, I've been personally responsible for a number of fixes being put in place in the last few weeks alone - including SW ones. Why? Because I do rigorous testing. I don't jump to conclusions because the data seems to indicate what I want it to indicate. I perform focused and specific experiments in order to isolate the root cause of some observed behavior. Then, if I do find there is a defect, I write out a formal report. Guess what, Vorpal/Terror fix? My report. Harrowstorm? Mine too. There's many more. So, maybe you should take a deep breath and think a little bit before popping this attitude with people trying to actually help.
The problem is, the data you've posted here doesn't indicate anything other than Avalanche is responsible for a lot of damage. I also see in your table any number of other feats, abilities, gear, what have you that could potentially also be contributing. All I see you doing here is throwing piles of data that may, or may not be, relevant to an issue that appears to cause Avalanch to proc a lot. What I have shown here is that it doesn't appear to be malfunctioning on it's own, which means it needs to be tested in a different way. I should add that what I did here is step one in standard QA - which means, under normal circumstances, a QA staffer would probably have said as I did - WAI - time to move on to my other 300 items to test. Now, I don't have 300 QA tickets to pound though, since I'm not a QA staffer and I can see, despite your foolish and thoroughly insulting comments, that there's more to this than a simple defect in the Avalanche feat. In fact, as I said, it doesn't appear the problem is actually anything to do with Avalanche itself, I think it probably is working as intended. The problem is most likely an unintended consequence of it's interaction with other abilities. But, without focused testing, it's too early to say for sure.
However, crying about it on the forum will do you no good. Presenting a disjointed rant that shows psudo-data that include piles of other powers and gear that would make QA have to go through an immense effort to validate a report also will do you no good. Showing the PvP leaderboard is irrelevant and again, does you no good. Calling me names will do you no good. Your assumptions are flawed and so is your data. The end conclusion, that Avalanche is causing too much damage is probably correct - but you haven't tried to explain why you just came here to complain about it.
I don't complain about it. I figure out what's really happening and present Cryptic (directly, I might add) with formal reports that they can easily and quickly validate internally so the devs can get a fix in. That's what I do. So... there's you... complains and rants. Then there's me... logical testing and a track record of actually helping get bugs fixed.
Now... I suggest you stop insulting me and others, drop the angry attitude and see about being constructive, or I have a hunch this thread won't be long for this world. Here's where we test your "reading comprehension" -- before you reply, please re-read that last sentence.
Lets get some facts straight, since you seem to be skipping steps of what QA goes through.
First the BUGS are reported by the COSTUMERS, usually in a very poorly written mails or tickets, QA's job is to DECIPHER those complaints and submit a formal ticket (using jira for examle) to the DEV team, it is NOT the customer's responsibility to write formal and structured tickets. (you expect every non professional person to know how to submit a bug report, nice joke).
Now regarding your "achievements", I don't see anything that you did, all i see is you hijacking other threads and reposting the same thing with better formatting, you didn't actually stumble upon the bugs, you just retest them after someone else already did.
All QA person needs to do is read the encounter description, put 1+1 and submit a bug report to DEV, this is how it works in every major corporate. So who's to say you had a direct impact on that? strum the community manager THANKED ALL in that thread he confirmed devs know about the issue.
The fact that they have their own agenda and prioritize bugs at the bottom of the list shows you who we're dealing with, this company has a track record of failing addressing major bugs, are you going to say that's all because of badly formatted threads? step off your high horse m8.
Now I don't want to discuss this any further, this thread is the biggest reason SW under performs in PVP, when they ever decide to look at class balance, this issue will be unavoidable, plus, every SW in the top 10 leaderboard will indicate the same issue, that's why I'm not worried how I phrase my complaints, It doesn't matter if no one is giving it any attention anyway.
It's a LOGICAL problem that QA should pick up on; a boon that was BUFFED with mod6, that reflects upto 20k dmg when reaching certain amount of stacks, having classes like SW/HR was an overlooked issue.
It's not a gamer's job to be QA, it's QA's job.
(for the record I never insulted you, I just questioned you, you chose to be offended).
Writing gobbledygook and expecting QA to decipher it is why things don't get done fast. Writing solid reports that clearly - emphasis on clearly - explain the problem helps immensely. Not sure how much IT/dev experience you have (I've been at it for more than 15 years now), but I can tell you - it takes WAY more time to troubleshoot a potential defect if the report has to be decrypted first. If you want fast action, put as much effort into writing a clear report as you put into getting indignant in this thread and you might actually be amazed. Keep acting like a spoiled brat and frankly you can expect nothing. Clearly you didn't read my second to last sentence... This thread has devolved into a flame war, and it should be closed.
Jumping in here. Let's just all calm down and get this bug fixed. True QA usually needs to decipher player reports with what is given - as is their job - but it also helps them if there are repro steps involved as it may take a long time to reproduce a bug based solely on halo testing. That being said, I'll send this off to QA. Sorry for not doing so earlier. My apologies.
Call me Andy (or Strum, or Spider-Man)! Follow Neverwinter on Twitter: NeverwinterGame Like Neverwinter on Facebook: Neverwinter Follow me on Twitter: StrumSlinger
Not sure why I'm replying here, but... First off, I've been personally responsible for a number of fixes being put in place in the last few weeks alone - including SW ones. Why? Because I do rigorous testing. I don't jump to conclusions because the data seems to indicate what I want it to indicate. I perform focused and specific experiments in order to isolate the root cause of some observed behavior. Then, if I do find there is a defect, I write out a formal report. Guess what, Vorpal/Terror fix? My report. Harrowstorm? Mine too. There's many more. So, maybe you should take a deep breath and think a little bit before popping this attitude with people trying to actually help.
Your arrogance nullifies your entire post. Why don't you think a little bit before popping that attitude with people who have done more testing than you have?
The problem is, the data you've posted here doesn't indicate anything other than Avalanche is responsible for a lot of damage. I also see in your table any number of other feats, abilities, gear, what have you that could potentially also be contributing. All I see you doing here is throwing piles of data that may, or may not be, relevant to an issue that appears to cause Avalanch to proc a lot. What I have shown here is that it doesn't appear to be malfunctioning on it's own, which means it needs to be tested in a different way. I should add that what I did here is step one in standard QA - which means, under normal circumstances, a QA staffer would probably have said as I did - WAI - time to move on to my other 300 items to test. Now, I don't have 300 QA tickets to pound though, since I'm not a QA staffer and I can see, despite your foolish and thoroughly insulting comments, that there's more to this than a simple defect in the Avalanche feat. In fact, as I said, it doesn't appear the problem is actually anything to do with Avalanche itself, I think it probably is working as intended. The problem is most likely an unintended consequence of it's interaction with other abilities. But, without focused testing, it's too early to say for sure.
Okay. Let's iron the facts out:
a) At 20 stacks, avalanche can and will multiproc upwards of 15 times sometimes, because of the amount of dots that are on the target will activate it at the same time
b) Avalanche has no ICD between gaining stacks, which means the above issue is even worse because it's not something you can time to avoid
However, crying about it on the forum will do you no good. Presenting a disjointed rant that shows psudo-data that include piles of other powers and gear that would make QA have to go through an immense effort to validate a report also will do you no good. Showing the PvP leaderboard is irrelevant and again, does you no good. Calling me names will do you no good. Your assumptions are flawed and so is your data. The end conclusion, that Avalanche is causing too much damage is probably correct - but you haven't tried to explain why you just came here to complain about it.
I don't complain about it. I figure out what's really happening and present Cryptic (directly, I might add) with formal reports that they can easily and quickly validate internally so the devs can get a fix in. That's what I do. So... there's you... complains and rants. Then there's me... logical testing and a track record of actually helping get bugs fixed.
Now... I suggest you stop insulting me and others, drop the angry attitude and see about being constructive, or I have a hunch this thread won't be long for this world. Here's where we test your "reading comprehension" -- before you reply, please re-read that last sentence.
First of all, your attitude of "I get things fixed and you don't because I can engrish and you don't" is really really annoying, please kindly drop it or shut up. Secondly, these aren't assumptions, they're conclusions and facts that HAVE BEEN TESTED NUMEROUS TIMES BY SEVERAL DIFFERENT PEOPLE.
This data has been tested by many top PvPers, SWs and other players. People don't need to work in IT for 15 years to understand how a game works - they understand it because they're smart players and know what to test. On the other hand, people who work in IT for 15 years may still need experience to understand how a game works. Spurting BS about "this is how QA works" doesn't make you any better in anyone's eyes - not mine, not any respectable/intelligent/good player in the game, or anyone else for that matter. It just makes you a prick.
I know you're a PvE player with a PvE mindset, but this is a PvP thread. Keep your PvE testing where it belongs please, and don't provide misinformation.
As for testing and evidence:
A GF sat and blocked the whole time (testing in DV), while a SW basically unloaded rotation on him. This was the overall damage:
That was with the GF BLOCKING and only hit once with anvil for 17k. The rest was avalanche damage mostly.
The GF's outgoing damage:
This is the SW's total stats:
This is part of the avalanche ticks that took place. Note the timestamps:
ALL they need to do is put a 1 sec ICD on the stacks. Makes it a MIN 20 sec icd by default and I SUSPECT that alone might also remove the multi proc issues as well. Not 100% sure there but id suspect atleast a 50-50 chance it would remove the multi proc issue. Atleast a 1 sec ICD on gaining stacks would make it more manageable so even if it DID multiproc it wouldnt be AS bad as it is here where its proccing every 3-5 seconds against an SW....
No problem! Also, I will say that @kvet has actually been very helpful in squishing bugs and has indeed helped QA out a lot with his reports.
Call me Andy (or Strum, or Spider-Man)! Follow Neverwinter on Twitter: NeverwinterGame Like Neverwinter on Facebook: Neverwinter Follow me on Twitter: StrumSlinger
Thanks @martianmnhunter for posting and persevering with this avalanche thread and @ralexinor for posting even more evidence. Sounds like a fix should be on the way soon.
You know, technically its over TWO seconds not one. So its only HALF as OP as you think it is ^^ hahahaha jk.
Yeah this seriously needs a fix. Like I said I would BET that just swapping this to an ICD could potentially fix this. How many abilities that have ICDs end up multi-proccing? My guess is its something to do with the lack of ICD that causes the multiproc issue.
Okay SIX procs for one stack dump... my that is a juicy one...90k premitigated burst damage for a passive boon.
Seems like there must be a delay from reaching 20 stacks to the avalanche dmg proc. tic tic tic tic tic tic tic (20 stacks reached..,, tic tic tic tic tic,,,, dumps 6 times) tic tic tic tic tic
Can we get a confirmation from devs if this is ever going to be addressed?
0
silverkeltMember, NW M9 PlaytestPosts: 4,235Arc User
I dont have a comment on avalanche.. but I do have a comment on naming and shaming and its not allowed, all posts with direct names need to be removed, you can go post those on the other site if you wish.
I do not understand why this was allowed to continue.
I dont have a comment on avalanche.. but I do have a comment on naming and shaming and its not allowed, all posts with direct names need to be removed, you can go post those on the other site if you wish.
I do not understand why this was allowed to continue.
I'm not sure you even understand what naming and shaming means.
Where do you see me shaming anyone? My agenda is not against PLAYERS it's against GAME MECHANICS. Why would I use my guildmate as example to shame him? seriously just gtfo, tired of sjw everywhere.
0
silverkeltMember, NW M9 PlaytestPosts: 4,235Arc User
No, the terms dont allow for your intent, that is the difference the protection is for everyone. I simply don't understand why names couldn't be removed for purposes of the posting.
No, the terms dont allow for your intent, that is the difference the protection is for everyone. I simply don't understand why names couldn't be removed for purposes of the posting.
Because it's called Naming AND Shaming, it's not OR, it's BOTH. If we followed your logic, every post in the showcase forum would need to be deleted.
Comments
Dude, you have issues.
The problem is, the data you've posted here doesn't indicate anything other than Avalanche is responsible for a lot of damage. I also see in your table any number of other feats, abilities, gear, what have you that could potentially also be contributing. All I see you doing here is throwing piles of data that may, or may not be, relevant to an issue that appears to cause Avalanch to proc a lot. What I have shown here is that it doesn't appear to be malfunctioning on it's own, which means it needs to be tested in a different way. I should add that what I did here is step one in standard QA - which means, under normal circumstances, a QA staffer would probably have said as I did - WAI - time to move on to my other 300 items to test. Now, I don't have 300 QA tickets to pound though, since I'm not a QA staffer and I can see, despite your foolish and thoroughly insulting comments, that there's more to this than a simple defect in the Avalanche feat. In fact, as I said, it doesn't appear the problem is actually anything to do with Avalanche itself, I think it probably is working as intended. The problem is most likely an unintended consequence of it's interaction with other abilities. But, without focused testing, it's too early to say for sure.
However, crying about it on the forum will do you no good. Presenting a disjointed rant that shows psudo-data that include piles of other powers and gear that would make QA have to go through an immense effort to validate a report also will do you no good. Showing the PvP leaderboard is irrelevant and again, does you no good. Calling me names will do you no good. Your assumptions are flawed and so is your data. The end conclusion, that Avalanche is causing too much damage is probably correct - but you haven't tried to explain why you just came here to complain about it.
I don't complain about it. I figure out what's really happening and present Cryptic (directly, I might add) with formal reports that they can easily and quickly validate internally so the devs can get a fix in. That's what I do. So... there's you... complains and rants. Then there's me... logical testing and a track record of actually helping get bugs fixed.
Now... I suggest you stop insulting me and others, drop the angry attitude and see about being constructive, or I have a hunch this thread won't be long for this world. Here's where we test your "reading comprehension" -- before you reply, please re-read that last sentence.
Sekhmet@kvetchus_
Guilds: Greycloaks, Blackcloaks, Whitecloaks, Goldcloaks, Browncloaks, Spiritcloaks, Bluecloaks, Silvercloaks, Black Dawn
Tredecim: The Cloak Alliance
First the BUGS are reported by the COSTUMERS, usually in a very poorly written mails or tickets, QA's job is to DECIPHER those complaints and submit a formal ticket (using jira for examle) to the DEV team, it is NOT the customer's responsibility to write formal and structured tickets. (you expect every non professional person to know how to submit a bug report, nice joke).
Now regarding your "achievements", I don't see anything that you did, all i see is you hijacking other threads and reposting the same thing with better formatting, you didn't actually stumble upon the bugs, you just retest them after someone else already did.
For example I made a thread about harrowstorm:
http://www.arcgames.com/en/forums#/discussion/562024/you-broke-harrowstorm-after-recent-patch
All QA person needs to do is read the encounter description, put 1+1 and submit a bug report to DEV, this is how it works in every major corporate. So who's to say you had a direct impact on that? strum the community manager THANKED ALL in that thread he confirmed devs know about the issue.
The fact that they have their own agenda and prioritize bugs at the bottom of the list shows you who we're dealing with, this company has a track record of failing addressing major bugs, are you going to say that's all because of badly formatted threads? step off your high horse m8.
Now I don't want to discuss this any further, this thread is the biggest reason SW under performs in PVP, when they ever decide to look at class balance, this issue will be unavoidable, plus, every SW in the top 10 leaderboard will indicate the same issue, that's why I'm not worried how I phrase my complaints, It doesn't matter if no one is giving it any attention anyway.
It's a LOGICAL problem that QA should pick up on; a boon that was BUFFED with mod6, that reflects upto 20k dmg when reaching certain amount of stacks, having classes like SW/HR was an overlooked issue.
It's not a gamer's job to be QA, it's QA's job.
(for the record I never insulted you, I just questioned you, you chose to be offended).
Writing gobbledygook and expecting QA to decipher it is why things don't get done fast. Writing solid reports that clearly - emphasis on clearly - explain the problem helps immensely. Not sure how much IT/dev experience you have (I've been at it for more than 15 years now), but I can tell you - it takes WAY more time to troubleshoot a potential defect if the report has to be decrypted first. If you want fast action, put as much effort into writing a clear report as you put into getting indignant in this thread and you might actually be amazed. Keep acting like a spoiled brat and frankly you can expect nothing. Clearly you didn't read my second to last sentence... This thread has devolved into a flame war, and it should be closed.
Sekhmet@kvetchus_
Guilds: Greycloaks, Blackcloaks, Whitecloaks, Goldcloaks, Browncloaks, Spiritcloaks, Bluecloaks, Silvercloaks, Black Dawn
Tredecim: The Cloak Alliance
Call me Andy (or Strum, or Spider-Man)!
Follow Neverwinter on Twitter: NeverwinterGame
Like Neverwinter on Facebook: Neverwinter
Follow me on Twitter: StrumSlinger
Your arrogance nullifies your entire post. Why don't you think a little bit before popping that attitude with people who have done more testing than you have?
Okay. Let's iron the facts out:
a) At 20 stacks, avalanche can and will multiproc upwards of 15 times sometimes, because of the amount of dots that are on the target will activate it at the same time
b) Avalanche has no ICD between gaining stacks, which means the above issue is even worse because it's not something you can time to avoid
First of all, your attitude of "I get things fixed and you don't because I can engrish and you don't" is really really annoying, please kindly drop it or shut up. Secondly, these aren't assumptions, they're conclusions and facts that HAVE BEEN TESTED NUMEROUS TIMES BY SEVERAL DIFFERENT PEOPLE.
This data has been tested by many top PvPers, SWs and other players. People don't need to work in IT for 15 years to understand how a game works - they understand it because they're smart players and know what to test. On the other hand, people who work in IT for 15 years may still need experience to understand how a game works. Spurting BS about "this is how QA works" doesn't make you any better in anyone's eyes - not mine, not any respectable/intelligent/good player in the game, or anyone else for that matter. It just makes you a prick.
I know you're a PvE player with a PvE mindset, but this is a PvP thread. Keep your PvE testing where it belongs please, and don't provide misinformation.
As for testing and evidence:
A GF sat and blocked the whole time (testing in DV), while a SW basically unloaded rotation on him. This was the overall damage:
That was with the GF BLOCKING and only hit once with anvil for 17k. The rest was avalanche damage mostly.
The GF's outgoing damage:
This is the SW's total stats:
This is part of the avalanche ticks that took place. Note the timestamps:
For a video:
Edit: Thanks strum! Hopefully this bug gets fixed asap.
Call me Andy (or Strum, or Spider-Man)!
Follow Neverwinter on Twitter: NeverwinterGame
Like Neverwinter on Facebook: Neverwinter
Follow me on Twitter: StrumSlinger
.
Sopi SW Youtube channel pvp brickabrack
http://i.imgur.com/nSQhzLs.png
You know, technically its over TWO seconds not one. So its only HALF as OP as you think it is ^^ hahahaha jk.
Yeah this seriously needs a fix. Like I said I would BET that just swapping this to an ICD could potentially fix this. How many abilities that have ICDs end up multi-proccing? My guess is its something to do with the lack of ICD that causes the multiproc issue.
Seems like there must be a delay from reaching 20 stacks to the avalanche dmg proc.
tic tic tic tic tic tic tic (20 stacks reached..,, tic tic tic tic tic,,,, dumps 6 times) tic tic tic tic tic
Sopi SW Youtube channel pvp brickabrack
I do not understand why this was allowed to continue.
Where do you see me shaming anyone? My agenda is not against PLAYERS it's against GAME MECHANICS.
Why would I use my guildmate as example to shame him? seriously just gtfo, tired of sjw everywhere.