Author Topic: The battle of Gliese 784  (Read 370 times)

0 Members and 1 Guest are viewing this topic.

Offline superstrijder15

  • Leading Rate
  • *
  • Posts: 11
  • Thanked: 3 times
    • View Profile
The battle of Gliese 784
« on: July 19, 2017, 03:21:53 PM »
This is my first AAR for this game, done in my first ever campaign.   Feedback is welcome, both on writing and on gameplay.   

Late november and early December 2104:
It was now almost 30 years ago, that the first expedition to Gliese 784 had been sent.   It should have been a completely normal system: the carrier would carry the fleet from Sol to the system, it would launch the GeoFighters, and then commence research of the gravitational survey points in the system.   After a few months, the fighters would return, and the ship would spend another year or so flying around and doing gravitational surveys. 
But it wasn't to be this way.   After the fighters were launched, the commander sat back, but after a day he suddenly got a bunch of messages: Multiple hostile contacts, hiding behind planets or on moons, suddenly attacked the fighters.   They ran, but to no avail.   Then enemy had huge battleships, simply able to outrun our best couriers, to say nothing of the slow research fighters.   Distress messages were flooding the system, but, even more worrying, they then went silent.   
The commander of the carrier turned his ship around, slowing to a crawl so as to evade detaction, attempting to reach the JP of Lacaille 8760.   The ship took a month, but reached the new colony of Lacaille.   From there it returned to Earth, with the news that an incredibly hostile force was encountered.   The full fleet was shuttled over, using the ability of the carrier to take two other ships with her on each jump to be shuttled in pairs.   The fleet waited for the imminent invasion at the Lacaille colony*, but it never came.   In the meantime, communication experts probed the system and tried to start communications.   From their research, they found that the enemy was old, and probably robotic.   No signs of civilisation existed on the planet.   In the meantime, the military geniusus of Earth rushed to create something that could be effective against these battleships, while building missile boats able to outpace, outrange and outlast the older laser warships around Lacaille, yet would be no match against the enemy warfleet.   This class was called the
MB Flower**.   
As there was no space for big sensors or jump drives on these ships, the BattleRider** class command carrier was designed.   It had large sensors, a squad jump drive and hangars for scouts or FACs.   The final ship designed, still having techs in research while the other were already being produced, was the Audacious class FAC**.   It was the only class so far to be faster than the opponent, using the best engines available and a lot of box launchers.   
Twelve Flower, three BattleRider and three Audacious were built, and then the fleet started moving.   

After almost a month of travel, the fleet reached Lacaille 7860.   It refueled, and moved over to the JP.   They were accompanied now by the original carrier, which had been taken off of system surveys to bring in more scouts**.   After the fleet jumped in, it wen't into formation quickly.   One of the battleriders served as the formation anchor.   The scouts were posted on the maximum 100 million km from the anchor***, formed an arc of 80 degrees with about 8 pairs, and turned on their actives.   The battlegroup formed up with 3 groups: The FAC formed in the center, 100 million km from the anchor, and the missile boats formed up 20 degrees offset, each group of 6 with a Battlerider for sensors.   These kept their sensors off however, allowing the enemy to charge through the middle, right through the Alpha strike of the FAC and then a barrage from the missile groups, at the sensor boat.   The first enemy sighted were 4 enemy FAC, charging at only 6000km/s at the center of the formation.   The first barrage of missiles from the FAC took out 1 ship, while the others seperated and tried to attack scouts.   While the FAC went to the missile group to reload, the center scouts pulled back to let the enemy come closer.   However, due to the enemy small size, the fleet couldn't attack from a longer range, so only the FAC were an effective weapon.   Three more barrages were needed to take the enemy down, but no casualties were sustained.   
The fleet resumed formation and moved on, certain of an easy victory now.    But then, the signal from the BattleRider 003 went down, being replaced by a distress signal as it got hit by a salvo of missiles.   Choas and confusion, and then the actives of one of the Flower came online, and the task group scattered.   Tens of salvoes flew less than a minute away from the group, which tried to survive by splitting up.   As the Anti-clockwise TG got hit, the captain of the clockwise one hurried to get the sensors working, and saw a daunting picture: At least 15 salvoes were flying at his TG.   In the distance, but well within sensor range, there was a fleet of multiple battleships, charging in at 10Mm/s.   He quickly coordinated a AMM defense, telling units to just fire at will at the salvoes.   Slowly the salvoes of ASM and AMM grew closer. 
On the anti-clockwise front, the situation was a lot more drastic.   The fleet scattered, and although many actives went up, the FC failed to react quickly enough (read: i forgot to turn on auto fire and when i did the ships didn't fire for unknown reasons) to take out the missiles.   The last to go was the Flower 016, which managed to take out 2 salvoes and wheather a third before succumbing.   In only three minutes, the fleet was halved. 
The FAC had now also started moving, going for the enemy battleship.   The ranges of combat were long however, and the next happening was well over an hour later, when the ASM and AMM clashed.   Each salvo took out about half on enemy salvo, so lot's of them were needed.   After another hour, most salvoes had been dealt with, and it seemed like the TG would surive unscathed. 
In two more hours, the FAC finally reached firing distance, and opened fire on the enemy.   The first barage did nothing, but they returned.   In the meantime, all ASM were destroyed, and the enemy had stopped firing.   Which was good, as there were only about 100 AMMs left in all the stocks.   The fleet was woefully unprepared.  .  . 

However, nothing dangerous happened.   It would take multiple days for the FAC to whittle down the armour on the enemy ships, which barely even tried to escape.   Obviously better missiles would be needed in the future.   When the enemies were finally taken down, the fleet moved for the Lacaille 8760 JP, taking on survivors on the way and regrouping at the point.   A salvager was called in, and the fleet retreated to Earth. 

*I play without maintenance, so the fact there are no facilities is no problem
** Schematics:

Flower:
Off-Topic: show
Flower class Missile Boat    8 950 tons     212 Crew     1928.  8 BP      TCS 179  TH 200  EM 0
2234 km/s     Armour 4-38     Shields 0-0     Sensors 1/1/0/0     Damage Control Rating 11     PPV 21
Maint Life 0.  19 Years     MSP 135    AFR 640%    IFR 8.  9%    1YR 704    5YR 10564    Max Repair 300 MSP
Intended Deployment Time: 24 months    Spare Berths 1   
Magazine 543   

100 EP Internal Fusion Drive (4)    Power 100    Fuel Use 38%    Signature 50    Exp 10%
Fuel Capacity 750 000 Litres    Range 39.  7 billion km   (205 days at full power)

S3 ML (50% SRed) (6)    Missile Size 3    Rate of Fire 225
Size 1 Missile Launcher (12)    Missile Size 1    Rate of Fire 15
Missile Fire Control FC14-R1 (3)     Range 14.  4m km    Resolution 1
Missile Fire Control FC230-R100 (70%) (1)     Range 230.  4m km    Resolution 100
S3 ASM (90)  Speed: 30 800 km/s   End: 124.  8m    Range: 230.  7m km   WH: 4    Size: 3    TH: 102/61/30
S1 AMM (273)  Speed: 35 000 km/s   End: 7m    Range: 14.  8m km   WH: 1    Size: 1    TH: 140/84/42

Active Search Sensor MR14-R1 (1)     GPS 240     Range 14.  4m km    MCR 1.  6m km    Resolution 1
Active Search Sensor MR144-R100 (70%) (1)     GPS 24000     Range 144.  0m km    Resolution 100

Missile to hit chances are vs targets moving at 3000 km/s, 5000 km/s and 10,000 km/s

This design is classed as a Military Vessel for maintenance purposes

BattleRider:
Off-Topic: show
BattleRider class Command Carrier    20 000 tons     457 Crew     3900.  2 BP      TCS 400  TH 500  EM 0
2500 km/s    JR 5-250     Armour 2-65     Shields 0-0     Sensors 110/110/0/0     Damage Control Rating 0     PPV 0
Maint Life 0 Years     MSP 0    AFR 4000%    IFR 55.  6%    1YR 10623    5YR 159340    Max Repair 640 MSP
Intended Deployment Time: 60 months    Flight Crew Berths 0   
Flag Bridge    Hangar Deck Capacity 3000 tons     

J20000(5-250) Military Jump Drive     Max Ship Size 20000 tons    Distance 250k km     Squadron Size 5
100 EP Internal Fusion Drive (10)    Power 100    Fuel Use 38%    Signature 50    Exp 10%
Fuel Capacity 3 100 000 Litres    Range 73.  4 billion km   (339 days at full power)

Active Search Sensor MR70-R1 (1)     GPS 640     Range 70.  4m km    MCR 7.  7m km    Resolution 1
Active Search Sensor MR704-R100 (1)     GPS 64000     Range 704.  0m km    Resolution 100
Thermal Sensor TH10-110 (1)     Sensitivity 110     Detect Sig Strength 1000:  110m km
EM Detection Sensor EM10-110 (1)     Sensitivity 110     Detect Sig Strength 1000:  110m km

Strike Group
2x WatcherR100 Recon Fighter   Speed: 6000 km/s    Size: 10
2x WatcherR20 Recon Fighter   Speed: 5000 km/s    Size: 10

This design is classed as a Military Vessel for maintenance purposes


Audacious:
Off-Topic: show
Audacious class Fast Attack Craft    1 000 tons     25 Crew     357.  5 BP      TCS 20  TH 125  EM 0
12500 km/s     Armour 1-8     Shields 0-0     Sensors 1/1/0/0     Damage Control Rating 1     PPV 4.  5
Maint Life 9.  56 Years     MSP 223    AFR 8%    IFR 0.  1%    1YR 4    5YR 66    Max Repair 187.  5 MSP
Intended Deployment Time: 3 months    Spare Berths 2   
Magazine 30   

FACE 250 EP MagFusDrive (1)    Power 250    Fuel Use 161.  22%    Signature 125    Exp 20%
Fuel Capacity 100 000 Litres    Range 11.  2 billion km   (10 days at full power)

S3 Box Launcher (10)    Missile Size 3    Hangar Reload 22.  5 minutes    MF Reload 3.  7 hours
Missile Fire Control FC245-R50 (1)     Range 245.  0m km    Resolution 50
S3 ASM (10)  Speed: 30 800 km/s   End: 124.  8m    Range: 230.  7m km   WH: 4    Size: 3    TH: 102/61/30

Missile to hit chances are vs targets moving at 3000 km/s, 5000 km/s and 10,000 km/s

This design is classed as a Military Vessel for maintenance purposes

scout:
Off-Topic: show
WatcherR100 class Recon Fighter    500 tons     12 Crew     141.  6 BP      TCS 10  TH 60  EM 0
6000 km/s     Armour 1-5     Shields 0-0     Sensors 1/1/0/0     Damage Control Rating 0     PPV 0
Maint Life 0 Years     MSP 0    AFR 100%    IFR 1.  4%    1YR 29    5YR 430    Max Repair 80 MSP
Intended Deployment Time: 24 months    Spare Berths 0   

FE 30 EP Internal Fusion Drive (2)    Power 30    Fuel Use 109.  13%    Signature 30    Exp 15%
Fuel Capacity 80 000 Litres    Range 26.  4 billion km   (50 days at full power)

Active Search Sensor MR64-R100 (1)     GPS 8000     Range 64.  0m km    Resolution 100

This design is classed as a Fighter for production, combat and maintenance purposes


Off-Topic: show
WatcherR20 class Recon Fighter    500 tons     12 Crew     176.  1 BP      TCS 10  TH 25  EM 0
5000 km/s     Armour 1-5     Shields 0-0     Sensors 1/1/0/0     Damage Control Rating 0     PPV 0
Maint Life 0 Years     MSP 0    AFR 100%    IFR 1.  4%    1YR 40    5YR 600    Max Repair 105 MSP
Intended Deployment Time: 3 months    Spare Berths 1   

FE 50 EP MagFusDrive(Sig50%) (1)    Power 50    Fuel Use 29.  4%    Signature 25    Exp 10%
Fuel Capacity 95 000 Litres    Range 116.  3 billion km   (269 days at full power)

Active Search Sensor MR51-R20 (1)     GPS 2100     Range 51.  7m km    Resolution 20

This design is classed as a Fighter for production, combat and maintenance purposes


***It would be massively appreciated if this limit could be increased, or if someone could give a click by click guide to letting ship A escort ship B while ship B escorts ship C
« Last Edit: July 19, 2017, 03:24:01 PM by superstrijder15 »
 

Offline superstrijder15

  • Leading Rate
  • *
  • Posts: 11
  • Thanked: 3 times
    • View Profile
Re: The battle of Gliese 784
« Reply #1 on: August 08, 2017, 04:20:27 PM »
After the battle of Gliese 784, a jump gate to the system has been constructed, a salvager has salvaged the enemy wrecks, which sadly didn't contain any unknown technology.   The fleet took it's time to return, mainly because the fleet had lost a third of it's hangar and jumping capabilities, while it had taken a lot of survivors from the destroyed ships.   For unknown reasons, all survivors absolutely had to be stationed on the Battlerider 002, overloading life support all the time*.   Even when the ship reached port and, together with most of the battleships, went into overhaul and had all men go on shore leave, something kept on blowing up in the system.   Eventually this was traced to a Aurora fail software failure leading to superheating of critical components. 

While all was sorted out, research was going on, and an expedition was sent to research the system.   By 2107 it was getting obvious that the current expedition forces were insufficient for continuation of exploration as it was taking a year to survey just the one system, and a new ship class was needed**.   The concept for the exploration would be close to that of the old fleet: During exploration, a Poeper class carrier will carry 16 Optimist class survey fighters to an unexplored system, 8 of the Geo variety and 8 of the Grav one, they will be deployed with survey orders, and after a while they return.   
Unlike with the earlier designs, the carrier stays on the jump point, ready to flee.   Also unlike the earlier plans, this fleet won't need to return after each system, instead having sufficient fuel to continue to another system once the fleet is done in one system.   Instead of returning, this fleet has a bit of extra hangar space for miniscule, on a spacecraft scale, courier drones able to connect with the system of jump gates to notify the command of findings. 

In the near future, it is expected that a new fleet doctrine will be developed, with gauss fighters instead of missile FAC and quite possibly dedicated beam defense platforms and new, better missiles. 

Some more details on the ships:
The Poeper*** class Exploration Mothership, coming in at 20 kilotons, can move almost 2 thousand km/s.   The better part of it's interior consists of hangars, followed by engines and living space.   It has enough space to house the crews of all the fighters comfortably.   It's terribly efficient engines give the ship a technical range of 2 billion megameters, although it would take 41 years to expend all fuel, the more intensive fighter engines might use up a bit of that fuel though. 
The Poeper carries 16 survey fighters of the Optimist*** class.   These fighters can go over twice the speed of their carrier, but with a shorter range and deployment time.   They swarm out in a wave to take over a whole system for a few weeks, and then dissapear from whence they came. 



*Other ships had the capacity to handle the amount of survivors if cooperating, but IDK how to move the survivors, so I just SM repaired. 
**OOC: I had been on a sailing camp, and I really wanted to design something today, and as it will take a while for the techs for Gauss to get better and I want to give my military ships the engine tech I will have in a few years, I got to the explo service instead.   Naming in the near future is likely to be inspired by Dutch smaller sailing classes. 
***Poeper: an old class of cargo barge, I lived on one of these and a 'polyvalk' for a week a week ago. 
Optimist: the smallest class of sailing boat, used by children of up to 12-14.   It's a crude and simple construction, cheap and easy to mass-produce or learn to control. 
****Schematics:
Poeper:
Code: [Select]
Poeper class Exploration Mothership    20 000 tons     279 Crew     1943.125 BP      TCS 400  TH 625  EM 0
1562 km/s    JR 5-250     Armour 1-65     Shields 0-0     Sensors 1/1/0/0     Damage Control Rating 1     PPV 0
Maint Life 0.02 Years     MSP 61    AFR 3200%    IFR 44.4%    1YR 2849    5YR 42731    Max Repair 471 MSP
Intended Deployment Time: 120 months    Flight Crew Berths 197   
Hangar Deck Capacity 7375 tons     

J20000(5-250) Military Jump Drive     Max Ship Size 20000 tons    Distance 250k km     Squadron Size 5
312.5 EP Commercial Magnetic Fusion Drive (2)    Power 312.5    Fuel Use 0.47%    Signature 312.5    Exp 2%
Fuel Capacity 1 100 000 Litres    Range 2105.7 billion km   (15602 days at full power)

Strike Group
8x Optimist R Survey Fighter   Speed: 4347 km/s    Size: 9.2
8x Optimist E Survey Fighter   Speed: 4347 km/s    Size: 9.2

This design is classed as a Military Vessel for maintenance purposes
Optimists:
Code: [Select]
Optimist E class Survey Fighter    460 tons     12 Crew     192 BP      TCS 9.2  TH 40  EM 0
4347 km/s     Armour 1-5     Shields 0-0     Sensors 1/1/0/2     Damage Control Rating 0     PPV 0
Maint Life 0 Years     MSP 0    AFR 92%    IFR 1.3%    1YR 59    5YR 886    Max Repair 150 MSP
Intended Deployment Time: 24 months    Spare Berths 0   

FE 20 EP Internal Fusion Drive (2)    Power 20    Fuel Use 39.6%    Signature 20    Exp 10%
Fuel Capacity 50 000 Litres    Range 49.4 billion km   (131 days at full power)

Improved Geological Sensors (1)   2 Survey Points Per Hour

This design is classed as a Fighter for production, combat and maintenance purposes
Code: [Select]
Optimist R class Survey Fighter    460 tons     12 Crew     192 BP      TCS 9.2  TH 40  EM 0
4347 km/s     Armour 1-5     Shields 0-0     Sensors 1/1/2/0     Damage Control Rating 0     PPV 0
Maint Life 0 Years     MSP 0    AFR 92%    IFR 1.3%    1YR 59    5YR 886    Max Repair 150 MSP
Intended Deployment Time: 24 months    Spare Berths 0   

FE 20 EP Internal Fusion Drive (2)    Power 20    Fuel Use 39.6%    Signature 20    Exp 10%
Fuel Capacity 50 000 Litres    Range 49.4 billion km   (131 days at full power)

Improved Gravitational Sensors (1)   2 Survey Points Per Hour

This design is classed as a Fighter for production, combat and maintenance purposes
« Last Edit: August 08, 2017, 04:23:11 PM by superstrijder15 »
 

Offline superstrijder15

  • Leading Rate
  • *
  • Posts: 11
  • Thanked: 3 times
    • View Profile
Re: The battle of Gliese 784
« Reply #2 on: August 18, 2017, 12:53:55 PM »
« Last Edit: August 18, 2017, 01:12:15 PM by superstrijder15 »
 

 

Sitemap 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52