RED ALERT CHRONOLOGICAL NARRATIVE
Note: This is drawn from the rules and scenario background. I've presumed the Dates are in the form BD-Epoch#-Day#, in a kind of Julian calendar form. This isn't anywhere detailed, but the Epoch number at least seems to marry up with the text. Epochs seem to last about 1250 "days", with a day being an unknown amount of time, but presumably a human sleep cycle amount of time. BD = ?
Assuming this dating is correct, the War of Confederation Succession can be seen as a flurry of initial battles in Epoch 16 using the leftover existing fleets, and a process of re-arming on both sides. The Othorians apparently build starships equally for both sides, and other neutral worlds are drawn into the conflict zone(s). Towards the end of the Epoch there is a number of space hazards that impact military operations. Epoch 17 is very quiet (or unreported), potentially due to military and resource exhaustion, with a further escalation in Epoch 18. Epoch 19 sees a swift Confederate stealth attack on the Commonwealth home world as a peace treaty gambit.
BACKGROUND
After the joint effort by all known systems and races in the galaxy to defeat the Krawl invasion in the early part of the 15th epoch, the tension between the outlying planets and the Commonwealth Alliance again began to mount. Coming to a head during the High Council meeting in the second session of the 16th epoch, which traditionally was still being held on the Commonwealth home planet, a number of delegates calling themselves the Confederation stated that their planets were no longer willing to accept the Commonwealth’s self-serving priorities and trade deals, and walked out of the meeting.
Although the Commonwealth Alliance didn’t like the idea of a rival galactic organization, an unwritten truce came into existence, with the thought that the Rebel Confederation would eventually collapse under the financial stress of maintaining a new governing body and its fleets. But despite these challenges, or maybe because of them, the Rebel Confederation proved to be a resourceful federation that continued to grow.
In time, the unwritten truce began to disintegrate. The Rebel Confederation, armed with a small number of military space fleets still in service after the war with the Krawl, would gain strength and challenge the Commonwealth Alliance’s interplanetary peace-keeping force, which was once the most powerful force in the galaxy.
As history writes, the only difference between the Commonwealth Alliance and Rebel Confederation ships was the colour of their fleets.
Opening Salvo: Uneasy Truce (BD-16-0611)
After almost a generation without trouble, a small task force from the Commonwealth Alliance and Rebel Confederation came face to face in a distant uncharted sector of space. Both commanders reported that the other side fired the first volley; but it didn’t matter because war had arrived. The Commonwealth Alliance kicked their propaganda machine into overdrive and managed to label the Confederation as the aggressors, branding them as rebels. The High Consuls of both factions had known this day would come and had prepared accordingly. Building on similar technology after the joint effort to defeat the Krawl invasion, neither faction could claim a military advantage. It therefore seemed that the task force commanders deployed in the near and far reaches of the galaxy would determine victory.
DoW: Declaration of War (BD-16-0618)
The High Consuls of both factions quickly dispatched additional units to the sector. The sector, however, had remained relatively quiet after the brief skirmish of a few days earlier. With new forces arriving almost hourly, the commanders were eager, ready and willing to prove their military abilities. The Commonwealth commander formed up in a traditional line of battle, while the Confederation commander used a small, unnamed planet to mask his initial deployment. Neither side backed down; it therefore would be a fight to the death.
#1: Cardinal’s Belt (BD-16-0816)
Almost halfway across the galaxy near the sector know as the Cardinal’s Belt, news of the declaration of war reached the two task force commanders. Although there was nothing really to gain in this sector, except for bragging rights, the two commanders set about vying for position before launching their attacks.
#2: Uncharted Supply Base (BD-16-0820)
Spies have reported that there is a pre-war supply base in the sector. The report did not state its exact location, but intelligence places the base near the enemy deployment. Your orders are to break the enemy line of battle and, once the opposition line is broken, locate the supply base and occupy it. The enemy, it also seems, is aware of the supply base, but intercepted transmissions report they also do not know its exact location.
#3: The Supply Base (BD-16-0821)
The enemy and we have both located the hidden supply base. Although both wings of the task force have not yet joined together, we are moving forward at once, with the hope that aggressive manoeuvring and careful resource management will allow us to gain control of the planet known as Acme and its hidden supply base.
#4: Triangulum System (BD-16-0825)
In a nearby system, there are a number of planets that would be an ideal location for a supply base. But before this can happen, all regions in the system need to be cleared of enemy forces and the planets controlled. The enemy, once again, is totally aware of our plans, even before the plan is set in motion. There must be a spy in the High Consul, but it is of little concern out here in space, especially when facing yet another enemy task force.
#5: Triangulum System II (BD-16-0827)
This region of the Triangulum system has two very large planets, and negotiations are already well underway with the officials on the larger planet of Kale. The enemy has also sent an ambassador to the planet in the hope of gaining the support of the Kale officials. We only have a small force of ships near Kale. The remaining ships from the task force are deployed near Kale’s sister planet Lyra. The time for negotiations may have passed and if they break down, we are ready to strike and destroy the enemy and take over the two planets by force.
#17: Evacuation (BD 16-0831)
The transport ships are all loaded and the fleet commander hopes to have the evacuation completed before any trouble arrives in this sector. But her hope of a quick getaway and safe passage will not be realized, for the enemy ships have begun to arrive and are currently moving into position to set up a blockade to prevent our departure.
#19: Meteor dodge (BD 16-0924)
Nothing has gone as planned. Not only have we made contact with and started to engage the enemy fleet, we are now also under attack by the elements! A meteor shower came up out of nowhere. This has slowed the fighting somewhat, as we are forced to dodge these pesky little chunks of rock and debris, but they are more of a nuisance than a threat.
#18: Sector 44 (BD 16-0928)
It looks like there will be another struggle for control of Sector 44. Both factions have arrived and have deployed with plenty of supplies and support vessels. Casualties are sure to be high, but we will report back when victory has been achieved.
#6: Cardinal’s Belt II (BD-16-0929)
The fighting in the eastern-most sector of the Cardinal’s Belt has flared up again. Both factions have come to realize that sending additional units to the sector is pointless; however, neither faction is willing to give up this sector of worthless rock. The order of the day therefore is: Clear the enemy from the sector and break through.
#11: A welcome addition (BD 16-1001)
News that we are soon going to receive a brand spanking new carrier unit is very welcome indeed. It seems that the Othorians have joined our cause and are beginning to supply some much-needed starships. Rumour has it that we are getting three new carriers. But of course, such great news did not remain a secret very long and we have learned that the enemy has responded with their own carrier unit to be deployed in the sector. All are wondering, however, if this new weapon and its mass of short-range carrier fighters will bring with it a change in tactics.
#7: Cardinal’s Belt III (BD-16-1008)
The Rebel Confederation is on the run and only a small rearguard stands in the way of the Commonwealth clearing the rebels from the Cardinal’s Belt once and for all. No quarter, no mercy is the order of the day, but the outgunned Confederation commander is an experienced foe.
#12: The weapon of choice (BD 16-1022)
After a few weeks, the carrier unit has proven itself very worthy in battle. High Command is requesting additional carrier units and the Othorians, it would seem, are willing to oblige. We in the ranks are starting to wonder what really is their motive. It seems that for every carrier unit we field, the enemy is doing the same. It is an arms race, but neither faction is gaining any ground.
#20: Planet Polis under siege (BD 16-1022)
Not often in recent times has the Commonwealth Alliance and Rebel Confederation been willing to work together. But when the planet of Polis found itself in the direct path of a major meteor storm, both fleets in the region determined the only way to ensure the safety of the planet was to work together. But as both sides were well aware, there was no telling how much collateral damage might occur on enemy ships during this valiant effort.
#8: Twin Sisters (BD-16-1215)
The Twin Sisters sector is a very crowded piece of space. With two planet systems of similar sizes and an unstable asteroid field that hangs between the two planets, neither faction has dared to venture into the sector to date, but now it seems that the risk may be worth the expected rewards. The two known planets near the asteroid field are believed to be void of any life.
#22: Near Star Region (BD 17-1015)
The Near Star Region is a very treacherous piece of space, yet the sector may provide planetary resources that can aid the war effort. No one has dared to venture so near the rift for some time, but the risk may be worth the expected rewards. The two known planets near the rift are believed to be devoid of any life.
#23: Near Star Region (BD 17-1229)
Upon further exploration of the Near Star Region, it seems to contain a series of space rifts. This is our first encounter with a rift that is strung out almost across the entire sector. If it moves it could be a blessing, or lead to some serious ship shifts. Looks like the enemy fleet is positioning to also take advantage of this rift. We are prepared and ready for whatever is about to happen.
#9: Dreadnoughts (BD 18-0121)
Although fighting near the frontier has escalated, both sides have been able to hold their own. High Command, however, has intercepted a message that the enemy is planning to reinforce the sector with one of their dreadnoughts. High Command has therefore realized that the only way to win here is to counter the move by sending in one of our own dreadnoughts.
#21: Another day, another space rift (BD 18-0202)
Space Rifts... We have encountered our fair share of these space features and they seem to be more prevalent in our northern-most sectors. Some reports refer to them as space ribbons or folds in space, and for the most part they all share the same traits. When one develops in a sector, it might snake around for some time before it fades away. We have used them as cover in battle and have learned to make rift jump movements. Of course, the main issue when in the rift is the possibility that it may throw the ships. When tossed to a new location, the landing can really shake you up and one never knows where the fold in space will take the ship. We have arrived near Sector 141 to explore a rift that was reported here, but it looks like we will have to deal with an enemy fleet first.
#10: They captured our Dreadnought (BD 18-0210)
Reports have been received that the space platform in Sector 7? has been destroyed. To make matters worse one of our dreadnoughts near the platform, under repair and with the ship's crew on leave, has been captured. Survivors from the incident report that Commonwealth spies along with an elite force of commandos boarded the ship and quickly overpowered the security team. Shortly after this, a Commonwealth fleet arrived in the sector and demanded the platform surrender. When they refused, the platform was destroyed and only a few crew managed to escape. The Commonwealth fleet remains in the sector. Your orders are to prevent the Commonwealth fleet from leaving the sector and to recover any survivors.
#13: Vice Admiral on deck (BD 18-0303)
A second flagship is joining the fleet, and it is commanded by Vice Admiral Mersey. During the Krawl invasion, Mersey captained one of the battleships in the fleet and was very well respected before he received a transfer. Although his flagship will add another very powerful ship to the fleet and will create a stronger command structure, the question becomes, will having two command vessels create some friction and a rivalry that could detract from the mission at hand? Only time will tell.
#14: Sector 72 (BD 18-0331)
The battle lines in Sector 72 have remained intact for some time now with neither side gaining any perceived advantage. A Vice Admiral is on his way with orders to break the stalemate in the sector and break through enemy lines. Of course, our spies report that the enemy is aware of the move and has directed a second flagship to the sector as well.
#15: Commonwealth Space Platform (BD 18-0401)
The Commonwealth Alliance has recently completed construction of a space platform near the planet Rigel. The governing body of Rigel has always remained neutral in the struggle between the Commonwealth and Confederation, but with this new development, Rigel has requested Confederation help. The High Council has responded and ordered a Confederation task force to proceed to Rigel and destroy the Commonwealth space platform. The Confederation fleet, arriving near Rigel, finds that the Commonwealth fleet has prepared a trap.
#16: Hostile Seginus (BD 18-0407)
Our fleet has arrived at the outskirts of the frontier near the planet Seginus. We have attempted to contact the planet's military governor, but before we could open communications stating that we come in peace, an enemy fleet arrived in the sector. We have just been attacked and believe the attack actually came from the planet's space platform not the enemy. Orders have been sent to all officers and we are preparing for battle.
#24: Commonwealth Raiders (BD 18-0721)
The raid did not go at all as planned.We are attempting to return to base with the Confederation in hot pursuit. And now we can see that enemy ships have arrived to block our way out. This was a mistake. I told the High Council this was a mistake. But not, it was to be an easy task, get in, get out fast, nothing to worry about. Well we will have to fight our way out now, but in my opinion the prospects do not look good.
#25: Kepler (BD 18-0729)
Call me crazy, but why would anyone want to inhabit a planet located smack dab in between two belts of the Kepler asteroid field? Until now there was no reason to even venture into this region, but the High Council received a request from these fine folks to join the Confederation. The Commonwealth must have also gotten word of their request, for as we approach the planet Kepler, we have made visual contact through the asteroid belt with the Commonwealth fleet.
#26: Meteors & Planets (BD 18-0822)
This sector of space is, and has always been, subject to more meteor occurrences than almost any other sector in this part of the system. The prospect to gain control of the sector and its two planets has, however, once again brought us and the enemy’s fleet back to the sector.
#27: I Believe it's a Rift (BD 18-0823)
A space rift is in the process of forming directly to our front. It is now just between our fleet and the enemy’s fleet. Neither side has taken any action – I expect they are as amazed as we are that this thing has materialized and is taking shape. We would like to pull back from the sector for now, but I will await your confirmation before taking any action. Too late! The enemy is on the move and they have deployed into attack formation.
#28: Commonwealth Guard Destroyers (BD 19-0517)
Not expecting an attack in a region so close to their capital, the Commonwealth High Council called for the immediate deployment of both of their guard destroyer units. The only reason we have made it so deep into Commonwealth space is because of the speed at which our fleet has been moving. Led by our elite fighter squadrons, we were able to bypass most opposition and are now within striking distance of the Commonwealth home world sector. We probably can’t hope to make a direct attack on their home world, but we sure can scare the ***** out of them.
#29: Commonwealth Space (BD 19-0518)
We have broken through, and after receiving replacements, which brought us back to almost full strength, we are moving into Commonwealth home world space. We’ve been reinforced by a powerful dreadnought direct from the Othorians. We received word from the dreadnought’s captain that this is the last such vessel produced by the Othorians and that production has now completely shifted to carriers and carrier fighters. It must have cost the Confederation High Council a pretty penny, but that is of little concern out here; we are just happy to have this beast on our side. As we approach the outlying planets of the Commonwealth home world, it would seem they have called forward every ship possible.
#30: Commonwealth counter-offensive (BD 19-0519)
With the possibility of ending the war right here and now, or at least having the Commonwealth sue for peace, the Confederation High Council has sent another task force in support of our efforts in this sector. This new force, along with what remains of the units from our last engagement, has redeployed and now waits for the Commonwealth counter-offensive. Given this breathing space, the Commonwealth has also brought in a new task force of their own from a neighbouring sector.