Popular Posts of the Week
Another new piece in my store is from the Disney XD cartoon, Star VS the Forces of Evil. I found this piece of pixel art on a tumblr page,...
You voted and here they are! Your Top Ten Hotties in the Video Game Industry! 1. Tommy Tallarico Tommy Tallarico is a v...
My favorite website, http://www.sugarbank.com/ has now added another site to its many sister sites called SugarJoy. ht...
Apr 4, 2008
New Map Pack for Call of Duty 4 Breaks Xbox Live
Surprisingly Microsoft must have not anticipated all the people who would be downloading the new map packs for Call of Duty 4 today, cause we done broke it and now Microsoft is rushing to fix live before all the angry COD4 fans join forces and take down their headquarters in Redmond, Washington.
Gamers trying to download the new maps for Call of Duty 4 today, were soon greeted with an error message "Can’t retrieve information from XBOX LIVE, please try again later. Status Code: 8015000a". Apparently the servers couldn't handle the mass amounts of gamers trying download the maps all at once and we broke the system.
Microsoft and Infinity Ward are aware of problem with Xbox live and the map download, and are trying hard to fix the error as quick as possible.
There is away around the error but you still gotta wait a long time to download the maps. First, go into Call of Duty 4 to download a new update for the game and then restart the game. Head into the multi-player section and there will be an area to download the new maps. There maybe an error message there too, but if you try it once or twice the download will start.
You've got to wonder though, with the Xbox Live crash at Christmas time and now this, what's going to happen when Xbox Live is attacked by hundreds of thousands of Grand Theft Auto IV fans on April 29th. Microsoft is smart enough to prepare the servers for Halo 3 but are they smart enough now to realise they have to start anticipating major Xbox Live traffic events or they will continue to allow their servers to keep crashing like this?
Guess we'll see.