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
... replying to combining abilities .... no, it’s not easy to combine Frenzy with Pull because opponents can dodge out immediately before the end of the animation, taking them out of the AOE of Frenzy and thereby eliminating the combination.
as for Freeze ... well you “could” but it’s a poor choice for 2 reasons .. the AOE of Freeze is FAR larger than Frenzy to Kylo has to close distance to activate it .. & second, it’s more strategic to attempt to perform a standard strike from behind and get the additional damage than it is to use Frenzy. The only time I try to combine them is when I have distance to close and I need to use the leap before the Freeze duration runs out but this isn’t a benefit either because, as you saw from the video, Freeze doesn’t last long enough for Kylo to close distance before the opponent can “block” while still in animation.
Its so poorly put together for Kylo that the real world instances where these abilities are beneficial is exceptionally low.
again, I don’t know if on Xbox there are factors that create a disparity over what you see on PC; I do know that there are variations in gameplay between what people observe on Xbox vs PS.
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.
I stated specially that the ability produces two “leaps”, not strikes. Kylo will strike so long as the ability is active, however, I am correct in that he only leaps twice.
yes, the video does show the animation issue and if video isn’t enough proof of an issue I don’t know what is. That example is what I have been experiencing and it’s clear from the animation error that something behind the scenes with the game mechanic is broken. It shouldn’t be doing that all the time.
Perhaps someone on Xbox should contribute toward the discussion. When it comes to researching problems, proper and related data & experiences are what need to be evaluated.
I do believe there is a platform contribution at play because although the bug report focuses on Kylo’s Frenzy there are a lot of other consistent gameplay anomalies that are occurring.
What you experience and test on PC isn’t reflective of what those on Xbox can expect as a result.
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.
