criterion-sm dice-lg ea-starwars-lg instagram lucasfilm-lg motive-lg twitch you-tube

A Match in Review: 12 Different BUGs Exposed & Reported. Also, the highest Rey Killstreak in HvV

Hello Everyone, once again I come back with more BUG reporting to see if DICE can do something about it.

As many here may have noticed, we're experiencing one very buggy patch update, until at least mid/late January with the Count's arrival. It's not the worst we ever had, but it's a pretty bad one.

2 Days ago I played the best Rey Match of my life on Heroes Vs Villains Game Mode. 41 Killstreak, 93 Eliminations, 200 points short of 60K Score Points. But the Match was COMPLETELY FILLED with BUGs. 12 different types of BUGs were spotted by me while playing and later reviewing the match, and some happened several times.



The most notorious was the Disabled Block BUG, which happened a total of 5 times in this match. This means I had to reset my stamina 5 times during that match to have my block back so to get back to the fighting (this will be better explained in this BUG's section below). The match was very long, and you all know why: Runners & Hiders, a concept EA/DICE dedicate many patch notes to make us believe they got rid of it, just to a few matches later after the patch everyone realise they failed.

A funny BUG which is a side-effect of the Disabled Block BUG was the spotlight of this match, the Dash Strike Visual BUG, and I want to share some of these with you, to tease the most BUGGED match of my life:

giphy.gif
giphy.gif
giphy.gif
giphy.gif
giphy.gif

And here I briefly expose, with Report Links included (so please go there and upvote these reports to get DICE's attention faster), all the 12 BUGs:
Maul's Corpse Attacking BUG (https://answers.ea.com/t5/Bug-Reports/Maul-s-Corpse-Attacking-BUG/td-p/7288835)
This one happens when Maul dies while performing the spin ability. He keeps damaging enemies that pass near his corpse for a time before he respawns. This BUG also happens to Luke and Phasma.
Maul's Choke Hold Throwing in Random Directions BUG (https://answers.ea.com/t5/Bug-Reports/Maul-s-Choke-Hold-Throwing-in-Random-Direction/m-p/7233994#M20533)
This one is new. Since the last patch update (or the one before), Maul's Choke Hold sends people in totally random direction. It's unpredictable. Before it complied with the weird physics of the game. Now even a completely motionless player may be sent towards Maul by a Choke Hold (which should send people away from maul).
Disabled Block BUG (https://answers.ea.com/t5/Bug-Reports/Disabled-Block-BUG/m-p/6762835#M13381)
This one is notorious. I've reported a method on how to reproduce it in a testing environment back in April. We're almost getting into 2019, and this BUG is still here. In this one, for various reasons, a Blocking Character (sabers, except maul) can suddenly lose the ability to block any incoming hit. But this one can be fixed in-game by a method other then dying/respawning. If you spend all your stamina while this BUG is in effect, just as the stamina starts refilling, your block will return to normal.
Rey's Dash Strike Visual BUG (https://answers.ea.com/t5/Bug-Reports/Rey-s-Dash-Strike-Visual-BUG/m-p/7288862#M20756)
This one is a consequence of the previous one. Whenever Rey is affected by the Disabled Block BUG, her Dash Strike gets this weird effect. It may not happen. It may happen more then once. But it usually happens once. Those GIFs posted above show the effect of this BUG. Besides the visual bug, nothing else really is affected, everything behaves as normal.
Scoreboard Killstreak Counter Desync BUG (https://answers.ea.com/t5/Bug-Reports/Scoreboard-Killstreak-Counter-Desync-BUG/m-p/7288882#M20758)
I had seen this long ago, but never like now. I started the match, killed 3 enemies and died. After that I killed 41 in a streak. Whenever I killed someone, the counter pop-up display was doing things correctly. However, the counter on the scoreboard screen was considering one more kill in my streak. By reviewing the match it's clear the scoreboard counter was wrong, it somehow desynced with the pop-up counter, and started displaying a wrong value.
Rey's Dash Strike Orientation BUG (https://answers.ea.com/t5/Bug-Reports/Rey-s-Dash-Strike-Orientation-BUG/m-p/6827667#M15399)
I've also reported this long ago. In this BUG, when Rey uses Dash Strike, and for some reason her character model isn't looking to the same spot as the player's camera, she won't go towards where the camera is pointing, but rather to where her character model is facing. This usually creates small tilts when used (but enough to make you miss the target or fall to your death), but sometimes it can be as big as 180° tilt (check video on the Report Link). This also isn't restricted to a single hero, but any rushing character can experience this bug with their rushing ability (Luke, Yoda, Maul are other examples).
Obi-Wan's All-Out Push Stuck Sound BUG (https://answers.ea.com/t5/Bug-Reports/Obi-Wan-s-All-Out-Push-Stuck-Sound-BUG/m-p/7288905#M20759)
In this one, for unknown Reasons, the All-Out Push Sound Effect gets stuck in Obi-Wan. Wherever he goes, an eerie 'vouuuushhhhh' sound follows.
Shaky Camera During Forced Movement BUG (https://answers.ea.com/t5/Bug-Reports/Shaky-Camera-During-Forced-Movement-BUG/m-p/7288919#M20760)
Shaky Cameras are a problem since launch, but it wasn't until now that almost always a forced movement effect will cause the camera to shake like crazy. Kylo's Pull and Obi's Push have been effective in reproduce this BUG.
Kylo's Freeze Half Effect BUG (https://answers.ea.com/t5/Bug-Reports/Kylo-s-Freeze-Half-Effect-BUG/m-p/7288937#M20761)
This one and the following 2 are caused by the same trigger, but each to a different ability in the game. Whenever you block such force powers in a brief window of time between a successful block and an unsuccessful block, you trigger the "Half Effect" BUG. This usually cancels or delays the forced movement/paralysis effect, but still apply damage when its due. In Kylo's Freeze case, it simply delays the freeze while you can stay blocking but not moving. The screen darkens as if you're frozen. Because of stagger (being attacked) or timely dodges, one can get free of the Half-Effect without having to endure a following fully frozen effect.
Maul's Choke Hold Half Effect BUG (https://answers.ea.com/t5/Bug-Reports/Maul-s-Choke-Hold-Half-Effect-BUG/m-p/7288947#M20762)
As with the previous one, a block during that brief window will cancel the forced movement of the choke hold, will tilt the camera to somewhere else, but will still do damage. While in that state, you can keep blocking and moving, and after it's finished, no delayed effect takes place.
Vader's Choke Half Effect BUG (https://answers.ea.com/t5/Bug-Reports/Vader-s-Choke-Half-Effect-BUG/m-p/7288959#M20763)
As with the 2 previous ones, blocking during the window triggers this. In this one you get slowed, get the choke's sound effect as if it was hitting, the damage still applies normally, but no forced movement happens. If you release your block anytime during this weird state, or after it's done, you'll resume the choke's forced movement effect. However a perfect dodge during the Half Effect state may get you free of the delayed forced movement effect. And that will NECESSARILY TRIGGER the Disabled Block BUG. That's actually our Method of doing it on purpose, posted on our channel, and reported to EA back in April.
Grievous's Thrust Surge Far Hit BUG (https://answers.ea.com/t5/Bug-Reports/Grievous-s-Thrust-Surge-Far-Hit-BUG/m-p/7288971#M20764)
This one is new to me. It's just that, thrust surge can hit people far away. I was far from grievous, with allies in between us, he used thrust surge, targetted one of these allies, and he also hit me in the process (all these bugs are timestamped on the video description). I was with insight on, so I knew there were no other enemies nearby or with LoS to me to have dealt that.

We will also put @RogueOneKenobi 's view of this match as Yoda later, so many BUGs can even be checked from 2 different perspectives. Especially because we're usually playing close to each other, so most of the time we see the same things happening.

So look DICE, we're here to do good to the Star Wars Franchise. The amount of BUG's you're allowing to haunt this game is a lot more then anyone can stand. At this point, this game is a joke in the BUGFixing front. Yet you have many people, like myself, doing a lot to report BUGs, to find evidence, to share material, to test parameters. The active crew in Answers HQ is amazing. Some are EA Heroes, and some aren't, which shows how passionate and dedicated some fans are to help improve this game, no matter if they'll only gain a better experience with said game.

But your QA Team, Live QA Team, and Dev Team have time and time again only proven to the fans that BUGs are here to stay (and many times to resurface). For each one that gets fixed, 5 more are gradually included.

For each patch, at least one new BUG is included.
For each BUG to be fixed, 3 or more patches need to go by.

I suggest a different approach to the situation. You have the means, and we have the empirical material and knowledge on the gaming side of things. By working together we can get rid of these BUGs. Without BUGs I'm sure more people will come back to play and more people will buy the game because their friends are telling them to. More people means a Win-Win situation: You get the revenue, we get more lobbies and activity. Everyone gets happier. Star Wars fandom rejoices.
Tired of BUGs?
giphy.gif
Well, they'll still exist.
But visit the Rogue Bros Channel, there we document many BUGs and possible workarounds for them. There's also gameplay and other videos related to EA's Star Wars Battlefront (I & II)

Replies

  • At first I thought you were just advertising your channel, but then I read on, and the bug compilation was very informational and specific. It looks like you put time and effort into this. Great work!
    Add more Extraction and Hunt maps please!

    What the ROADMAP should look like for 2019/2020:
    “Season” 4: Rogue One
    “Season” 5: Clone Wars Revival
    “Season” 6: Episode IX
  • RogueZeroRendar the hero the dev team needs but doesn't deserve.
    Dont act a fool and you wont get called out. PSN: DarthOdium- old PSN:unit900000
  • Hello Everyone, once again I come back with more BUG reporting to see if DICE can do something about it.

    As many here may have noticed, we're experiencing one very buggy patch update, until at least mid/late January with the Count's arrival. It's not the worst we ever had, but it's a pretty bad one.

    2 Days ago I played the best Rey Match of my life on Heroes Vs Villains Game Mode. 41 Killstreak, 93 Eliminations, 200 points short of 60K Score Points. But the Match was COMPLETELY FILLED with BUGs. 12 different types of BUGs were spotted by me while playing and later reviewing the match, and some happened several times.



    The most notorious was the Disabled Block BUG, which happened a total of 5 times in this match. This means I had to reset my stamina 5 times during that match to have my block back so to get back to the fighting (this will be better explained in this BUG's section below). The match was very long, and you all know why: Runners & Hiders, a concept EA/DICE dedicate many patch notes to make us believe they got rid of it, just to a few matches later after the patch everyone realise they failed.

    A funny BUG which is a side-effect of the Disabled Block BUG was the spotlight of this match, the Dash Strike Visual BUG, and I want to share some of these with you, to tease the most BUGGED match of my life:

    giphy.gif
    giphy.gif
    giphy.gif
    giphy.gif
    giphy.gif

    And here I briefly expose, with Report Links included (so please go there and upvote these reports to get DICE's attention faster), all the 12 BUGs:
    Maul's Corpse Attacking BUG (https://answers.ea.com/t5/Bug-Reports/Maul-s-Corpse-Attacking-BUG/td-p/7288835)
    This one happens when Maul dies while performing the spin ability. He keeps damaging enemies that pass near his corpse for a time before he respawns. This BUG also happens to Luke and Phasma.
    Maul's Choke Hold Throwing in Random Directions BUG (https://answers.ea.com/t5/Bug-Reports/Maul-s-Choke-Hold-Throwing-in-Random-Direction/m-p/7233994#M20533)
    This one is new. Since the last patch update (or the one before), Maul's Choke Hold sends people in totally random direction. It's unpredictable. Before it complied with the weird physics of the game. Now even a completely motionless player may be sent towards Maul by a Choke Hold (which should send people away from maul).
    Disabled Block BUG (https://answers.ea.com/t5/Bug-Reports/Disabled-Block-BUG/m-p/6762835#M13381)
    This one is notorious. I've reported a method on how to reproduce it in a testing environment back in April. We're almost getting into 2019, and this BUG is still here. In this one, for various reasons, a Blocking Character (sabers, except maul) can suddenly lose the ability to block any incoming hit. But this one can be fixed in-game by a method other then dying/respawning. If you spend all your stamina while this BUG is in effect, just as the stamina starts refilling, your block will return to normal.
    Rey's Dash Strike Visual BUG (https://answers.ea.com/t5/Bug-Reports/Rey-s-Dash-Strike-Visual-BUG/m-p/7288862#M20756)
    This one is a consequence of the previous one. Whenever Rey is affected by the Disabled Block BUG, her Dash Strike gets this weird effect. It may not happen. It may happen more then once. But it usually happens once. Those GIFs posted above show the effect of this BUG. Besides the visual bug, nothing else really is affected, everything behaves as normal.
    Scoreboard Killstreak Counter Desync BUG (https://answers.ea.com/t5/Bug-Reports/Scoreboard-Killstreak-Counter-Desync-BUG/m-p/7288882#M20758)
    I had seen this long ago, but never like now. I started the match, killed 3 enemies and died. After that I killed 41 in a streak. Whenever I killed someone, the counter pop-up display was doing things correctly. However, the counter on the scoreboard screen was considering one more kill in my streak. By reviewing the match it's clear the scoreboard counter was wrong, it somehow desynced with the pop-up counter, and started displaying a wrong value.
    Rey's Dash Strike Orientation BUG (https://answers.ea.com/t5/Bug-Reports/Rey-s-Dash-Strike-Orientation-BUG/m-p/6827667#M15399)
    I've also reported this long ago. In this BUG, when Rey uses Dash Strike, and for some reason her character model isn't looking to the same spot as the player's camera, she won't go towards where the camera is pointing, but rather to where her character model is facing. This usually creates small tilts when used (but enough to make you miss the target or fall to your death), but sometimes it can be as big as 180° tilt (check video on the Report Link). This also isn't restricted to a single hero, but any rushing character can experience this bug with their rushing ability (Luke, Yoda, Maul are other examples).
    Obi-Wan's All-Out Push Stuck Sound BUG (https://answers.ea.com/t5/Bug-Reports/Obi-Wan-s-All-Out-Push-Stuck-Sound-BUG/m-p/7288905#M20759)
    In this one, for unknown Reasons, the All-Out Push Sound Effect gets stuck in Obi-Wan. Wherever he goes, an eerie 'vouuuushhhhh' sound follows.
    Shaky Camera During Forced Movement BUG (https://answers.ea.com/t5/Bug-Reports/Shaky-Camera-During-Forced-Movement-BUG/m-p/7288919#M20760)
    Shaky Cameras are a problem since launch, but it wasn't until now that almost always a forced movement effect will cause the camera to shake like crazy. Kylo's Pull and Obi's Push have been effective in reproduce this BUG.
    Kylo's Freeze Half Effect BUG (https://answers.ea.com/t5/Bug-Reports/Kylo-s-Freeze-Half-Effect-BUG/m-p/7288937#M20761)
    This one and the following 2 are caused by the same trigger, but each to a different ability in the game. Whenever you block such force powers in a brief window of time between a successful block and an unsuccessful block, you trigger the "Half Effect" BUG. This usually cancels or delays the forced movement/paralysis effect, but still apply damage when its due. In Kylo's Freeze case, it simply delays the freeze while you can stay blocking but not moving. The screen darkens as if you're frozen. Because of stagger (being attacked) or timely dodges, one can get free of the Half-Effect without having to endure a following fully frozen effect.
    Maul's Choke Hold Half Effect BUG (https://answers.ea.com/t5/Bug-Reports/Maul-s-Choke-Hold-Half-Effect-BUG/m-p/7288947#M20762)
    As with the previous one, a block during that brief window will cancel the forced movement of the choke hold, will tilt the camera to somewhere else, but will still do damage. While in that state, you can keep blocking and moving, and after it's finished, no delayed effect takes place.
    Vader's Choke Half Effect BUG (https://answers.ea.com/t5/Bug-Reports/Vader-s-Choke-Half-Effect-BUG/m-p/7288959#M20763)
    As with the 2 previous ones, blocking during the window triggers this. In this one you get slowed, get the choke's sound effect as if it was hitting, the damage still applies normally, but no forced movement happens. If you release your block anytime during this weird state, or after it's done, you'll resume the choke's forced movement effect. However a perfect dodge during the Half Effect state may get you free of the delayed forced movement effect. And that will NECESSARILY TRIGGER the Disabled Block BUG. That's actually our Method of doing it on purpose, posted on our channel, and reported to EA back in April.
    Grievous's Thrust Surge Far Hit BUG (https://answers.ea.com/t5/Bug-Reports/Grievous-s-Thrust-Surge-Far-Hit-BUG/m-p/7288971#M20764)
    This one is new to me. It's just that, thrust surge can hit people far away. I was far from grievous, with allies in between us, he used thrust surge, targetted one of these allies, and he also hit me in the process (all these bugs are timestamped on the video description). I was with insight on, so I knew there were no other enemies nearby or with LoS to me to have dealt that.

    We will also put @RogueOneKenobi 's view of this match as Yoda later, so many BUGs can even be checked from 2 different perspectives. Especially because we're usually playing close to each other, so most of the time we see the same things happening.

    So look DICE, we're here to do good to the Star Wars Franchise. The amount of BUG's you're allowing to haunt this game is a lot more then anyone can stand. At this point, this game is a joke in the BUGFixing front. Yet you have many people, like myself, doing a lot to report BUGs, to find evidence, to share material, to test parameters. The active crew in Answers HQ is amazing. Some are EA Heroes, and some aren't, which shows how passionate and dedicated some fans are to help improve this game, no matter if they'll only gain a better experience with said game.

    But your QA Team, Live QA Team, and Dev Team have time and time again only proven to the fans that BUGs are here to stay (and many times to resurface). For each one that gets fixed, 5 more are gradually included.

    For each patch, at least one new BUG is included.
    For each BUG to be fixed, 3 or more patches need to go by.

    I suggest a different approach to the situation. You have the means, and we have the empirical material and knowledge on the gaming side of things. By working together we can get rid of these BUGs. Without BUGs I'm sure more people will come back to play and more people will buy the game because their friends are telling them to. More people means a Win-Win situation: You get the revenue, we get more lobbies and activity. Everyone gets happier. Star Wars fandom rejoices.

    dash strike bug is indiana jones on steriods, now i have proof that harrison ford had two roles in the force awakens
    cause everything you read on the internet is true...
  • The Maul choke I have noticed a LOT. It's been that way since Kenobi came out. I don't consider the Thrust Surge thing to be a bug, just an awesome move. It can be easily avoided if you're not running away or caught off guard, and since Greebus can't use the force, I feel like it's a good compromise.
    ZI7BNkU.gif
    ^Maximum the Hormone - Alien^
    (Sorta like an insane Japanese SOAD, but w/ 3 vocalists and slap bass)

    Gamertag: Billkwando YouTube: Billkwando
    Find me in HvV, pushing people off of stuff and watching them fall, like a cat.
  • @EventHorizionOH @The_Sith_Apprentice @MyLittleGreenFriend @unit900000
    Thanks for the compliments! I wish DICE would look this and say something about it.

    @Billkwando
    Yeah, Maul's one is very annoying, glad you remember it came with Obi. I rarely play Maul, so it took me a while to recognize this as a BUG. But have you seen the thrust surge moment in the video? I was considerably far from grievous. He needed to make his lightsaber at least 3 times in length to have hit me there. And he didn't even target me, he targetted an ally, who wasn't near me. As you said, he doesn't have the force, but only the force could explain how he hit me from such a distance (as seen in the footage, he doesn't get propelled towards me by using the skill, he propels to an ally several feet away from me, and not only damage him, but also damages me as well). Time stamp for this one in the video: 41:15

    I also would like to tag @lerodemmy to see this Rey Killstreak, but I believe he's been inactive for quite some time. Oh well.

    @IronSoldier can we do something for this massive report to get the attention it deserves?

    Also to everyone: I'll resume BUG hunting now that college has eased a bit and the summer break is almost upon me. So expect several videos with exposing, explaining and trying methods to fix BUGs in the near future.
    Tired of BUGs?
    giphy.gif
    Well, they'll still exist.
    But visit the Rogue Bros Channel, there we document many BUGs and possible workarounds for them. There's also gameplay and other videos related to EA's Star Wars Battlefront (I & II)
  • Great post RogueZeroRendar. I feel that more people should head over to Answers to report bugs and help them get attention.

    And awesome killstreak. :smiley:
  • LOTR2013 wrote: »
    Great post RogueZeroRendar. I feel that more people should head over to Answers to report bugs and help them get attention.

    And awesome killstreak. :smiley:

    Yeah it was an amazing killstreak.
  • i even bookmarked it
    cause everything you read on the internet is true...
  • Thanks folks! But a comment from any mod or staff is yet to come. Let's wait. After all, the bug list is big and detailed, I really want to speed up the bugfixing process.
    Tired of BUGs?
    giphy.gif
    Well, they'll still exist.
    But visit the Rogue Bros Channel, there we document many BUGs and possible workarounds for them. There's also gameplay and other videos related to EA's Star Wars Battlefront (I & II)
  • and the response has been...?
  • Congrats on the killstreak and great job with the thread and bug reporting!
    21 years in the making... the wait is almost over. Pre-order RESIDENT EVIL 2 now!
    header.jpg?t=1547513853
  • RogueZeroRendar
    796 posts Member
    edited December 2018
    lerodemmy wrote: »
    Congrats on the killstreak and great job with the thread and bug reporting!
    Thanks! And glad to see you back!
    gibran5000 wrote: »
    and the response has been...?
    None, as usual, they didn't say anything yet.

    And now the second view of the same match has been released:



    This started to be recorded 17 seconds ahead of the other one, so to check on Yoda's video each of the BUGs time stamped on Rey's video description, just add 17 seconds to the time stamp and there you go.

    So here it is DICE, 2 PoVs of the same match, 12 BUGs exposed and explained with their times written in the video description. I'm doing my part, now it's time for you to do yours.
    Tired of BUGs?
    giphy.gif
    Well, they'll still exist.
    But visit the Rogue Bros Channel, there we document many BUGs and possible workarounds for them. There's also gameplay and other videos related to EA's Star Wars Battlefront (I & II)
  • Nice detailed post. Hopefully it gets a worthwhile response soon.

    The bugged and inconsistent blocking has been nothing short of abysmal for me today. Worked fine when I played last night, but I only switched to HvV because GA was rubber banding and lagging so bad. Deal breaking bad today, guess I’ll play Forza and RDR2 instead.

    When you look at the wall and wonder what it’d look like after your controller was rifled into it, it’s time to stop playing. :D
    Knights of Gareth
    XBL- JsOnMyFett 13
  • Good post man, needs to stay up top. It’s been hard to play HvV lately, borderline unplayable at times on my end. Block works only half the time, Maul’s rush is buggy now, Grievous claw rush has been a 50/50 on if it works or not, then yesterday Vader’s block and Heath card was 50/50 on working.
  • @RogueZeroRendar

    Great post. Mind if I ask what star cards you used for Rey?
  • Ppong_Man12
    2044 posts Member
    edited December 2018
    Getting stuck on randomness is another bug that keeps popping up lately. Tried to post a few vids but they’re not going through.
  • thorzhammers
    384 posts Member
    edited December 2018
    A+ posting.

    I've also noticed the Darth Maul throw bug the most... It's just freaky. But particularly game breaking for me on Kamino. I would have thrown three of the opposing team on HvV into the water, instead they went sideways and stayed on the platform and got up to triple team me. Funny yet annoying.
  • The Maul throw bug is so annoying. Has cost me many kills that should have sent people flying off the map but instead throws them any old way. Half the time it almost seems to pull them instead of push. Needs to be fixed asap.
  • Saw a great bug on DS2 in HvV the other day, I was Phasma and Vader threw his lightsaber through her turret. It got stuck and just kept spinning around it for at least a minute. Sad when the bugs are the best entertainment in the game.
  • Nice man someone that put effort into real important things that need fixing in the game!

    I reported many bugs too and have a big list. Almost nothing is fixed still...
    Priority list:

    1. Fix Split Screen bugs and the rest
    2. Reduce bright Saber glows especially on Yodas head
    3. 41st Scout clone trooper
    4. Max out Arcade maps Combat area
    5. First Person only mode
  • Thanks for the words again folks, I'm trying my best to make this game a better experience. Now it's up to DICE to come here and try to take advantage of someone doing the investigation work for them.
    @RogueZeroRendar

    Great post. Mind if I ask what star cards you used for Rey?

    I won't remember their names now, but the one which gives 60 health on kill, the one which extends the duration of Insight, and the one which increases Rey's damage by 15 points when she strikes someone under the effect of mind control or an immobilizing effect
    Getting stuck on randomness is another bug that keeps popping up lately. Tried to post a few vids but they’re not going through.

    I have several different recorded matches where this new bug happened and I'm working on a new video exposing this and other bugs. I still don't understand how that happens, but it seems to me trying to dodge in weird shaped terrains, corners, or stairs
    Tired of BUGs?
    giphy.gif
    Well, they'll still exist.
    But visit the Rogue Bros Channel, there we document many BUGs and possible workarounds for them. There's also gameplay and other videos related to EA's Star Wars Battlefront (I & II)
  • Thanks for the words again folks, I'm trying my best to make this game a better experience. Now it's up to DICE to come here and try to take advantage of someone doing the investigation work for them.
    @RogueZeroRendar

    Great post. Mind if I ask what star cards you used for Rey?

    I won't remember their names now, but the one which gives 60 health on kill, the one which extends the duration of Insight, and the one which increases Rey's damage by 15 points when she strikes someone under the effect of mind control or an immobilizing effect
    Survivor, Focused Sight, Opportunist. Good choices.
    21 years in the making... the wait is almost over. Pre-order RESIDENT EVIL 2 now!
    header.jpg?t=1547513853
  • Great work, Z! Best way to report a bunch of bugs, do it while being the best! :)
  • Thank you for putting this together with video examples. Very much appreciated and cool of you!

    Regarding your Rey streak though - it’s doesnt mean much if you play with a squad. You should put an asterisk next to the stat - kind of like in baseball when someone uses steroids to achieve a record. Now if you did that while running solo with a pack of noobs and still manage to beat up the enemy team - I would be very impressed.
  • @Rugbymaster1

    How higher do you want to move the bar? :D If I was in a 4 man squad with my 3 mates helping me achieve a killstreak, I would understand. But to stay alive in a true match for around half an hour, get a 41 killstreak, and only with one other in my group is impressive to me.

    But you ask me to do that while carrying 3 noobs? Lol, that's hard. And then, when I do, will you say I did that because all 4 on the other team were noobs too? I mean, we can go anywhere with these restrictions, but I assure you 1 pro player can't take 4 pro players with 3 noobs to carry and still manage the score I did:

    dstgfp6ndsy2.png

    This mode is a team mode, more then any other. Team play is far more important and effective then being pro in HvV. A noob who stays together and tries to use skills to help his team is far better for the team then a pro rusher who leaves his mates behind.

    And I wasn't in a squad, I had only @RogueOneKenobi , the other 2 we actually met on that match and we added each other afterwards. Nice fellas these 2.

    However, if you feel alone playthrough more appealing, I did a 21 killstreak as Rey back in March 2018, that was my record before this one, and I was playing solo:



    But yeah, the focus here is actually the BUG exposure, to which DICE has yet to come and say something about it.
    Tired of BUGs?
    giphy.gif
    Well, they'll still exist.
    But visit the Rogue Bros Channel, there we document many BUGs and possible workarounds for them. There's also gameplay and other videos related to EA's Star Wars Battlefront (I & II)
  • @Rugbymaster1

    How higher do you want to move the bar? :D If I was in a 4 man squad with my 3 mates helping me achieve a killstreak, I would understand. But to stay alive in a true match for around half an hour, get a 41 killstreak, and only with one other in my group is impressive to me.

    But you ask me to do that while carrying 3 noobs? Lol, that's hard. And then, when I do, will you say I did that because all 4 on the other team were noobs too? I mean, we can go anywhere with these restrictions, but I assure you 1 pro player can't take 4 pro players with 3 noobs to carry and still manage the score I did:

    dstgfp6ndsy2.png

    This mode is a team mode, more then any other. Team play is far more important and effective then being pro in HvV. A noob who stays together and tries to use skills to help his team is far better for the team then a pro rusher who leaves his mates behind.

    And I wasn't in a squad, I had only @RogueOneKenobi , the other 2 we actually met on that match and we added each other afterwards. Nice fellas these 2.

    However, if you feel alone playthrough more appealing, I did a 21 killstreak as Rey back in March 2018, that was my record before this one, and I was playing solo:



    But yeah, the focus here is actually the BUG exposure, to which DICE has yet to come and say something about it.

    I’m not doubting that you are a good player and a really really nice guy who makes the forums better with your posts. 🖖
  • @RogueZeroRendar impressive streaks, I’ve done a few 50+ with Han but how do you make the rounds last so long. Just farming them and not target? Can’t say I’ve ever got more than around 70 elims in an HvV but that was 4v4 grouped play. Always keen to go for 100 streak in it but simply can’t make them go the distance
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!