Dawn

[attack_condor]

Hello everyone -

I have just registered as a user on this forum, and I enjoy creating AARs. I'd like to offer my hat into the ring. I have begun a BM game (thank you Mr. Kwok for your fantastic work - and anyone else who helped with the production of the game and mod!) and am currently at 2409.9 in it.

I'll hold off more turns until I get the readers up to where I'm at. A bit of FYI - the empire is called "Colonial Dawn" and is Terran with an overwhelming desire for knowledge. Perhaps not always a good thing...

Anyway, please look for the posts and I hope you enjoy the read.

[attack_condor]

Nekkar IV�homeworld for the Colonial Dawn Empire�
2405.8 (sorry about the wrong year posted in my opening post)

Chairman Lomax rubbed his eyes. He was looking at yet another system report. He smiled. It was late, he was tired, and he was happy.

Well, he was supposed to be happy.

Success brought happiness.

Didn�t it?

�34 colonies in ten systems� he read aloud. In less than six years. The Dawn�s growth was � indeed � amazing. And he had confirmation of that. The Chethrod race had just sent him the very same message last month. How right they were. And how instrumental they were, although they probably had no knowledge of it. The growth of the empire had coined the phrase, �The rising of the Dawn�. And it was all because of the Chethrod. A seemingly insignificant oversight, in a series of negotiations during that first contact almost two years ago may well have catapulted the Dawn into a position of prominence they may never relinquish.

The Chethrod were encountered by the Dawn in the Sheliak system. The frigate Leeds (or, more correctly, Colonial Dawn Ship Leeds � CDS Leeds) had warped into the system to find two rock worlds that could be colonized. They also encountered the Chethrod. Of note were the 30 fighters that orbited the planet they had colonized. The message from the Leeds also mentioned one more important fact. The Chethrod inhabited gas giant planets.

CDS Southampton, another frigate, joined Leeds on the Sheliak side of the warphole joining Sheliak to the Praxis system. Negotiations were initiated by the Chethrod and they were fairly basic � colonization in each other�s systems, trade, and re-supply between both empires. As a standard response, Dawn made a counter-offer: an observation of non-aggression in neutral systems, but the prohibition of establishing colonies in each other�s systems. The offer was fair, and a logical first step. Lomax knew not to jump at the first offer (it wasn�t good business, after all), and always ask for what you want � only then settling for what you need. The want, in this case, was simple.

Dawn wanted everything. Everything Chethrod had researched. The request, of course, was worded a bit more eloquently, but it was still there: �We require all research � including racially unique research � to ensure our two races can coexist peacefully.�

To the surprise of everyone, the Chethrod agreed.

The science council was ecstatic, to say the least. The big prize, of course, was the secret to establishing colonies on gas giant planets.

And just like that, the Dawn had opened up a treasure trove of locations. No less than ten new worlds were at least medium sized gas giants with oxygen atmospheres. Dawn had, indeed, risen.

Lomax returned to the present and re-read the recommendations of the council heads within the empire. The question was whether or not to allow contact with more races. Doing so might be profitable, but there was always the concern to secure the position of the empire before moving on to a new system. They actually had a system with two planets to colonize they hadn�t even got to yet. The Forlorn system had two planets yet to be colonized. It was secure with only one warp point, and that was to another system � Samora � that only connected to Forlorn and Sirius. Sirius was a Dawn stronghold. Practically speaking, all ten systems were Dawn strongholds since no other empires were in the systems. Lomax decided to keep it that way. Choke points were established in three systems that effectively prevented any contact if so desired.

Another race, the Cue Cappa found that out, when their frigate emerged from a warp point in the Ushphada system, and was greeted with a pair of fourth generation capital ship missiles. A second frigate also met that same fate, before the Cue Cappa initiated negotiations. A treaty was finally signed with the same provisions as the Chethrod treaty � stay out of our systems, and give us your research. They objected, of course, but the Dawn�s position, like their hold on the warp points, was unmovable. The Dawn didn�t need the Cue Cappa. Which reduced the Cue Cappa �empire� to that of mere competition.

And no corporation gives their competition a chance to become equals.

With 89 second-generation research facilities and 39 more scheduled to come online, the capability of the Dawn to develop new technology was staggering. They already had shields, energy stream weapons (lasers), and new kinds of point defense technology that included the laser, small seeking missiles and a very basic but effective version of the old shotgun called the flak cannon. The universities of the empire were also adding to the knowledge base of the scientists here, and fiscal policies were continuing to reduce expenditures, allowing more and better facilities, ships, and units.

It was a dream. New ships were being designed. Mining operations had left the planet surfaces and were now being conducted by company ships in asteroid fields. The Dawn was rising and nothing could stop it.

But Lomax knew that there would be competition. Somewhere, there would be an empire, or perhaps several, that would challenge the Dawn and its lofty technology. Lomax kept that thought foremost as he made his decisions. He knew it would happen. He just didn�t know when�

[attack_condor]

2405.8...

Chazzwazzer Star System�
Onboard the CDS Harvester 004 in asteroid field #3�

James Cabrera watched as the supply transport undocked and departed from his ship. The completion of the supply base on the new gas giant colony in the system meant that his crew could finally go off of their rationing and get back to eating regular meals. Regular, as it were, for a crew whose lives would be spent mostly in space with chunks of destroyed planets and comets as company.

He was in command of a 600kt freighter configured as a radioactive resource harvester. The crew knew her by a less ostentatious title: �double-oh-four�. His ship�s size allowed four of the robotic miners to be carried and still have a decent engine compliment. Other Harvester configurations were available from the design bureau and could be built to make the most profitable use of a particular asteroid field. Asteroids that were high in mineral content would be mined by a �four-double-oh�, while asteroids rich in both radioactive resources and organics � Cabrera winced a bit at visualizing that particular combination � would be mined by a Harvester 022; known simply as a �twenty-two�. His Harvester was one of eight the empire operated, and they were producing over 80,000 units of resources a month.

Cabrera watched as his display console monitored the quantity and purity of the harvested material. Projections put this particular field at 283% of a standard mine output. The projection for this particular ship in this particular asteroid field was over 11000 units of radioactive resources each month. Both he and his crew would be handsomely compensated for their efforts. He did have one concern, and that was the fact that the corporation did not provide protection for the freighters. The standard response to such queries was that protection was unnecessary since no other known empires were in the Dawn systems.

Still, it wouldn�t hurt to explore the possibility enlisting a little �assistance��

Samora Star System�
Onboard the space yard ship CDS Mexico City

The crew of the ungainly ship fired its engines and began the slow transit from Somora to Pantrissa. There, the ship would begin to upgrade the defenders of the two warp points into non-Dawn space with the latest in upgrades. This was the role she was designed for � allowing the defense ships to remain on post while the planetary space yards concentrated on producing colony ships as fast as possible�

Usphada Star System
Usphada Design and Combat Simulation Center

The rings of Usphada I were beautiful to the observer from space. Even more so that, only two sectors away, her sister Usphada II matched her brilliance with her own set of rings forever in orbit around her.

All of which meant absolutely nothing to the men and women in the darkened room of the design complex. Members of the Navy were also on hand with the researchers as all were about to witness the trial run of a point defense ship design. The classification was given the name Artemis, and she would join the England class frigates and Canada class light cruisers as active ships of the Navy.

Research had been progressing on an effective deterrent to a massed fighter attack by an enemy. The Navy had proven � albeit only three times � that its weapons could outrange anything opposing them, but the lack of an anti-fighter weapon always nagged the senior officers of the Navy. Artemis was to be that answer.

The simulation was set up with the Artemis facing off against a Dawn frigate with two missile launchers. The Artemis continually was able to engage the missiles at range (almost 100 km from the Artemis) and was able to get three shots off within that time needed for the missiles to close.

Then the fighters came in the next simulation. This time, the results were less spectacular. With two shield generators, almost 600kT of armor and a shield regenerator, Artemis was a tough nut to crack; but damage was taken. And this was against the enemy fighters that the Dawn scientists knew about. They were about to cancel the test and stop production when a Navy commander asked to try an idea. He paired the Artemis up with a Canada class light cruiser, but replaced one of the cruiser�s armor sections with a flak cannon. He also quadrupled the number of fighters. When the simulation started, he closed the two ships almost head on into the fighters, but stopped when they were within 200km of the fighters and then turned away from them. He then flew away from the fighters slowly until they came within the Artemis� flak envelope. Artemis fired, and fighters took damage, but they kept coming. Artemis did not fire a second salvo, however, but leapfrogged in front of the cruiser, which fired her own flak cannon. This pattern repeated until the two ships had destroyed or disabled every fighter with the shields absorbing each hit and having time to regenerate as the ships leapt over each other.

Artemis had proved herself and production was approved�

(Question for the moderators: would screenshots be best posted as attachments?)

[attack_condor]

2405.9

Haphik warp point...
...onboard CDS Southampton...

The voice was soothing. Feminine. Almost alluring.

Research demonstrated that such a voice was comforting in times of stress.

Like, well...now.

The operations officer turned her head when she heard the voice. Lieutenant Katherine O�Rourke knew the voice. Somewhere inside her, she wondered why it couldn�t be a strong, comforting male voice, but those thoughts were pushed aside as the soft voice beckoned for attention.

�Warning. Warp point breach imminent. Warp point breach in thirty seconds.�

O�Rourke opened a channel to the Southampton�s sister ship on patrol with her.

�Southampton calling Dover, Lieutenant O�Rourke on duty. Captain on the way. Dover, are you getting this?�

O'Rourke had to make sure the computer wasn't generating a false breach...

...onboard CDS Dover...

�Southampton, Dover�we confirm warp point breach in�twenty seconds�missiles set and...�

The duty officer followed protocol. Haphnik was quarantined � as was all of Dawn space. No one was to get into the area until the corporation was ready for them. That point was about to be made with emphasis.

�Southampton, this is Dover � we have missiles away, repeat missiles away!!�

Then, Dover began to pull away from the warp point. She probably had a longer combat reach than whatever was coming through the point, but there was no sense in sticking around to find out.

...onboard CDS Southampton...

Captain Harrison arrived on the bridge to hear the voice announce what everyone knew would happen.

�Warp point breached.�

Lieutenant O�Rourke filled her captain in:

�Sir, we have an unknown breach of the warp point. Dover has already released missiles and is pulling behind us. We are ready to fire on your orders. Our position is 150km from the point, sir.�

Captain Rodney Harrison took the report in and winced. His initial thought was that some poor Cue Cappa bastard is not going to have a nice day today.

He was wrong...

...onboard the Sergetti frigate Celea...

The Sergetti commander had heard the rumors about the Haphnik warp point. About ships that entered only to be not heard from again. He didn�t believe the stories, but more to the point he was sure his frigate would be able to handle any challenge. He had the second generation of weapons his race had developed. He realized his mistake when, upon entering the system, he found two missiles bearing down on his ship.

The Sergetti point defense fired when the missiles were in range...

...onboard the CDS Southampton...

Lieutenant O'Rourke brought her ship alongside Dover, with about 10,000 meters separating them. Together they pulled away from the intruder...

...onboard the Sergetti frigate Celea...

The point defense did well, knocking out one missile and almost knocking down the second. It was a microsecond too late...

The missile impacted the bow of the Sergetti frigate, and the resulting heat generated burned almost all of the ship�s armor away. The shock to the ship was measurable, and the crew wasn�t able to respond for a few seconds after the explosion...

...onboard the CDS Southampton...

Captain Harrison was the senior commander, and assumed tactical command of both ships. He ordered a second salvo as his little fleet began to pull out of weapons range of the target...

...onboard the Sergetti frigate Celea...

The captain was about to order a pursuit when his own display showed four missiles now closing on the ship, with his targets outdistancing him at a speed he would have found impressive; had not he been contemplating his own death at the moment...

The frigate tried to heel about and run from the new set of missiles, but they had too much residual energy from the warp point jump - although the impact from the first missile hit helped to bleed some of that energy away. The crew had finally recovered and began to turn the frigate when the point defense cannon automatically fired at the first missile...

...onboard the CDS Southampton...

Lieutenant O�Rourke watched the display as the four smaller dots closed with the one larger dot. Suddenly, one of the four smaller dots disappeared. The three remaining dots continued on their way � oblivious to what had just happened or what was about to happen � and they merged with the larger dot. Then, the screen went blank...

The Colonial Dawn had just said hello to the Sergetti Empire. And another race of sentient beings would try to figure out what kinds of creatures would react in this most peculiar way...

...Nekkar Research Center...

It was just one of those days.

The calculations couldn�t be wrong. They were rather simple, and the technician had gone over this very formula many times before.

The problem was how to improve the range of the detector in the combat sensor array used by the ships defending the corporation. Basic modulation techniques were first used, but the power required to generate such signals would be prohibitively large for a space vehicle. Then, low power algorithms were discovered, and the system worked. A simple binary method of coding the transmissions provided a rudimentary sort of identification between transmitter and target. If the target replied with the right binary code pattern, the system recognized the target as friendly.

But today, the technician was working out a way to code the code itself. Or was trying to. And failing. Miserably.

It was just one of those days everyone has. Nothing worked. The technician questioned himself and his abilities. He knew better, but today it just wasn�t working for him.

In a rare show of emotion, he grabbed his formula sheet off of the desk and tore it. And again. And again.

�Feel better?" querried his partner.

The technician looked a bit sheepish as he realized he wasn�t alone. Then, his demeanor changed to fear once he realized he had taken out his frustration out on not his failed computations, but on the monthly report for the Department of Sensor Technology for the Nekkar Research Center.

In a panic he gathered the pieces off of the floor and began to look at each one as if trying to figure out which pieces went where.

His partner was still laughing when he chided him and simply printed out another copy of the report. It was good-natured, and the technician was about to reply with a jest in kind when he froze in his tracks.

He looked back at the pieces of paper on the floor and realized...

�It can�t be...� he breathed�

His partner was curious and looked at the paper scraps on the floor and back at the technician.

The technician looked at his partner and began to smile. Broadly. He knew. He knew!!

It was just one of those days...

[attack_condor]

Nekkar III
Colonial Dawn Council Meeting
Corporate Headquarters�

The meeting was underway, and the council department heads were updating the chairman of the status of each department. The research council led off, and the presentation of the development of the ECM .

�Ladies and gentlemen, the procedure is, in theory, simple��

Defense interrupted him. �All theories are simple, aren�t they?�

The presenter continued on, undeterred.

�The problem was to improve our ability to interrogate signals and discern their origin. We have devised a way to improve on the procedure.� He picked up a piece of paper and wrote his own name on it.

�And now, ladies and gentlemen��

He fed the paper into the shredder, and picked up the basket with thousands of small slivers of his document, and others that were shredded.

�Mr. Chairman, ladies and gentlemen, I submit to you I can reassemble my original document from this canister of paper shreds. I only need two things. First, I have to know what the original document was � which I do, because I created it � and second��

The financial officer chimed in.

�Second, you need time. A lot of time.�

The presenter smiled.

�Exactly, madam. Time. I would need about one month; working every second of every day to examine the shreds, sort out my shreds from the rest, and reassemble the document.�

Chairman Lomax asked the next obvious question.

�And you can now do this with interrogation message from these countermeasure pods?�

The presenter looked off to the side for just a second.

�No, Mr. Chairman. We don�t do it to the interrogation message. We can, and have, done it to the code that makes up the interrogation message. Not only does an enemy need to rearrange the letters of the message, they have to reassemble the letters from the shreds the same way I have to reassemble my paper to get to the point where they could then try to reassemble the code.�

Nobody spoke as they tried to visualize what was being said.

Defense tried first.

�You mean you can��

The presenter cut him off � not normally a good idea, but the presenter was still a bit flush with excitement.

�Yes, Admiral. And it doesn�t take a month, or a day, or an hour. We can reassemble the interrogation code in thirteen-millionths of a second.

The presenter played his final card.

�Ladies and gentlemen, we - in fact � didn�t need more time.�

He smiled.

�We needed a faster clock.�

Dawn now had ECM.

The remaining briefings went on, albeit with less flare than the research announcement. Finance announced it would be able to reduce expenditure requirements for maintenance of the empire�s facilities, ships, and units. Marketing reported the population was solidly behind the chairman and his policy of isolationism. Resources announced there were plenty of materials to continue to build and expand the known areas of Dawn space. They also announced an improvement in their storage facilities. Finally, Defense announced the creation of Operation Loophole. The plan was to take the Velocitas system and hold it as a choke point. Velocatis had warp gates to both the Pantrissa and Haphik systems. Taking the system would reduce the threat to Dawn as any ship or ships no more than 500kT. Of course, with such a small warp point, an enemy would logically need to send in a lot of smaller ships. There was some thought given to leaving Velocitas as a buffer system, but the decision was made to try and clear Velocitas and then block the warp point to whatever was on the other side.

[attack_condor]

2405.9

Update to board members:

Status report (board members will please note all Harvester resource values are per month)

Forlorn system

One oxygen gas giant available for colonization (huge and mild climate. Space yard projected)
One non-oxygen gas giant available for colonization
One non-oxygen rock world available for colonization
Two asteroid fields available

Samora system

No planets available for colonization
Four asteroid fields available
Samora I: Upgrading from intelligence center 1 to 2. Spaceport online Tripwire satellite on queue
Samora II: Supply depot operational. Construction on space yard begins

Sirius system

Three gas giants available for colonization (one oxygen atmosphere)
Three asteroid fields available
Sirius V: Construction on space yard (huge gas giant with oxygen atmosphere) begins

Zanthris system

Two gas giants available for colonization (non-oxygen)
Zanthris II: Producing Canada III class light cruiser (CDS Toronto). Two Pinta gas colony ships scheduled and spaceyard will be decommissioned (small rock with carbon dioxide atmosphere) as Sirius V space yard comes online
Harvester 400 mining 8100+ minerals
Two asteroid fields available

Pantrissa system

Warp point to Velocitas (guarded)
Warp point to Sheliak (guarded)
Pantrissa V Construction on space yard begins
Pantrissa I construction on two Artemis-class PD ships (CDS Artemis and CDS Longbow) to be complete in 0.5 years. Space yard will be decommissioned as Pantrissa V takes over
Harvester 400 mining 8300+ minerals
Two asteroid fields available
Four planets (two rock and two gsa giant, all non-oxygen) available for colonization

Qornor system

Two gas giants (non-oxygen) available for colonization
Harvester 400 mining 9000+ minerals
Two asteroid fields available

Chazzwazzer system

Six planets available for colonization (two oxygen gas giants, two non-oxygen gas giants, two rock non-oxygen)
Harvester 004 mining 11000+ radioactive resources
Two asteroid fields available
Chazzwazzer IV Construction on space yard begins

Haphik system

Warp point to Velocitas (guarded)
Two non-oxygen gas giants available
Haphik VI Construction on space yard begins
Three asteroid fields available

Praxis system

Three gas giant and one rock world available for colonization (all non-oxygen)
Praxis IX Construction on space yard begins
Three asteroid fields available

Ushphada system

One non-oxygen gas giant available for colonization
Warp point to Tikikantula (guarded)
Ushphada I producing Artemis (CDS Sniper)
Harvester 202 mining 3000+ minerals and 4000+ radioactive resources
Harvester 400 mining 8200+ minerals
One asteroid field available

Nekkar system (home system)

One rock and one gas giant (non-oxygen) planets available for colonization
Nekkar III building Pinta � ready next month
Nekkar VII Construction on space yard begins
Harvester 400 mining 8000+ minerals
Harvester 040 mining 11000+ organics

End of report

Space yard design report

Design upgrades...

Canada III upgrade to Canada IV (Lt. Cruiser)

Two level 2 particle beam weapons, one shield, one shield regenerator, level one ECM, one boarding party compliment

Artemis upgrade to Artemis II (PDS Destroyer)

Replace 10kT of armor with level one ECM

End of report

Defense council report

Operation Loophole commences. Frigates Southampton and Dover enter Velocitas from Ushphada while the frigate West End and the light cruiser Montreal enter Velocitas from Pantrissa. Southampton and West End will sweep Velocitas toward third (and unknown) warp point while Monteral and Dover guard their warp points...

Update: Southampton six sectors from the unknown warp point. West End twelve sectors away from the unknown warp point. No contacts reported...

End of report