On this week's installment of "Wow, It Would Have Been Really Stupid If They Said Literally Anything Else", EA executives remarked that Titanfall won't experience the same kind of shaky launch that Battlefield 4 did. The comment came during the company's quarterly earnings call, where assuaging investor concerns tends to be a priority.
EA chalked up the Battlefield 4 debacle to trying to simultaneously launch on two new consoles, two existing consoles, PC, and a mobile app. "We were pushing innovation heavily and we're delivering 60 frames per second gameplay for 64 players plus the ability to connect via mobile tablet as a commander into the product, coupled those with some very innovative features in the gameplay side," said EA executive vice president Patrick Soderlund.
However, EA's confident that Titanfall will launch more smoothly than Battlefield 4, because it's learned from its mistakes. There was an alpha to stress test servers, and according to Respawn's Jon Shiring "During our small closed alpha, we rolled out three new server builds and completely moved players from one build to the next without interrupting gameplay. Players never noticed a difference."
This all sounds fine and dandy, but these are the exact things that you're supposed to say leading up to the launch of your mega-title. We won't have a semblance of a clue until March 11 about how the servers handle the strain of Titanfall being in the public's hands. Until then, I'm going to take these assurances with the world's largest grain of salt.
Get more destructoid: We're indie-run, blogging for the love of it, and our site will always be free. Optionally, you can support us and get: (1) Faster pages from our cloud server (3) Wide(r)screen (3) No big ads on Dtoid, Japanator, Tomopop, or Flixist (4) Auto contest entries, and (5) Dibs on betas & downloads. Try it out
Unsavory comments? Please report harassment, spam, and hate speech to our moderators, and flag the user (we will ban users dishing bad karma). Can't see comments? Apps like Avast or browser extensions can cause it. You can fix it by adding *.disqus.com to your whitelists.