{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
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.
-
1 返信Blink strike is broken they fix it and everything I going to say is: its a knife attack not a Katana.
-
3 通の返信
-
2 通の返信
-
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.
-
20 通の返信Wow, i can understand the fix, but adding range is ridiculus. Your mellee can 1hit, regenrates health and you perform a blink meaning you can hardly get damaged. Fix the frontstep first, it still procs in the forehead
-
2 通の返信Im a hunter and never would agree to a amplitude boost in the range of blink strike. Solely because it still one hits in the crucible. The front backstab technique never got fix and that's why its broken. No range needed.
-
Im a huntervand never would agree to a amplitude boost in the range of blink strike. Solely because it still one hits in the crucible. The front backstab technique never got fix and that's why its broken. No range needed.
-
14 通の返信
-
7 通の返信Ms Felicityにより編集済み: 9/1/2016 5:37:25 AM[quote]2) The appropriate range is only as far as a warlocks [b]base[/b] melee range.[/quote] Warlock [b]base[/b] melee range = 6.0m Blink Strike = 5.3m Thunderstrike + Amplitude = 10.0m What I would like to see is a separate button for melee overrides. And when we use Blink Strike we just blink 5.3m forward unless we have a target within range, then we blink to the target and shank 'm. Or maybe, change Blink Strike to where you lunge through your enemy and you slice them along the way landing behind them after the lunge.
-
1 返信Yes, for all it does is give the hunter the same (or less. I didn't check) as the warlocks melee with no charge. Great I use my charge to not have a shitty range.
-
3 通の返信BUMP. Blink Strike hit detection is so utterly horrible, it's embarassing. I play on every sub class of every character and nothing is as terrible as blink strike. Not even close. The super is slightly better, now the melee needs to be addressed.
-
4 通の返信Mars3099により編集済み: 9/1/2016 3:33:39 AM[quote]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. [/quote] if they did this, restored Blink (so that it does not completly suck), and made Graviton forfeit for all Hunter subclasses like Garrison then I would use my Bladedancer again
-
[quote]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 only as far as 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.[/quote] It actually has less range then warlock melee after the nerf. And why the hell did they nerf fast twitch because all it did was give you warlock ranged melee MORE OFTEN not even all the time like the warlock melee which always has that range and sometimes additional abilities but using fast twitch takes away hunter melee abilities. So why was a fast twitch nerf even necessary?? Just wondering
-
3 通の返信Definitely play with this. However as they do these changes they need to fix backstab. I have more procs of backstab from the side and front than I do the actual back... Still... Even after they reduced the angles and stuff to try to fix it.
