Bad news, everyone: the giant 42-player Civilization V game that was turning into the most enjoyable spectator sport of 2015 (at least for me) has broken down, crushed by the weight of its own awesomeness.

A few days back the entire game‚ÄĒwhich as a reminder is an AI-only, 42-player showdown of absolutely epic proportions‚ÄĒground to a stuttering halt. Many had long feared this day would come: the thought of that many civs moving that many units sent shivers down my PC's spine (indeed, it's reported that before the end the game was taking twenty minutes just to load, there were so many units and cities on the map).

For 11 days, though, everything went well: there were updates, maps, status reports and even gifs like the one below showing how the war was coming along.

Advertisement

But then, on day 12, it happened. On turn 239, the game crashed during Japan's turn, with the suspected cause being that leader Tojo was building more naval units in a single turn than the game could manage.

Despite the best efforts of organiser TPangolin, and some charitable folks donating new PC hardware for him in the hopes of speeding up debugging (and game performance), the game has failed to return from the dead.

Advertisement

Its only hope now is that the Battle Royale's save files are in the hands of 2K support (2K published Civ V), who will take a look at the cause of the breakdown and hopefully fix it. But given the scale of the game, and the fact it was using mods, you shouldn't hold your breath.

If the doctors at 2K can fix it, awesome! If they can't, you can read up on recaps of how everything went down here.