SoD proc only with a direct cac encounter ( lashing blade, Dazing Strike ) and with physical ranged encounters. With Blitz, it proc only for one of the targets.
No proc with at-wills and daily. Few times, it don't proc whith direct cac encouter after the firt time in a fight.
Stealth regen speed and stealth regen immunity don't work.
Reported since the begining of mod 6 preview tests : no answer, no comment. It's a ninja nerf for a ninja class, enjoy..
0
lordseth1985Member, NW M9 PlaytestPosts: 319Arc User
SoD proc only with a direct cac encounter ( lashing blade, Dazing Strike ) and with physical ranged encounters. With Blitz, it proc only for one of the targets.
No proc with at-wills and daily. Few times, it don't proc whith direct cac encouter after the firt time in a fight.
Stealth regen speed and stealth regen immunity don't work.
Reported since the begining of mod 6 preview tests : no answer, no comment. It's a ninja nerf for a ninja class, enjoy..
Oh man... It's ridiculous this "changes", since the focus of TR was [or still it is?] doing heavy damage one hit-K.O.
Also, many powers of the rogue drains all the stealth when you use it, so what's the point in those changes????????????
Avestruz.Q.T.Seduz - Rogue, natural born assassin.
Oh man... It's ridiculous this "changes", since the focus of TR was [or still it is?] doing heavy damage one hit-K.O.
Also, many powers of the rogue drains all the stealth when you use it, so what's the point in those changes????????????
Finding some other way of damage dealing than relying on lazy 1-shots, I take.
For instance, a different way of maximizing SoD damage by use of consecutive encounter powers, such as LB -> Dazing Strike -> Impact Shot/Wicked Reminder follow-up attacks, which have multiple charges that can be spammed in a short interval of time. Or, you can settle for lesser damage by using fewer offensive encounters and maintaining utilities of stuff like SS, ITC.
best move is to not use your free respec yet guys. wait a little bit more 'til most problems are fixed (crossing my fingers) then decide which build to go..
The main issue is, I suppose, that without confirmation we cannot speculate what exactly is intended. Is this a bug, is it now WAI, etc. I know the devs cannot respond to every issue but certain things do need to be acknowledged after a specific period of time (a month on the outside but certainly two weeks for something class specific as this which would drastically alter a specific path and whether a player would choose it or not). Picking a path is a pretty important part of this game and not knowing what a capstone is meant to do (or in this case having the capstone not perform as the tooltips indicate) is significant enough to warrant a hasty response. I haven't played my executioner in awhile and I could not see me picking that path with the current unknown situation.
0
onegaki101Member, NW M9 PlaytestPosts: 327Arc User
edited April 2015
This is a bug as it was not stated in the patch nor was the tool tip changed to correctly describe the new behavior. It was reported in preview like many other bugs, but was not fixed before the launch.
The main issue is, I suppose, that without confirmation we cannot speculate what exactly is intended. Is this a bug, is it now WAI, etc. I know the devs cannot respond to every issue but certain things do need to be acknowledged after a specific period of time (a month on the outside but certainly two weeks for something class specific as this which would drastically alter a specific path and whether a player would choose it or not). Picking a path is a pretty important part of this game and not knowing what a capstone is meant to do (or in this case having the capstone not perform as the tooltips indicate) is significant enough to warrant a hasty response. I haven't played my executioner in awhile and I could not see me picking that path with the current unknown situation.
This is not a bug. This was intentionally broken in week 2 of preview testing and we reported it week after week after week during testing and it went live. You cannot convince me that this was not an intentional nerf. Just like you cant convince me reducing stealth from 6 seconds to 5 seconds wasnt a knee jerk reaction nerf that has NOTHING to do with the real problems TR's had.
Bedlam: Creating chaos as a MI Exec TR Avariel Merilwen: Burn baby, MoF/Rene Aejun The Silver: Devoted to Healing, DevOP/Justice Mina Rosepetal: Super Natural, Pathfinder/Melee Frost: Benchwarmer, Soulbinder/Fury
0
onegaki101Member, NW M9 PlaytestPosts: 327Arc User
edited April 2015
There are other broken aspects of the game that were introduced early in preview that made it to live. Doubt they were intentional. Since the tool tip says otherwise, it is considered a bug.
0
beckylunaticMember, NW M9 PlaytestPosts: 14,231Arc User
Most of the changes projected for TRs that we knew were coming didn't even make it into the official notes.
I think the issue is that things have been changed have caused bugs or other things that may not be intentional. I think it is safe to call these out as bugs to the Devs at least until we know it was intended
Comments
this is true
No proc with at-wills and daily. Few times, it don't proc whith direct cac encouter after the firt time in a fight.
Stealth regen speed and stealth regen immunity don't work.
Reported since the begining of mod 6 preview tests : no answer, no comment. It's a ninja nerf for a ninja class, enjoy..
Oh man... It's ridiculous this "changes", since the focus of TR was [or still it is?] doing heavy damage one hit-K.O.
Also, many powers of the rogue drains all the stealth when you use it, so what's the point in those changes????????????
Finding some other way of damage dealing than relying on lazy 1-shots, I take.
For instance, a different way of maximizing SoD damage by use of consecutive encounter powers, such as LB -> Dazing Strike -> Impact Shot/Wicked Reminder follow-up attacks, which have multiple charges that can be spammed in a short interval of time. Or, you can settle for lesser damage by using fewer offensive encounters and maintaining utilities of stuff like SS, ITC.
This is not a bug. This was intentionally broken in week 2 of preview testing and we reported it week after week after week during testing and it went live. You cannot convince me that this was not an intentional nerf. Just like you cant convince me reducing stealth from 6 seconds to 5 seconds wasnt a knee jerk reaction nerf that has NOTHING to do with the real problems TR's had.
Avariel Merilwen: Burn baby, MoF/Rene
Aejun The Silver: Devoted to Healing, DevOP/Justice
Mina Rosepetal: Super Natural, Pathfinder/Melee
Frost: Benchwarmer, Soulbinder/Fury
Home page news post. Scroll down.
Most of the changes projected for TRs that we knew were coming didn't even make it into the official notes.
Neverwinter Census 2017
All posts pending disapproval by Cecilia
yeah i knew that part. and im sorry.
I think the issue is that things have been changed have caused bugs or other things that may not be intentional. I think it is safe to call these out as bugs to the Devs at least until we know it was intended