Zone Game 1

The first game of the revived series of Zone Games took place on 22nd September 2007.

The Battle for Mercury

Factions: Bios vs Iron Coalition

Commanders: Spidey vs Bacon

Map: East West

The players were arranged into their teams by an ASGS poll that ran for the week leading up to the game. There were a few problems in this sorting with a small number of players not being sorted into teams as they had requested. Far more people had either indicated that they were not going to be able to play in the poll or had logged in with the incorrect callsign. Tigereye and BlackViper managed to get most of these people sorted out before game time with help from some of the @Allegs.

The initial game started on a custom map. Unfortunately due to a problem with the map file it was discovered that Bios had 3 garrisons and IC had only 1 rather than the two apiece situation intended. After a short time the game crashed and players reassembled in the lobby.

A second game was launched on the East West map and this was played to the finish with Bios defeating IC.

Despite some definite flaws this game was heralded as a success and the mistakes made this time shall be avoided in future Zone Games.

DataNet File: 00151 - Battle for Mercury

Date: 23.09.2157

Report filed by: Nick H

       Last week's focus was on Mercury and the inner planets, so it should come as no surprise that BIOS and IC battled for the reportedly He3-rich Mercury. It should also come of no surprise that the Gen-7 BIOS -- noted around the system for their cold blooded killing instinct -- managed to secure the rights to Mercury. Surprisingly, it seems BIOS was able to out-organize the IC.

       Belter scavengers in the area reported that there were hundreds of destroyed ships after the battle: both BIOS and IC. With the IC attempting to make a better name for themselves in recent times, this loss is expected to be a setback. With BIOS being so tight-lipped about their operations, we won't know what spoils they will have managed to pull from Mercury, but it is to be assumed that if BIOS took an interest in it, there is something there.

       As always, the IC had something to say for itself.

---Start Report---

Time: 23:24 PM (UTC)

Date: 23.09.2157

Rank: Captain

Surname: Johnson

Tag: #0260530-C-117

Section: Office of Naval Intelligence

Public Battle Report No: #000103

Priority: C-64

     Greetings, fellow Coalition soldiers and those who are under our protection.

     I regret to inform you that our engagement with the BIOS over the surface of Mercury did not fare as well as expected. We did not manage to gain the planet, but our soldiers fought bravely, and incurred a great number of casualties upon the enemy.

     During a crucial part of the battle, a spatial anomaly caused our main communications satellite in orbit over Mercury to cease functioning for a few minutes. By the time it was brought back online, the BIOS had used their cowardly tactics to sneak Stealth Bombers into key sectors, by this time there was nothing we could do.

     The means by which the BIOS won the battle shows that they still do not have the hearts of real men to face us in battle as worthy opponents.

     The Coalition wishes to commend Fragtzack for his heroism and inflicting the greatest damage upon enemy forces.

     We still stand strong.

---End Report---

       As much as it pains this reporter to admit it, it doesn't seem the Gen-7 BIOS is stoppable. With their interruption of communications, who knows what else they will think up next. What will be their next move? How will Gen: Eve and Gen: Adam fare, now that they have been seeded on Earth?

     More as it develops, of course.

- - - - -

>>Red_Queen: Node: 1413:10181

I've said before that the BIOS are the worst threat to the system!

>>Monk_312: Node: 51414:101091

The IC are fools if they expected to find something on Mercury. There's no way they would have survived. I wouldn't be surprised if that satellite malfunction was due more to the sun than to the BIOS.

>>EmDash: Node: 1514:1891717

You can't deny that it's something BIOS would do.

>>3rd_Rail: Node: 01918:1171651

I'm staying as far away from Mercury as possible. It was bad enough without the BIOS there.