You expect rough MMO launches - you don't expect FPS titles to follow suit. And you certainly don't expect it to uncover serious issues in modern game reviewing.
It's been two weekends now since Battlefield Bad Company 2's launch. Two weekends of endless re-installing, Punkbuster troubles, log-in issues, and flaky servers. Two weekends of seeing the little news ticker at the bottom of the game's UI telling me that 'EA is aware of the problems and working toward a fix'...
And it's not just me - these issues seem spread across the BC2 userbase, according to the game's own forums. Each fix seems to only reveal another problem over the horizon, too, and a post on EA's Battlefield blog today reveals the full breadth of the issues. Here's just a taste of the fun.
Server Browser bugged: All the following browser issues are things the team is currently working on improving. Too slow This is caused by the current browser system. - A new system is being developed by the BFBC2 PC team to improve the server browser Displaying inaccurate number of players connected on game servers - This is caused by the difference in server status between when the refresh was initiated and when the results display. No ping displayed - This is caused by Windows admin privileges. To view ping in the server browser run BFBC2.exe with administrator privileges.
Server Browser bugged: All the following browser issues are things the team is currently working on improving.
Too slow This is caused by the current browser system. - A new system is being developed by the BFBC2 PC team to improve the server browser
Displaying inaccurate number of players connected on game servers - This is caused by the difference in server status between when the refresh was initiated and when the results display.
No ping displayed - This is caused by Windows admin privileges. To view ping in the server browser run BFBC2.exe with administrator privileges.
And that's just one issue. The blog post mentions eight issues that have needed fixing, or are being worked on. And not all of those fixes even work as planned. The Punkbuster issues actually require the old Punkbuster files to be removed by many users, before the manual update, for instance.
For a publisher like EA, and from a developer as skilled at rolling out online games as DICE, it is - frankly - a massive cock-up. These are issues that really should have been nailed before release, and combined with the game's semi-dedicated server system (only recognised and licensed server hosts can set up a game, and they have to wait for serverside updates to be delivered), it means the hosts themselves even have issues keeping up to date with the updates.
The corollary of this, for smaller countries like Australia, is that it can in turn be very hard to find a game, as most servers seem to only last a few days before disappearing. There were about twenty local servers at launch - we're now lucky to find a dozen. It's a moot point, anyway - we can't join any of them at time of writing.
All that said, it is great to see the EA blog being so open about it all, and working so hard on this. But we'd much rather a working game.
Issue: 116 | September, 2010