The silence was finally broken two days ago, when DICE community manager Kevin Johnson replied that with employees only just returning to the office from their holidays, progress on resolving the issue has been slow. The issue has remained long enough to garner replies from the development team, but there has been little communication between DICE and Battlefront 2's players beyond informing them that the situation was being looked into. In practice, this meant that a multiplayer lobby affected by this issue meant that it could only end in two ways: through the map timing out, or the more likely option – through every player quitting.Ĭomment from discussion T0TALfps's comment from discussion "EA/DICE finally responds to the Backlash, Part 2: "Many are quite content with the announcement and release schedules."". No matter the method, no matter the damage done to affected players, they would forever remain at 1HP – unable to drop below the threshold. Namely, the problem and the effect of the bug was rather simple. RELATED: EA's Biggest Star Wars Mistake May Be No Battlefront 3, Star Wars: Squadrons Sequel By December, the bug became so widespread that it bred enough discontent among the community as to label the game unplayable. ![]() Though Star Wars: Battlefront 2 has endured a long and fruitful post-launch support from DICE, a game-breaking bug started cropping up on the multiplayer servers as early as October of last year, with players creating posts about it on online forums. Star Wars: Battlefront 2 has been one of the most unexpected redemption stories in recent gaming memory, completely turning around the narrative of a disastrous launch into that of being a respectable third-person shooter set in a Galaxy Far Far Away, with a healthy playerbase and a lively modding scene that, among other things, went as far as to introduce Pope John Paul II to Star Wars: Battlefront 2.
0 Comments
Leave a Reply. |
AuthorGurmeet ArchivesCategories |