{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by SlowDancer13:
9/1/2016 11:28:24 AM
25
Blink Strike (And It's Many Problems)
Can we please fix blink strike? It's probably the worst charged melee in the game right now, for a few simple reason:
1) It almost [u][b][i]never[/i][/b][/u] proc's in the appropriate range.
2) The appropriate range is still .7 meters below a warlocks [b]base[/b] melee range.
3) Half the time, when it does proc, it doesn't connect with your opponent! It's like in the old days of the Cryptarch. You would roll a legendary engram and then re-roll it. You roll to get it to proc, and then you roll again praying it will actually connect!
Possible solutions:
1) Fix the hit detection (duh).
2) Give it Amplitude range. This way it won't be nearly as severe a punishment when it doesn't proc. It would also not be overpowered, as unlike amplitude, blink strike has a lunge forward.
If anyone reads this, give me opinions on why I'm right/wrong, and/or possible solutions.
-
The bladedancer subclass in general needs work. The hunter patch improved the super but made other areas way worse than they need to be, or in the case of blink strike often not work. Hunters needed only two nerfs: wombo combo, and backstab working when it proc from the front. We saw what they ended up doing. 2) The appropriate range is still .7 meters below a warlocks base melee range. This is a huge problem and embodies the horrible design and balance patches in year 2. If no changes happen to Hunters heading into year 3, then warlocks will still be the dominant class.
