hot  /  reviews  /  video  /  blogs  /  forum

Capcom shutting down Resident Evil Outbreak servers

Mar 04 // Nick Chester

Last week, when Konami decided to pull the plug on their servers that backed Metal Gear Solid 3: Subsistence's online play, the community was up in arms. You see, that's a game that people still actually play; it was released only one year ago.

On the other hand, when Capcom announces they're going to shut down the Resident Evil Outbreak: File 1 and 2 servers, it's kind of hard to believe that anyone would care.

Capcom regretfully announces that the server for our Playstation 2 online game Resident Evil Outbreak: File#2 will be closing at the end of March 2007.

Since Resident Evil Outbreak File#2 was released in August 2005 , Capcom has provided a server enabling consumers to experience the online element of this game free of charge.

Regretfully, conditions now dictate that we must close down this server effective from March 31, 2007. Naturally it will still be possible to play the game offline, but the online component will no longer be available.

Following the forum announcement, a five page thread erupted, with pages four and five going to s**t ... quite literally. For the love of God, don't click on page four, as it's not safe for work. Or home, for that matter.

 Reblog (or) Blog Reply




Nick Chester, Former Editor-in-Chief (2011)
 Follow Blog + disclosure Tips
Editor-in-Chief @ Destructoid.com nick at destructoid.com  more   |   staff directory

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

 Setup email comments

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.
advertisement:




Back to Top