Disabled Block BUG: Block Stops Working, No Block Animation, Stamina Depletes
Product: Star Wars Battlefront II
Platform:PC
What is your issue related to? General
Summarize your bug Suddenly a lightsaber user becomes unable to block with its associated button. Stamina is depleted normally, but neither the blocking animation nor the actual act of blocking work as intended.
What is your gamertag/PSN ID/EA Account name? RogueZeroRendar
How often does the bug occur? Often (50% - 99%)
Can you tell us the date (MM/DD/YYYY) that you saw the bug? Many dates
What time did you see the bug? (HH:MM AM/PM) Many times
In what game mode did the bug occur? Heroes vs. Villains
What is your time zone?
Steps: How can we find the bug ourselves? Follow the steps in the videos provided
What happens when the bug occurs? Lightsaber user becomes unable to block with his lightsaber.
What do you expect to see? That this longstanding BUG finally gets fixed
Please select your region Africa, Asia, Australia, Europe, North America, South America
AMD or Nvidia Model Number
PLAYERS: IF YOU DEPLETE ALL YOUR STAMINA BAR, THIS BUG GETS FIXED. CHECK THE FASTEST METHOD TO DEPLETE STAMINA IN THE 1ST VIDEO BELOW
(TIME STAMPS: 1 min 12 sec to fully check the process, or 1 min 30 sec to only check the actual fastest stamina depletion method itself)
The best I can provide is in this video:
In this newer video you just need to allow kylo to freeze you twice in a row, and the BUG will get activated.
There's also this older video that shows another method to reproduce this BUG. which works since April 2018 at least:
To summarize it: I block Vader's Choke in the exact moment between a successful Block and an unsuccessful block, which leads to a bad state where you take damage, gets slower, but remains walking and blocking. If you simply let go, you resume the choking animation (this BUG which I called Vader's Choke Half Effect BUG is covered here: https://answers.ea.com/t5/Bug-Reports/Half-Effect-BUG-Maul-s-Choke-Hold-Kylo-s-Freeze-Vader-s-Choke/m-p/7288947 ). However, if you try to dodge away during this bad state, with some trial and error, you'll trigger the Disabled Block BUG state, which can only be fixed by either respawning or depleting your stamina.
However, this doesn't mean this BUG is associated with Vader's choke, but it's the only case I've been able to reproduce (now there's the new Kylo's Freeze method since the Chosen One Update). I opened this new thread because Ewok Patch has come and this hasn't been adressed yet.
I hope this finally gets fixed once and for all.
Also, I leave here this match (December 2018) as another great mark for the existence of this BUG: I endured it happening 5 times in the same match, had to use the method of depleting stamina 5 times to get back to the fight properly, and even then I managed to die only once, and do a 41 killstreak as Rey.
The time stamps can be found in the video description on youtube, but here are they anyway: 04:05, 19:15, 21:40, 25:55, 38:50
Ok so finally I decided to close this report. This specific Block BUG has been properly fixed some months ago (after February 2019). It took them a long time to fix this issue, they tried several times before but none worked. I have gathered a lot of info to help on solving this BUG for one year, and most of it is shared on this report.
But then, after the game got completely broken around Anakin's launch, devs decided to finally tackle this issue. At that point it was so abusive that Kylo could distribute this BUG freely just by freezing enemies. After they announced it fixed, I made a test to check it properly. That test was my suggested method to trigger this BUG on purpose since April 2018, and if performed correctly would always trigger that BUG. I performed it correctly, but the Disabled Block BUG didn't trigger. However, the Dash Strike Visual BUG actually triggered (which is a BUG that always triggered together with the disabled block bug mentioned on this report). That made me believe the BUG was fixed for good.
But we can never be so sure, so I waited. And here we are now, several months after said fix, and the BUG hasn't resurfaced. There are other Block BUGs, but this one can finally be put to rest. It's great this BUG is finally solved, but the bad thing is that this one had a fixing method ingame, the others don't necessarily have one.
We're free from this BUG, but we aren't free of all Block BUGs unfortunately. At least one very serious and very disrupting BUG got fixed. Another Day 1 BUG finally fixed.
