The Return of Star Wars Battlefront II and Error Code: 721
There has been a resurgence of people playing Star Wars Battlefront II recently. Possibly because the game was discounted on many outlets on May 4th and may be due to the success of Andor season 2. There’s a lot more people streaming it as well as videos on YouTube. Whatever the reason, it is always good to see a deserving game enjoying a renaissance. Star Wars Battlefront II was blighted at launch, back in November 2017 by some egregious business decisions and it took nearly a year for the game to recover from the negative publicity and player animosity. Setting this historical debacle aside for one moment, there was always a handsome and engaging game to be found. One that used the licensed intellectual property well. Which is why I recently reinstalled the game and resumed playing its multiplayer mode.
There has been a resurgence of people playing Star Wars Battlefront II recently. Possibly because the game was discounted on many outlets on May 4th and may be due to the success of Andor season 2. There’s a lot more people streaming it as well as videos on YouTube. Whatever the reason, it is always good to see a deserving game enjoying a renaissance. Star Wars Battlefront II was blighted at launch, back in November 2017 by some egregious business decisions and it took nearly a year for the game to recover from the negative publicity and player animosity. Setting this historical debacle aside for one moment, there was always a handsome and engaging game to be found. One that used the licensed intellectual property well. Which is why I recently reinstalled the game and resumed playing its multiplayer mode.
However, the welcome return of this old favourite has also been accompanied by another not so pleasant reappearance. Namely the dreaded “Error Code:721”. This error code in Star Wars Battlefront II typically indicates a failure to connect to the EA servers. It is a bug that has plagued the game throughout its lifecycle. Furthermore because Star Wars Battlefront II is no longer being actively patched by EA the error code has made its presence felt once again, now that people have resumed playing. While it's often only a temporary server issue often linked to the number of people playing, some users have found success with the following troubleshooting steps to work round the problem.
Check the EA Servers: Wait for a bit to see if the issue is a general server outage.
DirectX12: Ensure DirectX12 is disabled in the game's video settings and that Windows Defender isn't blocking it.
EA App: If playing on PC, try launching the game through the EA app and adding "-dx11" to the advanced launch box.
Persistence: Keep attempting to connect to the game by repeatedly clicking the "Connect" button.
Restart: Rebooting your PC or console might resolve the issue.
Verify Game Files: On PC, you can verify the game files through the EA app to ensure they are not corrupted.
I find that the best way to beat this bug is by hammering the “connect” option and eventually my game client will be flagged as being online. Hopefully if you’re having a similar issue, one of the above suggestions will work for you. As for Star Wars Battlefront II, it is still worth playing. All lootbox mechanics have been removed and cosmetics skins are now unlocked by gameplay milestones. There are a variety of game modes and you can play in either first or third person, depending upon your preference. It should be noted that you can also shoot Ewoks. At present the servers are active and there is no major difficulty finding a multiplayer game. Eight years on the game is still visually stunning and exudes the Star Wars aesthetic. Furthermore, the recent renewed interest in may well create momentum for a Star Wars Battlefront III.
