Kylo Ren Frenzy Broken
Product: Star Wars Battlefront II Platform:Microsoft XBOX One What is your issue related to? General Summarize your bug Kylo Ren’s “Frenzy” ability is not breaking through saber wielders blocks. E...
Forum Discussion
You say it only produces 2 leaps/strikes, yet the video you provided clearly show 3 strikes being performed, despite only the second and third produced the block breaking animation (but animations not appearing isn't proof that something has failed).
I could lose a long time here saying what I agree with you, what I disagree with you, how my experience is completely different from yours and I don't think our platforms have anything to do it. However this is all about opinions on a character and/or skill. This isn't the place for that. Here we discuss BUGs. Head over to https://battlefront-forums.ea.com/categories/the-next-star-wars-battlefront and open it there. If you do open a thread in the main forum to discuss this, I'll go there to share my opinions. However, it'll take a while as I'm banned there. Just one or two weeks more and I'll come back there to give my feedback.
For now I feel nothing is bugged with his Frenzy, despite that huge jump he triggers whenever frenzy is activated in an upwards slope. It isn't a strong skill, but in my experience it's a very good skill for its effects and its really fast cooldown. I've played several times since the latest patch and nothing seems out of order.
And to be more specific; yes; the 3rd strike IS supposed to break (not bypass) an opponents block and that’s not happening. It’s supposed to happen and it’s not happening on Xbox; hence why this report is correctly here.
If you're separating leaps from strikes, then let's make things clear: Kylo is supposed to strike 3 times since they changed Frenzy from up to 7 strikes to only 3 with a damage increase to balance things out. In all my experiences, and also in your video evidence, he does strike 3 times. Leaps occur if he wants to strike a character which is not in range of a strike. If you manage to get an enemy away from kylo both between 1st and 2nd strikes and between 2nd and 3rd strikes, and kylo tried to target him from afar in the beginning, he'll leap 3 times. However if the target is within melee range, he'll leap 0 times. Leaps are connected to distance, while strikes are fixed and are always 3. This has been working as intended since the update which changed frenzy.
And about the last strike, not only we have no official info that it MUST break block (this is an assumption of it working consistently through hours, days, weeks, and months since the update that changed frenzy), but it also DOES that in your video evidence. The block breaking animation clearly happens in the lasts trike, it happens that the time it takes for your next strike (now a normal saber attack) to affect luke is more then the time Luke's block stays broken. Just test this with a shooter by your side and make him shoot while Luke plays the animation of block breaking, and you'll see the shots landing. This tactic has been employed by me and @RogueOneKenobi since launch, as he usually picks blaster heroes while I prefer saber heroes. Even before they removed the stagger produced by striking with a saber at a block, just by attacking a blocking character I opened a window where he could land shots on that very enemy.
If your video evidence shows anything, is that it feels unfair that a standing character may block Kylo's freny completely. But this is not a BUG, it's just bad game design, and I invite you once again to come to the main forum and share that there. Link it here so I may follow it. I don't think you're completely wrong in your opinions about how balanced or not Frenzy is, there are things I disagree, and things I agree. It's just that this doesn't seem to be a BUG at all, and by your evidence I can't see anything that slightly resembles a BUG.
However, because you insisted so much on this topic, I decided to keep checking Kylo in my latest test round and I found out that while Luke is able to block Kylo's frenzy completely, Anakin ISN'T. Anakin ALWAYS takes the 3rd hit if he blocks the prior 2 strikes.
As I only realised this in the end of my testing round, I didn't have time to test with all other saber characters, but this is now in my to-do list. Thanks for bringing awareness to Kylo's Frenzy, otherwise I wouldn't find this issue.
This may also not be a BUG, but when certain characters can completely block a move, while others can't, this is strange enough that it may be a BUG. I'll have to test Obi, Rey, and Yoda to see how they react, and eventually open a report just about this issue.
