Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21

Map of known Calana space at the commencement of the invasion. October 16th, 2055. Flags indicate known populations or fleet holdouts, a JP link between Mu Pyxidis and 91 Pegasi is strongly suspected.
   
By October 2055, just as the captured ships began exceeding their rated deployment, everything was in place. An invasion fleet has assembled at the 91 Pegasi jump point in Kuiper 41, numbering more than half of the Empire’s current-generation navy, with many ships recently having proven themselves in two campaigns against precursors, as well as the subjugation of a minor trans-newtonian race known as the Followers of Kent. All Tokushima-class trophy destroyers were also committed to the latter campaign where their short-range missile launchers were utilized to break through the Kent homeworld’s orbital defenses to a rather poor effect. Those now-expended destroyers were now awaiting dismantlement in occupied shipyards, and the High Command had low expectations of their longer-range siblings.

Two ground assault divisions, each 240 kilotons strong, were fighting to secure the last xeno colony in the system. No attempt to gather a sufficient army for the homeworld invasion was made yet, as the size and the extent of Calana ground forces across 91 Pegasi were not known. Thus, achieving space supremacy, eliminating all known enemy ships and surface-to-orbit elements, as well as obtaining intelligence of ground force strength throughout the system in preparation for the upcoming landings, were defined as main objectives of the invasion.

Russian Stellar Empire Order of Battle:
Assault Carrier Fleet:
3x CVH Knyaz Pozharsky-class Assault Carrier: Ekaterina, Petr Veliki, Tsessarevitch
Mightiest vessels of the Empire, each envisioned as a flagship capable of spearheading an entire operation. Three were built in total, and this was the first time all three were deployed in one area.

Strike Group:
25x GS Vepr-class Gunship - A fast strike craft, capable of outranging all known Calana vessels in a beam fight, but bereft of any staying power.
5x BPOD Otvaga-class Breaching Pod - A capable boarding vessel each carrying a company of well-armed and armored marines.
110x FTR MiG-65-class Fighter - A nimble fighter possessing great strength in numbers.
10x FTR MiG-65S-class Fighter - A fast scout utilized alongside fighter strike groups or separately.
Off-Topic: Fleet Specifications • show
Knyaz Pozharsky class Assault Carrier      50,000 tons       994 Crew       9,723 BP       TCS 1,000    TH 9,000    EM 6,780
9000 km/s    JR 5-100      Armour 5-120       Shields 226-565       HTK 208      Sensors 110/110/0/0      DCR 56-11      PPV 0
Maint Life 1.33 Years     MSP 11,444    AFR 1250%    IFR 17.4%    1YR 6,908    5YR 103,627    Max Repair 1,500 MSP
Hangar Deck Capacity 15,000 tons     Troop Capacity 1,000 tons     Boarding Capable    Cryogenic Berths 1,000   
Kapitan pervogo ranga    Control Rating 4   BRG   AUX   ENG   FLG   
Intended Deployment Time: 12 months    Flight Crew Berths 300    Morale Check Required   

Makarov Aeromarine J50000(5-100) Military Jump Drive     Max Ship Size 50000 tons    Distance 100k km     Squadron Size 5

Korolev MCRD-3000.00 (3)    Power 9000    Fuel Use 43.57%    Signature 3000    Explosion 15%
Fuel Capacity 3,885,900 Litres    Range 32.1 billion km (41 days at full power)
Danilov-Morozov Theta S113 / R565 Shields (2)     Recharge Time 565 seconds (0.4 per second)

Shevchenko-Maslov Micrometeorite Detector AS11-R1 (1)     GPS 28     Range 11.2m km    MCR 1m km    Resolution 1
Zhukov Warning & Control Area Search Sensor AS200-R100 (1)     GPS 42000     Range 200.8m km    Resolution 100
Nikolaev Sensor Systems Thermal Sensor TH10-110 (1)     Sensitivity 110     Detect Sig Strength 1000:  82.9m km
Nikolaev Sensor Systems EM Sensor EM10-110 (1)     Sensitivity 110     Detect Sig Strength 1000:  82.9m km

Electronic Warfare Jammers:   Fire Control 3    Missile 3   

Vepr class Gunship      1,000 tons       10 Crew       423.5 BP       TCS 20    TH 360    EM 0
18000 km/s      Armour 3-8       Shields 0-0       HTK 7      Sensors 0/0/0/0      DCR 0-0      PPV 8
Maint Life 0.58 Years     MSP 100    AFR 200%    IFR 2.8%    1YR 172    5YR 2,587    Max Repair 180 MSP
Kapitan tret'yego ranga    Control Rating 1   
Intended Deployment Time: 0.9 days    Morale Check Required   

Sukhoi MCRD-360.00F (1)    Power 360    Fuel Use 1006.23%    Signature 360    Explosion 30%
Fuel Capacity 31,600 Litres    Range 0.57 billion km (8 hours at full power)

Romanov-Mikhailov 25cm Railgun V50/C5 (1x4)    Range 250,000km     TS: 18,000 km/s     Power 15-5     RM 50,000 km    ROF 15       
Baranov Sensor Systems Beam Fire Control R320-TS10000 (SW) (1)     Max Range: 320,000 km   TS: 10,000 km/s    ECCM-2     97 94 91 88 84 81 78 75 72 69
Antonov Turbines Tokamak Fusion Reactor R5-PB60 (1)     Total Power Output 5.1    Exp 30%

Baranov Sensor Systems Active Search Sensor AS7-R10 (1)     GPS 28     Range 7.6m km    Resolution 10

Otvaga class Breaching Pod      1,000 tons       6 Crew       228.3 BP       TCS 20    TH 360    EM 0
18000 km/s      Armour 3-8       Shields 0-0       HTK 4      Sensors 0/0/0/0      DCR 0-0      PPV 0
Maint Life 0 Years     MSP 0    AFR 199%    IFR 2.8%    1YR 107    5YR 1,610    Max Repair 180 MSP
Troop Capacity 500 tons     Boarding Capable   
Kapitan tret'yego ranga    Control Rating 1   
Intended Deployment Time: 1.5 days    Morale Check Required   

Sukhoi MCRD-360.00F (1)    Power 360    Fuel Use 1006.23%    Signature 360    Explosion 30%
Fuel Capacity 28,600 Litres    Range 0.51 billion km (7 hours at full power)

Ground Forces
1x Abordazhnaya Rota – 2054

MiG-65 class Fighter      125 tons       1 Crew       40.8 BP       TCS 2    TH 48    EM 0
19325 km/s      Armour 1-2       Shields 0-0       HTK 1      Sensors 0/0/0/0      DCR 0-0      PPV 0.98
Maint Life 3.59 Years     MSP 10    AFR 25%    IFR 0.3%    1YR 1    5YR 18    Max Repair 24 MSP
Kapitan tret'yego ranga    Control Rating 1   
Intended Deployment Time: 3.3 days    Morale Check Required   

Mikoyan-Gurevitch MCRD-48.00 (1)    Power 48    Fuel Use 1653.41%    Signature 48    Explosion 30%
Fuel Capacity 5,700 Litres    Range 0.5 billion km (7 hours at full power)

Stepanov Precision Arms 10cm Railgun V10/C0.75/S1 (1)    Range 10,000km     TS: 19,325 km/s     Power 0.75-0.75     RM 10,000 km    ROF 5       
Baranov Sensor Systems Beam Fire Control R16-TS19000 (SW) (1)     Max Range: 16,000 km   TS: 19,000 km/s    ECCM-4     38 0 0 0 0 0 0 0 0 0
Antonov Turbines Tokamak Fusion Reactor R1-PB60 (1)     Total Power Output 0.8    Exp 30%

MiG-65S class Fighter      125 tons       1 Crew       54.5 BP       TCS 2    TH 48    EM 0
19333 km/s      Armour 1-2       Shields 0-0       HTK 1      Sensors 7/0/0/0      DCR 0-0      PPV 0
Maint Life 4.73 Years     MSP 25    AFR 25%    IFR 0.3%    1YR 2    5YR 28    Max Repair 24 MSP
Kapitan tret'yego ranga    Control Rating 1   
Intended Deployment Time: 11.2 days    Morale Check Required   

Mikoyan-Gurevitch MCRD-48.00 (1)    Power 48    Fuel Use 1653.41%    Signature 48    Explosion 30%
Fuel Capacity 20,400 Litres    Range 1.79 billion km (25 hours at full power)

Baranov Sensor Systems Active Search Sensor AS7-R1 (1)     GPS 14     Range 7.9m km    MCR 710.9k km    Resolution 1
Baranov Sensor Systems Thermal Sensor TH0.5-7.0 (1)     Sensitivity 7     Detect Sig Strength 1000:  20.9m km



Carrier Fleet:
1x CV Knyaz Potemkin-class Carrier
The previous-generation flagship of the Empire Fleet.
2x CV Kuzma Minin-class Carrier: Donets, Rostislav
Current-generation fleet carrier. Slow and unprotected, but boasts great capacity, often sees use as a mobile repair dock.

Strike Group:
24x BPOD Otvaga-class Breaching Pod
25x GS Vepr-class Gunship
50x FTR MiG-55-class Fighter – A previous-generation railgun fighter.
9x FTR MiG-55S - A previous-generation scout fighter.
Off-Topic: Fleet Specifications • show
Knyaz Potemkin class Carrier      50,000 tons       1,015 Crew       8,539.8 BP       TCS 1,000    TH 6,000    EM 0
6000 km/s    JR 5-100      Armour 6-120       Shields 0-0       HTK 224      Sensors 110/110/0/0      DCR 45-9      PPV 32
Maint Life 1.41 Years     MSP 9,901    AFR 1333%    IFR 18.5%    1YR 5,467    5YR 82,012    Max Repair 1,000 MSP
Hangar Deck Capacity 15,000 tons     Magazine 674 / 0    Cryogenic Berths 200   
Kapitan pervogo ranga    Control Rating 4   BRG   AUX   FLG   PFC   
Intended Deployment Time: 12 months    Flight Crew Berths 300    Morale Check Required   

Makarov Aeromarine J50000(5-100) Military Jump Drive     Max Ship Size 50000 tons    Distance 100k km     Squadron Size 5

Korolev MPRD-2000.00 (3)    Power 6000    Fuel Use 27.62%    Signature 2000    Explosion 12%
Fuel Capacity 2,282,100 Litres    Range 29.7 billion km (57 days at full power)

Popov & Vlasov Size 2.0 Missile Launcher (16)     Missile Size: 2    Rate of Fire 10
Zaytsev Electronics  Missile Fire Control FC20-R1 (2)     Range 20.7m km    Resolution 1   ECCM-1
Garda Mod.3 AMM (337)    Speed: 76,200 km/s    End: 0.7m     Range: 3.4m km    WH: 1    Size: 2    TH: 254/152/76

Zaytsev Electronics Missile Sensor AS16-R1 (1)     GPS 105     Range 16.4m km    MCR 1.5m km    Resolution 1
Zhukov Warning & Control Area Search Sensor AS154-R100 (1)     GPS 31500     Range 154.1m km    Resolution 100
Nikolaev Sensor Systems Thermal Sensor TH10-110 (1)     Sensitivity 110     Detect Sig Strength 1000:  82.9m km
Nikolaev Sensor Systems EM Sensor EM10-110 (1)     Sensitivity 110     Detect Sig Strength 1000:  82.9m km

Electronic Warfare Jammers:   Missile 2   

Kuzma Minin class Carrier      50,000 tons       782 Crew       7,527.5 BP       TCS 1,000    TH 6,000    EM 0
6000 km/s      Armour 3-120       Shields 0-0       HTK 233      Sensors 110/70/0/0      DCR 55-11      PPV 0
Maint Life 1.41 Years     MSP 9,011    AFR 1333%    IFR 18.5%    1YR 4,959    5YR 74,384    Max Repair 1,500 MSP
Hangar Deck Capacity 25,000 tons     Magazine 722 / 0    Cryogenic Berths 1,000   
Kapitan vtorogo ranga    Control Rating 3   BRG   AUX   PFC   
Intended Deployment Time: 12 months    Flight Crew Berths 500    Morale Check Required   

Korolev MCRD-3000.00 (2)    Power 6000    Fuel Use 43.57%    Signature 3000    Explosion 15%
Fuel Capacity 3,813,700 Litres    Range 31.5 billion km (60 days at full power)

Shevchenko-Maslov Micrometeorite Detector AS11-R1 (1)     GPS 28     Range 11.2m km    MCR 1m km    Resolution 1
Zhukov Warning & Control Active Search Sensor AS81-R100 (1)     GPS 7000     Range 82m km    Resolution 100
Kalinin Electronic Systems EM Sensor EM5-70 (1)     Sensitivity 70     Detect Sig Strength 1000:  66.1m km
Nikolaev Sensor Systems Thermal Sensor TH10-110 (1)     Sensitivity 110     Detect Sig Strength 1000:  82.9m km


MiG-55 class Fighter      250 tons       2 Crew       67.7 BP       TCS 5    TH 80    EM 0
16001 km/s      Armour 1-3       Shields 0-0       HTK 1      Sensors 0/0/0/0      DCR 0-0      PPV 1.63
Maint Life 1.54 Years     MSP 10    AFR 50%    IFR 0.7%    1YR 5    5YR 72    Max Repair 40 MSP
Kapitan tret'yego ranga    Control Rating 1   
Intended Deployment Time: 1.2 days    Morale Check Required   

Mikoyan-Gurevitch MPRD-80.00 (1)    Power 80    Fuel Use 1104.85%    Signature 80    Explosion 25%
Fuel Capacity 8,500 Litres    Range 0.55 billion km (9 hours at full power)

Stepanov Precision Arms 12cm Railgun V20/C0.75/S1 (1)    Range 38,400km     TS: 16,001 km/s     Power 1.5-0.75     RM 20,000 km    ROF 10       
Baranov Sensor Systems Beam Fire Control R38-TS16000 (SW) (1)     Max Range: 38,400 km   TS: 16,000 km/s    ECCM-2     74 48 22 0 0 0 0 0 0 0
Antonov Turbines Stellarator Fusion Reactor R1-PB30 (1)     Total Power Output 0.8    Exp 15%

MiG-55S class Fighter      250 tons       2 Crew       73.6 BP       TCS 5    TH 80    EM 0
16001 km/s      Armour 1-3       Shields 0-0       HTK 1      Sensors 3/0/0/0      DCR 0-0      PPV 0.98
Maint Life 1.60 Years     MSP 10    AFR 50%    IFR 0.7%    1YR 5    5YR 68    Max Repair 40 MSP
Kapitan tret'yego ranga    Control Rating 1   
Intended Deployment Time: 1.2 days    Morale Check Required   

Mikoyan-Gurevitch MPRD-80.00 (1)    Power 80    Fuel Use 1104.85%    Signature 80    Explosion 25%
Fuel Capacity 21,000 Litres    Range 1.37 billion km (23 hours at full power)

Stepanov Precision Arms 10cm Railgun V20/C0.75/S1 (1)    Range 20,000km     TS: 16,001 km/s     Power 0.75-0.75     RM 20,000 km    ROF 5       
Baranov Sensor Systems Beam Fire Control R38-TS16000 (SW) (1)     Max Range: 38,400 km   TS: 16,000 km/s    ECCM-2     74 48 22 0 0 0 0 0 0 0
Antonov Turbines Stellarator Fusion Reactor R1-PB30 (1)     Total Power Output 0.8    Exp 15%

Baranov Sensor Systems Active Search Sensor AS5-R10 (1)     GPS 21     Range 5.8m km    Resolution 10
Baranov Sensor Systems Thermal Sensor TH0.3-3.3 (1)     Sensitivity 3.3     Detect Sig Strength 1000:  14.4m km



2nd Combat Fleet:
2x Destroyer Task Group:
8x DD Admiral Lazarev-class Destroyer
The backbone of the Empire’s Navy, a general-purpose combat vessel.
2x DE Admiral Lazarev-E-class Destroyer Escort
A modification of the Admiral Lazarev hull, specialized for anti-missile screening.
2x CDD Admiral Lazarev-C-class Command Destroyer
A modification of the Admiral Lazarev hull, specialized as a task group leader.

Strike Group:
4x MiG-65S-class Fighter

All destroyers are organized into two Destroyer Task Groups, consisting of two specialized classes and four base classes.

Beam Frigate Task Group:
4x FF Orlan-class Frigate
A modern railgun frigate.
Off-Topic: Fleet Specifications • show
Admiral Lazarev class Destroyer      20,000 tons       528 Crew       4,453.8 BP       TCS 400    TH 4,000    EM 3,390
10000 km/s      Armour 5-65       Shields 113-565       HTK 124      Sensors 14/0/0/0      DCR 24-12      PPV 70.4
Maint Life 1.08 Years     MSP 2,356    AFR 800%    IFR 11.1%    1YR 2,036    5YR 30,544    Max Repair 500 MSP
Magazine 786 / 0   
Kapitan pervogo ranga    Control Rating 4   BRG   AUX   ENG   CIC   
Intended Deployment Time: 9 months    Morale Check Required   

Kuznetsov MCRD-1000.00 (4)    Power 4000    Fuel Use 43.67%    Signature 1000    Explosion 12%
Fuel Capacity 1,215,100 Litres    Range 25 billion km (28 days at full power)
Danilov-Morozov Theta S113 / R565 Shields (1)     Recharge Time 565 seconds (0.2 per second)

Romanov-Mikhailov 25cm Railgun V50/C5 (4x4)    Range 250,000km     TS: 10,000 km/s     Power 15-5     RM 50,000 km    ROF 15       
Markov & Golubev Beam Fire Control R320-TS10000 (1)     Max Range: 320,000 km   TS: 10,000 km/s    ECCM-4     97 94 91 88 84 81 78 75 72 69
Belov & Kiselev Tokamak Fusion Reactor R20 (1)     Total Power Output 20.1    Exp 5%

Kovalev-Makarov Size 8.00 Missile Launcher (60.0% Reduction) (8‎‎)     Missile Size: 8    Rate of Fire 85
Zhukov Warning & Control Missile Fire Control FC74-R20 (1)     Range 74.3m km    Resolution 20   ECCM-4
Nablyudatel Surveillance Missile (2)    Speed: 22,950 km/s    End: 184.8m     Range: 254.4m km    WH: 0    Size: 8    TH: 76/45/22
Kinzhal Mod.2 AShM (96)    Speed: 39,000 km/s    End: 30.3m     Range: 71m km    WH: 12    Size: 8    TH: 182/109/54

Shevchenko-Maslov Micrometeorite Detector AS11-R1 (1)     GPS 28     Range 11.2m km    MCR 1m km    Resolution 1
Zaytsev Electronics Active Search Sensor AS51-R100 (1)     GPS 2800     Range 51.8m km    Resolution 100
Kalinin Electronic Systems Thermal Sensor TH1.0-14.0 (1)     Sensitivity 14     Detect Sig Strength 1000:  29.6m km

Electronic Warfare Jammers:   Missile 3   

Admiral Lazarev-E class Destroyer Escort      20,000 tons       547 Crew       4,567.6 BP       TCS 400    TH 4,000    EM 3,390
10000 km/s      Armour 5-65       Shields 113-565       HTK 127      Sensors 14/14/0/0      DCR 24-12      PPV 64
Maint Life 1.08 Years     MSP 2,370    AFR 800%    IFR 11.1%    1YR 2,038    5YR 30,571    Max Repair 500 MSP
Magazine 754 / 0   
Kapitan pervogo ranga    Control Rating 4   BRG   AUX   ENG   CIC   
Intended Deployment Time: 9 months    Morale Check Required   

Kuznetsov MCRD-1000.00 (4)    Power 4000    Fuel Use 43.67%    Signature 1000    Explosion 12%
Fuel Capacity 1,220,100 Litres    Range 25.1 billion km (29 days at full power)
Danilov-Morozov Theta S113 / R565 Shields (1)     Recharge Time 565 seconds (0.2 per second)

Romanov-Mikhailov 25cm Railgun V50/C5 (4x4)    Range 250,000km     TS: 10,000 km/s     Power 15-5     RM 50,000 km    ROF 15       
Markov & Golubev Beam Fire Control R320-TS10000 (1)     Max Range: 320,000 km   TS: 10,000 km/s    ECCM-4     97 94 91 88 84 81 78 75 72 69
Belov & Kiselev Tokamak Fusion Reactor R20 (1)     Total Power Output 20.1    Exp 5%

Popov & Vlasov Size 2.0 Missile Launcher (16)     Missile Size: 2    Rate of Fire 10
Zaytsev Electronics Missile Fire Control FC27-R1 (2)     Range 27.4m km    Resolution 1   ECCM-2
Garda Mod.3 AMM (377)    Speed: 76,200 km/s    End: 0.7m     Range: 3.4m km    WH: 1    Size: 2    TH: 254/152/76

Zaytsev Electronics Missile Sensor AS22-R1 (1)     GPS 112     Range 22.3m km    MCR 2m km    Resolution 1
Zaytsev Electronics Active Search Sensor AS51-R100 (1)     GPS 2800     Range 51.8m km    Resolution 100
Kalinin Electronic Systems Thermal Sensor TH1.0-14.0 (1)     Sensitivity 14     Detect Sig Strength 1000:  29.6m km
Kalinin Electronic Systems EM Sensor EM1.0-14.0 (1)     Sensitivity 14     Detect Sig Strength 1000:  29.6m km

Electronic Warfare Jammers:   Missile 3   

Admiral Lazarev-C class Command Destroyer      20,000 tons       491 Crew       4,541.6 BP       TCS 400    TH 4,000    EM 3,390
10000 km/s    JR 6-500      Armour 5-65       Shields 113-565       HTK 111      Sensors 70/0/0/0      DCR 24-12      PPV 38.4
Maint Life 1.02 Years     MSP 2,103    AFR 753%    IFR 10.5%    1YR 2,035    5YR 30,531    Max Repair 500 MSP
Hangar Deck Capacity 250 tons     Magazine 786 / 0   
Kapitan pervogo ranga    Control Rating 4   BRG   AUX   ENG   FLG   
Intended Deployment Time: 9 months    Flight Crew Berths 5    Morale Check Required   

Chernov Aeromarine J20000(6-500) Military Jump Drive     Max Ship Size 20000 tons    Distance 500k km     Squadron Size 6

Kuznetsov MCRD-1000.00 (4)    Power 4000    Fuel Use 43.67%    Signature 1000    Explosion 12%
Fuel Capacity 1,231,800 Litres    Range 25.4 billion km (29 days at full power)
Danilov-Morozov Theta S113 / R565 Shields (1)     Recharge Time 565 seconds (0.2 per second)

Kovalev-Makarov Size 8.00 Missile Launcher (60.0% Reduction) (8‎‎)     Missile Size: 8    Rate of Fire 85
Zhukov Warning & Control Missile Fire Control FC74-R20 (1)     Range 74.3m km    Resolution 20   ECCM-4
Nablyudatel Surveillance Missile (2)    Speed: 22,950 km/s    End: 184.8m     Range: 254.4m km    WH: 0    Size: 8    TH: 76/45/22
Kinzhal Mod.2 AShM (96)    Speed: 39,000 km/s    End: 30.3m     Range: 71m km    WH: 12    Size: 8    TH: 182/109/54

Shevchenko-Maslov Micrometeorite Detector AS11-R1 (1)     GPS 28     Range 11.2m km    MCR 1m km    Resolution 1
Danilov Electronics Industries High-Res Active Search Sensor AS95-R20 (1)     GPS 5600     Range 95.9m km    Resolution 20
Kalinin Electronic Systems Thermal Sensor TH5-70 (1)     Sensitivity 70     Detect Sig Strength 1000:  66.1m km

Electronic Warfare Jammers:   Missile 3   

Strike Group
2x MiG-65S Fighter   Speed: 19333 km/s    Size: 2.48

Orlan class Frigate      10,000 tons       296 Crew       2,484.6 BP       TCS 200    TH 2,000    EM 1,200
10000 km/s      Armour 6-41       Shields 40-400       HTK 64      Sensors 14/0/0/0      DCR 22-22      PPV 40
Maint Life 1.25 Years     MSP 1,510    AFR 400%    IFR 5.6%    1YR 1,002    5YR 15,034    Max Repair 500 MSP
Kapitan vtorogo ranga    Control Rating 2   BRG   AUX   
Intended Deployment Time: 12 months    Morale Check Required   

Kuznetsov MCRD-1000.00 (2)    Power 2000    Fuel Use 43.67%    Signature 1000    Explosion 12%
Fuel Capacity 608,800 Litres    Range 25.1 billion km (29 days at full power)
Danilov-Morozov Theta S40 / R400 Shields (1)     Recharge Time 400 seconds (0.1 per second)

Romanov-Mikhailov 25cm Railgun V50/C5 (5x4)    Range 250,000km     TS: 10,000 km/s     Power 15-5     RM 50,000 km    ROF 15       
Markov & Golubev Beam Fire Control R320-TS10000 (1)     Max Range: 320,000 km   TS: 10,000 km/s    ECCM-4     97 94 91 88 84 81 78 75 72 69
Belov & Kiselev Tokamak Fusion Reactor R25 (1)     Total Power Output 25.2    Exp 5%

Shevchenko-Maslov Micrometeorite Detector AS11-R1 (1)     GPS 28     Range 11.2m km    MCR 1m km    Resolution 1
Kalinin Electronic Systems Thermal Sensor TH1.0-14.0 (1)     Sensitivity 14     Detect Sig Strength 1000:  29.6m km

Electronic Warfare Jammers:   Fire Control 4    Missile 3 
This fleet consists of shielded vessels only and is intended to perform breakthroughs alongside the Assault Carrier Fleet


4th Combat Fleet:
Frigate Task Group:
6x FF Pustelga-class Frigate
A modern missile frigate with limited point defense capability. This hull type is a direct descendant of the very first Russian warships.
1x JF Pustelga-P-class Jump Frigate
A modification of the Pustelga hull, specialized as a task group leader.

Old Frigate Task Group:
4x FF Krechet-class Frigate
A previous-generation missile frigate, veteran of the incursion.
1x JF Krechet-P class Jump Frigate
A jump-capable modification of the Krechet hull.

1x DD Admiral Nakhimov-class Destroyer
A previous-generation general purpose Destroyer.

Kagoshima Task Group:
3x DE Kagoshima (IC)-class Destroyer Escort
The newest generation of Calana point defense vessels, captured, crewed and pressed into service rather than scrapped.
Off-Topic: Fleet Specifications • show
Pustelga class Frigate      10,000 tons       263 Crew       2,160.3 BP       TCS 200    TH 2,000    EM 0
10000 km/s      Armour 5-41       Shields 0-0       HTK 64      Sensors 0/14/0/0      DCR 12-12      PPV 39
Maint Life 1.32 Years     MSP 1,570    AFR 400%    IFR 5.6%    1YR 958    5YR 14,366    Max Repair 500 MSP
Magazine 401 / 0   
Kapitan vtorogo ranga    Control Rating 2   BRG   AUX   
Intended Deployment Time: 12 months    Morale Check Required   

Kuznetsov MCRD-1000.00 (2)    Power 2000    Fuel Use 43.67%    Signature 1000    Explosion 12%
Fuel Capacity 611,100 Litres    Range 25.2 billion km (29 days at full power)

Romanov-Mikhailov 10cm Railgun V50/C3 (5x4)    Range 50,000km     TS: 10,000 km/s     Power 3-3     RM 50,000 km    ROF 5       
Markov & Golubev Beam Fire Control R160-TS10000 (1)     Max Range: 160,000 km   TS: 10,000 km/s    ECCM-2     94 88 81 75 69 62 56 50 44 38
Belov & Kiselev Tokamak Fusion Reactor R15-PB20 (1)     Total Power Output 15.1    Exp 10%

Kovalev-Makarov Size 8.00 Missile Launcher (60.0% Reduction) (5)     Missile Size: 8    Rate of Fire 85
Zhukov Warning & Control Missile Fire Control FC74-R20 (1)     Range 74.3m km    Resolution 20   ECCM-2
Kinzhal Mod.2 AShM (96)    Speed: 39,000 km/s    End: 30.3m     Range: 71m km    WH: 12    Size: 8    TH: 182/109/54

Zaytsev Electronics Active Search Sensor AS51-R100 (1)     GPS 2800     Range 51.8m km    Resolution 100
Shevchenko-Maslov Micrometeorite Detector AS11-R1 (1)     GPS 28     Range 11.2m km    MCR 1m km    Resolution 1
Kalinin Electronic Systems EM Sensor EM1.0-14.0 (1)     Sensitivity 14     Detect Sig Strength 1000:  29.6m km


Pustelga-P class Jump Frigate      10,000 tons       246 Crew       2,150.9 BP       TCS 200    TH 2,000    EM 0
10000 km/s    JR 5-100      Armour 5-41       Shields 0-0       HTK 59      Sensors 70/0/0/0      DCR 12-12      PPV 24
Maint Life 1.18 Years     MSP 1,368    AFR 400%    IFR 5.6%    1YR 1,002    5YR 15,035    Max Repair 500 MSP
Magazine 401 / 0   
Kapitan vtorogo ranga    Control Rating 2   BRG   AUX   
Intended Deployment Time: 12 months    Morale Check Required   

Makarov Aeromarine J10000(5-100) Military Jump Drive     Max Ship Size 10000 tons    Distance 100k km     Squadron Size 5

Kuznetsov MCRD-1000.00 (2)    Power 2000    Fuel Use 43.67%    Signature 1000    Explosion 12%
Fuel Capacity 610,600 Litres    Range 25.2 billion km (29 days at full power)

Kovalev-Makarov Size 8.00 Missile Launcher (60.0% Reduction) (5)     Missile Size: 8    Rate of Fire 85
Zhukov Warning & Control Missile Fire Control FC74-R20 (1)     Range 74.3m km    Resolution 20   ECCM-2
Kinzhal Mod.2 AShM (96)    Speed: 39,000 km/s    End: 30.3m     Range: 71m km    WH: 12    Size: 8    TH: 182/109/54

Zhukov Warning & Control Active Search Sensor AS81-R100 (1)     GPS 7000     Range 82m km    Resolution 100
Shevchenko-Maslov Micrometeorite Detector AS11-R1 (1)     GPS 28     Range 11.2m km    MCR 1m km    Resolution 1
Kalinin Electronic Systems Thermal Sensor TH5-70 (1)     Sensitivity 70     Detect Sig Strength 1000:  66.1m km

Krechet class Frigate      10,000 tons       267 Crew       1,731.1 BP       TCS 200    TH 1,600    EM 0
8000 km/s      Armour 4-41       Shields 0-0       HTK 63      Sensors 0/8/0/0      DCR 13-13      PPV 39
Maint Life 1.60 Years     MSP 1,124    AFR 267%    IFR 3.7%    1YR 509    5YR 7,635    Max Repair 400 MSP
Magazine 361 / 0   
Kapitan vtorogo ranga    Control Rating 2   BRG   AUX   
Intended Deployment Time: 12 months    Morale Check Required   

Kuznetsov MPRD-800.00 (2)    Power 1600    Fuel Use 52.41%    Signature 800    Explosion 12%
Fuel Capacity 698,000 Litres    Range 24 billion km (34 days at full power)

Romanov-Mikhailov 10cm Railgun V10/C3 (5x4)    Range 10,000km     TS: 8,000 km/s     Power 3-3     RM 10,000 km    ROF 5       
Markov & Golubev Beam Fire Control R128-TS8000 (1)     Max Range: 128,000 km   TS: 8,000 km/s    ECCM-1     92 84 77 69 61 53 45 38 30 22
Belov & Kiselev Stellarator Fusion Reactor R16-PB20 (1)     Total Power Output 15.5    Exp 10%

Kovalev-Makarov Size 8.00 Missile Launcher (60.0% Reduction) (5)     Missile Size: 8    Rate of Fire 85
Zhukov Warning & Control Missile Fire Control FC76-R50 (1)     Range 76.2m km    Resolution 50   ECCM-1
Kinzhal AShM (45)    Speed: 29,325 km/s    End: 40.4m     Range: 71.1m km    WH: 16    Size: 8    TH: 136/82/41

Shevchenko-Maslov Micrometeorite Detector AS7-R1 (1)     GPS 21     Range 7.3m km    MCR 658.1k km    Resolution 1
Zaytsev Electronics Active Search Sensor AS33-R100 (1)     GPS 2100     Range 33.9m km    Resolution 100
Markov-Semenov EM Sensor EM1.0-8.0 (1)     Sensitivity 8     Detect Sig Strength 1000:  22.4m km

Krechet-P class Jump Frigate      10,000 tons       244 Crew       1,810.6 BP       TCS 200    TH 1,600    EM 0
8000 km/s    JR 5-100      Armour 5-41       Shields 0-0       HTK 60      Sensors 8/8/0/0      DCR 13-13      PPV 24
Maint Life 1.77 Years     MSP 1,196    AFR 229%    IFR 3.2%    1YR 470    5YR 7,057    Max Repair 400 MSP
Magazine 361 / 0   
Kapitan vtorogo ranga    Control Rating 2   BRG   AUX   
Intended Deployment Time: 12 months    Morale Check Required   

Makarov Aeromarine J10000(5-100) Military Jump Drive     Max Ship Size 10000 tons    Distance 100k km     Squadron Size 5

Kuznetsov MPRD-800.00 (2)    Power 1600    Fuel Use 52.41%    Signature 800    Explosion 12%
Fuel Capacity 698,300 Litres    Range 24 billion km (34 days at full power)

Kovalev-Makarov Size 8.00 Missile Launcher (60.0% Reduction) (5)     Missile Size: 8    Rate of Fire 85
Zhukov Warning & Control Missile Fire Control FC76-R50 (1)     Range 76.2m km    Resolution 50   ECCM-1
Kinzhal AShM (45)    Speed: 29,325 km/s    End: 40.4m     Range: 71.1m km    WH: 16    Size: 8    TH: 136/82/41

Shevchenko-Maslov Micrometeorite Detector AS7-R1 (1)     GPS 21     Range 7.3m km    MCR 658.1k km    Resolution 1
Zaytsev Electronics Active Search Sensor AS33-R100 (1)     GPS 2100     Range 33.9m km    Resolution 100
Markov-Semenov EM Sensor EM1.0-8.0 (1)     Sensitivity 8     Detect Sig Strength 1000:  22.4m km
Markov-Semenov Thermal Sensor TH1.0-8.0 (1)     Sensitivity 8     Detect Sig Strength 1000:  22.4m km


Admiral Nakhimov class Destroyer      20,000 tons       519 Crew       3,657.2 BP       TCS 400    TH 3,200    EM 0
8000 km/s      Armour 7-65       Shields 0-0       HTK 113      Sensors 8/0/0/0      DCR 25-12      PPV 73.4
Maint Life 1.29 Years     MSP 2,071    AFR 640%    IFR 8.9%    1YR 1,311    5YR 19,671    Max Repair 400 MSP
Magazine 706 / 0   
Kapitan pervogo ranga    Control Rating 3   BRG   AUX   CIC   
Intended Deployment Time: 12 months    Morale Check Required   

Kuznetsov MPRD-800.00 (4)    Power 3200    Fuel Use 52.41%    Signature 800    Explosion 12%
Fuel Capacity 1,272,700 Litres    Range 21.9 billion km (31 days at full power)

Romanov-Mikhailov 20cm Railgun V40/C4 (5x4)    Range 160,000km     TS: 8,000 km/s     Power 12-4     RM 40,000 km    ROF 15       
Markov-Maximov Beam Fire Control R256-TS8000 (1)     Max Range: 256,000 km   TS: 8,000 km/s    ECCM-1     96 92 88 84 80 77 73 69 65 61
Fedorov & Bogdanov Stellarator Fusion Reactor R20-PB20 (1)     Total Power Output 20.1    Exp 10%

Kovalev-Makarov Size 8.00 Missile Launcher (60.0% Reduction) (8‎)     Missile Size: 8    Rate of Fire 85
Zhukov Warning & Control Missile Fire Control FC76-R50 (1)     Range 76.2m km    Resolution 50   ECCM-1
Kinzhal AShM (88‎)    Speed: 29,325 km/s    End: 40.4m     Range: 71.1m km    WH: 16    Size: 8    TH: 136/82/41

Shevchenko-Maslov Micrometeorite Detector AS7-R1 (1)     GPS 21     Range 7.3m km    MCR 658.1k km    Resolution 1
Zhukov Warning & Control Active Search Sensor AS53-R100 (1)     GPS 5250     Range 53.7m km    Resolution 100
Markov-Semenov Thermal Sensor TH1.0-8.0 (1)     Sensitivity 8     Detect Sig Strength 1000:  22.4m km

Kagoshima (IC) class Destroyer Escort      22,746 tons       724 Crew       5,217.1 BP       TCS 455    TH 3,975    EM 0
8737 km/s      Armour 7-71       Shields 0-0       HTK 125      Sensors 0/0/0/0      DCR 6-2      PPV 147
Maint Life 0.46 Years     MSP 860    AFR 690%    IFR 9.6%    1YR 1,852    5YR 27,782    Max Repair 662.5 MSP
Magazine 0 / 112   
Kapitan vtorogo ranga    Control Rating 1   BRG   
Intended Deployment Time: 12 months    Morale Check Required   

Inertial Fusion Drive  EP1325 (3)    Power 3975    Fuel Use 13.03%    Signature 1325    Explosion 10%
Fuel Capacity 650,000 Litres    Range 39.5 billion km (52 days at full power)

10cm Railgun V50/C3 (49x4)    Range 50,000km     TS: 8,737 km/s     Power 3-3     RM 50,000 km    ROF 5       
Beam Fire Control R160-TS9000 (2)     Max Range: 160,000 km   TS: 9,000 km/s    ECCM-3     94 88 81 75 69 62 56 50 44 38
Inertial Confinement Fusion Reactor R4 (49)     Total Power Output 173.5    Exp 5%

Size 28 Decoy Launcher (4)     Decoy Size: 28    Hangar Reload 264 minutes    MF Reload 44 hours

Active Search Sensor AS20-R1 (1)     GPS 120     Range 20.5m km    MCR 1.8m km    Resolution 1

Electronic Warfare Jammers:   Sensor 3    Fire Control 3    Missile 3
This fleet consists of less protected vessels and is intended to perform long-range missile strikes and provide point defense on demand.


Commercial Carrier Fleet:
2x CVE Patrulniy (MC)-class Escort Carrier
A commercial carrier designed for convoy escort duty, but employed throughout the incursion thanks to its tremendous staying power.

Strike Group:
142x MiG-65-class Fighter
10x MiG-65S-class Fighter
Off-Topic: Fleet Specifications • show
Patrulniy (MC) class Escort Carrier      100,000 tons       946 Crew       5,281.3 BP       TCS 2,000    TH 9,000    EM 0
4500 km/s      Armour 3-191       Shields 0-0       HTK 177      Sensors 11/14/0/0      DCR 1-0      PPV 0
MSP 10,033    Max Repair 250 MSP
Hangar Deck Capacity 10,000 tons     Magazine 2,000 / 0    Cryogenic Berths 400    Cargo Shuttle Multiplier 6   
Kapitan tret'yego ranga    Control Rating 1   BRG   
Intended Deployment Time: 3 months    Flight Crew Berths 200   
Maintenance Modules: 4 module(s) capable of supporting ships of 12,800 tons

Glushko MCRD-1000.00C (9)    Power 9000    Fuel Use 2.80%    Signature 1000    Explosion 5%
Fuel Capacity 2,046,000 Litres    Range 131.8 billion km (338 days at full power)

Ordnance Transfer Rate: 80 MSP per hour     Complete Transfer 25 hours
Zaytsev Electronics Active Search Sensor AS51-R100 (1)     GPS 2800     Range 51.8m km    Resolution 100
Shevchenko-Maslov Micrometeorite Detector AS11-R1 (1)     GPS 28     Range 11.2m km    MCR 1m km    Resolution 1
Kalinin Electronic Systems Thermal Sensor TH1.0-11.0 (1)     Sensitivity 11     Detect Sig Strength 1000:  26.2m km
Kalinin Electronic Systems EM Sensor EM1.0-14.0 (1)     Sensitivity 14     Detect Sig Strength 1000:  29.6m km



Grand Trophy Fleet:
17x DDG Kanazawa-class Missile Destroyer
An obsolete missile destroyer class captured in the Great Surrender of 2054, crewed by expendable Calana traitors.
10x DDG Kochi-class Missile Destroyer
An anti-FAC variant of the above hull.
Off-Topic: Fleet Specifications • show
Kanazawa class Missile Destroyer      17,125 tons       333 Crew       2,230.4 BP       TCS 342    TH 1,500    EM 0
4379 km/s      Armour 4-59       Shields 0-0       HTK 99      Sensors 6/0/0/0      DCR 6-3      PPV 63
Maint Life 0.68 Years     MSP 488    AFR 391%    IFR 5.4%    1YR 720    5YR 10,802    Max Repair 374.6 MSP
Magazine 1,414 / 56   
Kapitan vtorogo ranga    Control Rating 2   BRG   AUX   
Intended Deployment Time: 12 months    Morale Check Required   

Ion Drive  EP500.0 (3)    Power 1500    Fuel Use 30.0%    Signature 500    Explosion 10%
Fuel Capacity 650,000 Litres    Range 22.8 billion km (60 days at full power)

Size 28 Decoy Launcher (2)     Decoy Size: 28    Hangar Reload 264 minutes    MF Reload 44 hours
Size 6 Missile Launcher (30.0% Reduction) (35)     Missile Size: 6    Rate of Fire 735
Missile Fire Control FC64-R110 (1)     Range 64.9m km    Resolution 110   ECCM-1

Active Search Sensor AS56-R110 (1)     GPS 7920     Range 56.2m km    Resolution 110
Thermal Sensor TH1-6 (1)     Sensitivity 6     Detect Sig Strength 1000:  19.4m km

Electronic Warfare Jammers:   Sensor 1    Fire Control 1    Missile 1   

Kochi class Missile Destroyer      17,125 tons       333 Crew       2,230.4 BP       TCS 342    TH 1,500    EM 0
4379 km/s      Armour 4-59       Shields 0-0       HTK 99      Sensors 6/0/0/0      DCR 6-3      PPV 63
Maint Life 0.68 Years     MSP 488    AFR 391%    IFR 5.4%    1YR 720    5YR 10,802    Max Repair 374.6 MSP
Magazine 1,414 / 56   
Kapitan vtorogo ranga    Control Rating 2   BRG   AUX   
Intended Deployment Time: 12 months    Morale Check Required   

Ion Drive  EP500.0 (3)    Power 1500    Fuel Use 30.0%    Signature 500    Explosion 10%
Fuel Capacity 650,000 Litres    Range 22.8 billion km (60 days at full power)

Size 28 Decoy Launcher (2)     Decoy Size: 28    Hangar Reload 264 minutes    MF Reload 44 hours
Size 6 Missile Launcher (30.0% Reduction) (35)     Missile Size: 6    Rate of Fire 735
Missile Fire Control FC36-R20 (1)     Range 36.8m km    Resolution 20   ECCM-1

Active Search Sensor AS31-R20 (1)     GPS 1440     Range 31.8m km    Resolution 20
Thermal Sensor TH1-6 (1)     Sensitivity 6     Detect Sig Strength 1000:  19.4m km

Electronic Warfare Jammers:   Sensor 1    Fire Control 1    Missile 1   



New Collier Fleet:
2x FSV Soratnik-P (MC)-class Fleet Support Vessel
A bulky fleet support vessel carrying fuel, supplies and missiles for the invasion. Due to an ongoing ordnance shortage, older basic Kinzhal missiles and even ancient Gonchaya missile variants had to be loaded.
Off-Topic: Fleet Specifications • show
Soratnik-P (MC) class Fleet Support Vessel      100,000 tons       771 Crew       4,445.4 BP       TCS 2,000    TH 9,000    EM 0
4500 km/s    JR 3-50(C)      Armour 2-191       Shields 0-0       HTK 150      Sensors 14/14/0/0      DCR 1-0      PPV 0
MSP 20,027    Max Repair 250 MSP
Magazine 4,000 / 0    Cargo Shuttle Multiplier 12   
Kapitan vtorogo ranga    Control Rating 1   BRG   
Intended Deployment Time: 3 months   

Krylov Thrust JC100K Commercial Jump Drive     Max Ship Size 100000 tons    Distance 50k km     Squadron Size 3

Glushko MCRD-1000.00C (9)    Power 9000    Fuel Use 2.80%    Signature 1000    Explosion 5%
Fuel Capacity 21,075,700 Litres    Range 1,357.2 billion km (3490 days at full power)
Refuelling Capability: 100,000 litres per hour     Complete Refuel 210 hours

Garda Mod.2 AMM (200)    Speed: 65,500 km/s    End: 0.9m     Range: 3.4m km    WH: 1    Size: 2    TH: 218/131/65
Kinzhal Mod.2 AShM (50)    Speed: 39,000 km/s    End: 30.3m     Range: 71m km    WH: 12    Size: 8    TH: 182/109/54
Kinzhal AShM (100)    Speed: 29,325 km/s    End: 40.4m     Range: 71.1m km    WH: 16    Size: 8    TH: 136/82/41
Gonchaya(M) AShM (100)    Speed: 25,525 km/s    End: 45.7m     Range: 70m km    WH: 12    Size: 8    TH: 112/67/33
Gonchaya AShM (200)    Speed: 20,050 km/s    End: 41.8m     Range: 50.3m km    WH: 12    Size: 8    TH: 83/50/25
Ordnance Transfer Rate: 80 MSP per hour     Complete Transfer 50 hours

Shevchenko-Maslov Micrometeorite Detector AS11-R1 (1)     GPS 28     Range 11.2m km    MCR 1m km    Resolution 1
Zaytsev Electronics Active Search Sensor AS51-R100 (1)     GPS 2800     Range 51.8m km    Resolution 100
Kalinin Electronic Systems EM Sensor EM1.0-14.0 (1)     Sensitivity 14     Detect Sig Strength 1000:  29.6m km
Kalinin Electronic Systems Thermal Sensor TH1.0-14.0 (1)     Sensitivity 14     Detect Sig Strength 1000:  29.6m km



Spy Fleet:
2x IS Kornilov-M-class Intelligence Ship 
A spy vessel recently refitted to possess commerce raiding capabilities, utilized as advance scouts for the invasion.
Off-Topic: Fleet Specifications • show
Kornilov-M class Intelligence Ship      8,000 tons       160 Crew       1,182.1 BP       TCS 160    TH 800    EM 0
5000 km/s    JR 3-50      Armour 1-35       Shields 0-0       HTK 42      Sensors 70/70/0/0      DCR 3-3      PPV 5.4
Maint Life 4.12 Years     MSP 1,502    AFR 171%    IFR 2.4%    1YR 142    5YR 2,123    Max Repair 160 MSP
Magazine 42 / 0   
Kapitan vtorogo ranga    Control Rating 1   BRG   
Intended Deployment Time: 40 months    Morale Check Required   

Makarov Aeromarine J8000(3-50) Military Jump Drive     Max Ship Size 8000 tons    Distance 50k km     Squadron Size 3

Glushko MCRD-400.00C (2)    Power 800    Fuel Use 4.42%    Signature 400    Explosion 5%
Fuel Capacity 288,400 Litres    Range 146.8 billion km (339 days at full power)

Romanov-Mikhailov 10cm Railgun V50/C3 (1x4)    Range 50,000km     TS: 6,250 km/s     Power 3-3     RM 50,000 km    ROF 5       
Korolev-Tarasov Beam Fire Control R120-TS5000 (SW) (1)     Max Range: 120,000 km   TS: 5,000 km/s    ECCM-3     92 83 75 67 58 50 42 33 25 17
Antonov Turbines Tokamak Fusion Reactor R5-PB60 (1)     Total Power Output 5.1    Exp 30%

Kovalenko-Fedorov Size 8.00 Missile Launcher (30.0% Reduction) (1)     Missile Size: 8    Rate of Fire 680
Golubev Electronics Missile Fire Control FC9-R10 (1)     Range 10m km    Resolution 10
Nablyudatel Surveillance Missile (2)    Speed: 22,950 km/s    End: 184.8m     Range: 254.4m km    WH: 0    Size: 8    TH: 76/45/22
Nablyudatel Buoy (5)    Speed: 0 km/s    End: 0m     Range: 0m km    WH: 0    Size: 1.9988    TH: 0/0/0
Slyshashiy Buoy (2)    Speed: 0 km/s    End: 0m     Range: 0m km    WH: 0    Size: 8    TH: 0/0/0

Zhukov Warning & Control Active Search Sensor AS81-R100 (1)     GPS 7000     Range 82m km    Resolution 100
Shevchenko-Maslov Micrometeorite Detector AS11-R1 (1)     GPS 28     Range 11.2m km    MCR 1m km    Resolution 1
Kalinin Electronic Systems EM Sensor EM5-70 (1)     Sensitivity 70     Detect Sig Strength 1000:  66.1m km
Kalinin Electronic Systems Thermal Sensor TH5-70 (1)     Sensitivity 70     Detect Sig Strength 1000:  66.1m km
ELINT Module (2)     Sensitivity 16     Detect Sig Strength 1000:  31.6m km
22
General C# Fiction / Re: Chronicle of the Calana War
« Last post by Kaiser on December 15, 2024, 12:41:24 PM »
Never seen such a mass surrender before, I'm wondering if Steve has read this.
23
General C# Fiction / Chronicle of the Calana War
« Last post by Ghostly on December 15, 2024, 12:17:30 PM »
In the year of our Lord 2047, the Russian Stellar Empire has encountered the Calana Imperium, the second known active interstellar alien civilization in the galaxy and the closest one to the Empire's current borders. Communications were established quickly, but the relationship soon turned sour due to the Empire's repeated trespasses on Calana territory. By 2049, the Imperium had declared hostilities, which amounted to a couple attacks on Russian surveillance buoys and the destruction of one of its spy-ships. No attempt at reprisal was made, as intelligence has been gathered of a Calana ship class with engines utilizing Inertial Confinement Fusion technology that Russian scientists were only beginning to conduct reactor experiments with, and fleets of significant size were observed roaming Calana space.

Off-Topic: A fleet of ~300 Fast Attack Craft encountered in the Kuiper 41 system • show


Four years of military buildup, information gathering, careful buoy placement and exploration followed, and by 2053 the Empire had decent relations with another interstellar polity, the Kiamba Freehold, who appear to have been warring with the Calana since before the first Russian ship has left the Solar System. Many Calana wrecks were observed in Kiamba space, and many were scavenged, revealing useful information about Calana ship classes. Furthermore, a massive Calana fleet exceeding a million tons was observed, seemingly stranded deep within Kiamba territory with no jump capability to allow it to come back. More importantly, the now extensive Russian buoy network revealed no attempts by the Calana to mount any offensive operations during this time.

Off-Topic: Lost Calana fleet blockading a worthless jump point • show


Emboldened by this information, the Russian Naval High Command has authorized a limited incursion into Calana territory to secure the shortest route through Omicron Lyrae into Kiamba space, where the Empire's dig site at an ancient ruin was beginning to cause diplomatic friction and its wealth desperately needed to be transported back home. Recent destruction of a Russian survey ship in Omicron Pyxidis was cited as a pretext. A small task force made up of older, Magneto-plasma-driven ships, led by a carrier, entered Calana space ahead of the dig site-bound cargo fleet and encountered no resistance; even after several civilian vessels were boarded, known enemy fleets were content to guard jump points into their populated systems.


Map of known Calana space in 2053.

After the cargo fleet had made a few trips, the incursion fleet was reinforced and committed to unrestricted naval warfare, destroying or capturing many lone ships, escorted convoys, and a small number of military patrols. Its most important prizes were Inertial Confinement-driven destroyers that were immediately sent to the nearest repair yards for disassembly and reverse-engineering, and massive Sagara-class fuel harvesters equipped with the same technology, which were towed all the way back to Terra where a shipyard expansion was ordered to accommodate their bulk.

On June 16th, 2053, the previously encountered massive FAC fleet was detected in 92 Draconis by a Russian missile frigate group. The frigates utilized their long-range, sensor-capable missiles in a novel staggered firing technique to rain a constant stream of destruction upon the enemy, eliminating a great number of them. A populated Kuiper 41 system, home to the biggest known Calana missile destroyer fleet, was infiltrated from several directions, and a previously known but unexplored high-traffic jump-point was traversed by a lone fighter scout and revealed to be a path into 91 Pegasi, which was very likely to be the Calana home system.

Off-Topic: Missile frigates utilizing staggered fire against a FAC fleet • show



Off-Topic: Frigate task group tracking down a large convoy • show

Off-Topic: Troop transport convoy surrendering to a new Admiral Lazarev-class destroyer • show

Off-Topic: Spy ship evading the Kuiper 41 fleet • show

Off-Topic: Carrier group poised to board the third advanced enemy destroyer in a row • show


Kuiper 41 Defense Fleet:
1x CL Nara – railgun jump cruiser of ubiquitous design
19x DDG Kanazawa – missile destroyer with long-range sensors
19x DDG Kochi – missile destroyer with anti-FAC sensors
21x DDG Tokushima – missile destroyer with anti-fighter sensors
1x SC Omuta – capabilities unknown, provisional designation Scout, likely to be a missile frigate
1x FF Fukui – missile frigate with anti-FAC sensors
2x FF Asahikawa - missile frigate with anti-fighter sensors

By October 2054 every lone ship in Kuiper 41 would get hunted down and boarded or destroyed and the enemy fleet would move from jump point to jump point in vain, never managing to catch the Empire’s forces. Suddenly, it decided to abandon the system and the three colonies within altogether, leaving the system through a jump point into the wreckage-strewn Eta Vulpercae system. Said jump point was guarded on the other side by a minor Russian detachment consisting of just two ships, an old Sapsan-class railgun frigate and a Carnot-class light railgun cruiser of Precursor design. The detachment was obliterated by enemy missiles at point blank range as soon as their fire controls came online, though not before destroying one enemy ship, damaging or crippling two more, and having another one surrender, only to be brutally eliminated by its former comrades. Barring a few expendable boarding craft, these were the first Russian losses of the war.

Off-Topic: The Kuiper fleet breakout • show


The Kuiper 41 fleet then proceeded into the Theta Puppis system, losing several ships on the way to missile fire of whatever Russian ship was close enough to intercept it. Carriers previously raiding in Kuiper 41 were able to outrun it and lay an ambush on the other side of the jump point, leaving behind their fighters, gunships and breaching pods to inflict as much damage as possible before the enemy could fight back, then attempt boarding on the surviving ships. The Calana fleet, despite being composed of fairly ancient vessels, outmassed the Empire's forces in the area 7:1 and strike group casualties were projected to be heavy.

This, however, turned out to be a non-issue, as on October 23rd, 2054, upon entering Theta Puppis and receiving a couple railgun volleys, the Calana fleet inexplicably surrendered with all hands.


The Great Surrender of 2054

Grand Trophy Fleet:
17x DDG Kanazawa
10x DDG Kochi
17x DDG Tokushima
1x FF Asahikawa

Now in possession of ~800 kilotons of Ion-era missile ships, and having its ordnance stockpiles doubled in size overnight, the Russian Stellar Empire had no choice but to start preparing for the invasion of the Calana home system. And since it had neither the ability nor the will to maintain its newest trophies, the invasion was on the clock. It was also noted with amusement by the High Command that the Omuta-Fukui-Asahikawa-class ships were of an even older generation, boasting Nuclear Gas-Core engines, and their sluggish top speed was the only thing that made the ambush possible. The fleet was to remain in place until a tanker could arrive to refuel it, its fuel tanks emptied what must've been the final act of alien defiance, and an extensive screening proccess was carried out to ascertain the Calana crews' willingness to fight for the Imperial cause.

A blockade of the 91 Pegasi jump point was established, and more confoundingly, the intermittent transits of lone, unprepared Calana combat ships through the jump point did not cease, with many ships appearing brand new, fresh off the shipyard and boasting the coveted Inertial Fusion technology. A few troop transport convoys entered Kuiper too, and due to the jump shock no ship was in shape to fight back before getting overwhelmed.

This, along with the recent surrenders, has left the High Command confused as to what state the Imperium's communications were in and what sort of political upheaval it might be experiencing. In just a few short months, the Empire has captured enough prize ships for even the most pessimistic projections to forecast immediate finalization of the Inertial Confinement Fusion Reactor tech and full completion of the respective Engine tech as soon as scrapping operations were complete, and many thousands of tons of precious gallicite were expected to be recovered from the wrecks of the ships that didn't warrant or weren't feasible to capture.


The Kuiper 41 ship graveyard

Russian military intelligence has theorized that the ships attempting to pass through Kuiper 41 were aiming to enter the empty system of 95 Pegasi where a Calana jump point blockade was established for reasons unknown, but said system proved inconsequential in the year to come and no ship within has made any attempt to disrupt the Empire’s operations as preparations for the invasion were underway.
24
Humanity First / Humanity First: 2154 to 2155, Mopping Up
« Last post by Kurt on December 14, 2024, 09:20:32 AM »
April 5, 2154
The Xi Bootis Expeditionary Force has refueled, resupplied, and taken on all of the missiles carried by the waiting UNREP group.  Unfortunately, the UNREP groups missiles only filled the CVA’s magazines to just over 50%.  Still, it was better than nothing.  With their resupply complete, the expeditionary force sets out for the Xi Bootis system to escort the troop transports headed to the planet with the suspected Reaper infestation. 

May 7, 2154
The Hive Fleet Leviathan Expeditionary Force returns to Omicron Tucanae Base after probing the nearby systems, looking for any trace of Leviathan ships that had been sighted in the area.  Much to Rear Admiral Casella’s frustration, they could find no trace of any hive ships in any of the systems where they had previously been sighted. 

Admiral Casella detaches the carrier France, along with two destroyers and two destroyer escorts, to act as the system defense force.  A jump-capable battleship will be dispatched from the Solar System to provide the force with jump capability, giving the forward base in the Omicron Tucanae system the ability to project force to any of the nearby systems where a hive ship might appear. 

May 10, 2154
The ground assault force has arrived over Xi Bootis B-III, escorted by the Xi Bootis Expeditionary Fleet.  The transports immediately begin dropping the 3rd, 5th, and 29th Marine Divisions(reinforced).  Initial intel reports place the enemy Reaper force at 448 centurion infantry robots, 3 decurion AA mechs, and assorted support and leader units.  They are no match for the augmented and heavily armed and armored marines and their heavy armor and artillery support. 

The Reapers were concentrated in a defensive perimeter around what appeared to be a destroyed outpost, and the marine assault elements immediately attacked, pressing in from all sides.  The small Reaper force was overwhelmed and wiped out in a matter of hours, at the cost of seven marines KIA. 

After mopping up, the marines were loaded onto the transports.  Their next target was in the Kappa Ceti system, and would be a much tougher nut to crack. 

June 18, 2154
The scout left behind in the Kappa Ceti system to watch the Reaper base detects a Hotel class Reaper ship in the outer system.  The Hotel class is 17,772 tons and has commercial engines. 

August 29, 2154
The assault transports have finally rendezvoused with the Xi Bootis Expeditionary Force five million kilometers from Kappa Ceti III.  For several weeks as they waited for the assault transports to arrive, the Terran warships had been watching the planet, the Reaper outpost, and the orbiting Hotel class ship.  Commodore Gabehart and his staff had spent their time working out a plan to attack the Reaper outpost, and had decided to eliminate the ship before beginning landing operations.  In spite of it being a civilian ship and unlikely to interfere, it was a complication.  Shortly after the transports arrive the Angel of Retribution launched her fighters, and they moved forward towards the planet. 

One hour later the fighters were in position and launched against the ship in orbit over the planet.  Twenty-four missiles streaked away from the fighters, and slammed into the orbiting ship.  It only took eight to destroy it, and there was no opposition from the STO’s on the ground. 

The fighters turned back to the Angel, and once they were aboard the next phase started.  The Assault Carriers and battlecruisers detached from the rest of the force and moved forward, to just out of the known range of the STO’s on the planet.  They were followed by the troop transports, which were moving up about 50,000 kilometers from the planet. 

The Eternal Crusader took several hits from heavy particle STO’s at 228,000 kilometers, but her shields absorbed the damage and the force continued to advance, shielding the transports following behind.  The ground batteries pounded the two CVA’s with near continuous fire for the several minutes it took for the transports to close, but then the troop transports arrived and began dropping the three marine divisions.  It didn’t take long for the marines to drop, and then the transports turned and began racing away from the planet.  The warships would remain over the planet as long as it took for the transports to retreat, but the two big CVA’s shields hadn’t dropped below 90% during the engagement, so they were confident in their ability to shield the transports for as long as necessary.  Once the transports were out of range, the Terran warships followed them.  Now it was up to the marines. 

Much like their previous engagement with the Reapers, they were in protective emplacements, but would almost certainly come out to attach the marines when they landed.  Marine intel, gathered by the orbiting ships, estimated the Reaper force as follows:

Centurian Infantry Units: 1,715
Praetorian Combat Mechs: 286
Decurion AA Mech: 49
Support and Leadership: 916
Artillery: 67
Unk: 35

The estimate came with a warning that it should be considered unreliable as it was based on limited orbital observation.  The line marines found the warning hilarious, as they never considered any intel report reliable, ever.  As expected, the Reapers came out to meet the marines as they advanced and the fighting was heavy from the first.  By eight hours into the landing, the marines had destroyed 246 centurions, 10 praetorians, 9 decurions, 42 support units, and 9 STO’s.  In exchange, the 114th Assault Battalion, which was at the forefront of the fighting, lost 22 marines. 

The marines completely overmatched the Reapers, and achieved multiple breakthroughs as they advanced, striking at exposed rear area elements, including the critical STO’s.  Another eight hours of fighting saw 286 centurion, 14 praetorians, and 7 decurions destroyed, along with 42 support units and 13 STO’s.  All this in exchange for 15 marine losses.   

The battle lasted for seventy-two hours.  After the first sixteen, it was mostly mopping up by the marines.  By the end of the battle, the marines lost 197 KIA, most of which were equipped with the older Mk IV or Mk V armor and augments.  The Reaper force totaled 2446 centurion infantry, 151 praetorian combat mechs, 84 Decurion AA mechs, 2268 support units of various types, 37 artillery, and 18 STO’s. 

With the planetary defenses defeated, it was time for the fleet to return to the Solar System for overhaul.  The marines loaded up onto their transports, and the force departed for the 111 Virginis system, where it would rendezvous with the support units. 

September 18,2 154
The Xi Bootis Expeditionary Force has refueled and resupplied from the support ships in the 111 Virginis system.  They have been out on the frontier for almost a year, and Commodore Gabehart decides it’s time to return home.  The hive menace on this frontier has been destroyed, and the two Reaper infestations have been cleared, opening the way for research teams to begin studying the ruins they protected. 

October 17,2 154
Troop transports arrive over Xi Bootis B-III and begin dropping the 1st Xeno Sturdy Battalion, two territorial guard brigades, and a construction group to begin work on the ruins and the ancient construct on the planet.   

October 24, 2154
The Xi Bootis Expeditionary Force returned to Terra on this date.  The fleet’s arrival was celebrated by world-wide parades and the government announced the rest of the week would be a holiday for all except essential workers. 

Commodore Gabehart is promoted to rear admiral, and awards are handed out to many of the officers and crewers.  The expeditionary force’s ships are immediately sent to a much-needed overhaul. 

November 22, 2154
The 3rd LR Survey Group has finished its overhaul on Terra and will now be dispatched to the Bobruisk territories to continue the Empire’s effort to determine the location of their home world, or at least a major colony. 

On this same day, the 1st Xeno Study Regiment on Xi Bootis B-III completes its study of the ruined outpost on that planet.  The outpost belongs to an unknown race, given the code-name Hellcat, and the outpost contains ten potentially usable installations.  The Xeno regiment will begin studying the ancient construct, while the construction units begin retrofitting the preserved installations. 

November 28,2 154
The 1st Xeno Study regiment completes its study of the ancient construct on Xi Bootis B-II and determines that it will assist researchers working on defensive technologies. 

December 10, 2154
Surprising no one, a long-range survey ship from the 2nd LR Survey Group confirms the presence of a ruined city on Kappa Ceti III, the site of the Reaper infestation.  In addition, the survey ship finds large deposits of eleven TN resources at moderate availability levels.  The planet has a noxious atmosphere and is too cold for humans, but is fairly easily terraform-able. 

December 22, 2154
The construction units complete their work recovering the stored installations on Xi Bootis B-III.  In all, they recovered a mine, three auto mines, a terraformer, and a deep space tracking station, along with assorted alien artifacts, 10,400 tons of duranium, 5,800,000 tons of fuel, and five fire control jamming units.  The orbiting transports begin loading the ground units to move them to Kappa Ceti. 

January 21, 2154
A raider is detected by the sensor buoy orbiting Zeta Doradus II in the Leviathan Frontier.  The contact report is relayed to the courier at the jump point, which immediately jumps back to Omicron Tucanae to report.  When the report is received several hours later on Omicron Base, the orbiting squadron is dispatched to intercept the raider. 

Just hours later a second raider is detected in the 70 Ophiuchi system, 333 million kilometers from the small colony on the second planet.  The closest warships are at Shield Base in the Monoceri system, nine days away.  A battlegroup is dispatched, but in the meantime the outpost will have to rely on its STO’s. 

The Raider in 70 Ophiuchi heads directly for the innermost planet, which has a mining outpost on it.  Unfortunately, the mining outpost has not yet received its contingent of STO’s, and so is unprotected.  The Raider briefly orbits the mining outpost then departs for A-II and its much larger, and protected, colony.  As it approaches the colony, the raider is brought under fire by the defensive STO’s and quickly destroyed, but not before it gets off one salvo with its lasers, killing four thousand colonists.   

March 4, 2155
A ship from the 3rd LR survey group detects five Bobruisk commercial ships in the NN 4176 system during its survey.  This is a hopeful sign.  The NN 4176 system was selected by the survey command as the most likely of the remaining known systems to lead to Bobruisk territory, as it has an unbroken chain of jump gates leading to it from the first contact point.  The fact that a newly discovered jump point in the system also has been stabilized, and the presence of commercial ships, means that it is increasingly likely that the survey group is on the right track.   

March 20, 2155
A contact report has reached 111 Virginis from the Theta Corvi system, two jumps away.  The report states that an unarmed hive ship, Charon class, has been spotted multiple times in the system, most recently close to the jump point to 103 Ceti (in between Theta Corvi and 111 Virginis).  Captain Luis Bray, CO of the Virginis Garrison Force, would like to take his battlecruiser and supporting ships out to eliminate the threat, but he has no jump ships and the stabilized network has not been extended to Theta Corvi yet. 

May 24, 2155
A sensor probe launched from a survey ship probing the systems in the Bobruisk sphere in the HIP 96183 system detects an outpost from an entirely new race on the innermost planet of the system.  The survey commander had been close to calling their survey efforts off as they were beyond the Bobruisk stabilization network, so out of their territory, but this new discovery has changed his mind. 

July 2, 2155
The ruined city found on Kappa Ceti III has been fully explored and contains 169 buildings that can be recovered. 
25
General C# Fiction / Re: United Nations Enclave - Scenario
« Last post by Mark Yanning on December 13, 2024, 03:44:48 PM »
Nice, gonna play it right now! I like the idea of scenario. Do we have also other scenario with multiple human faction in SOL? Would be nice...
26
General C# Fiction / Re: AAR: The Dawn of the Second Era
« Last post by jahwillprovide on December 12, 2024, 12:56:32 AM »
Ashes to Ambition: The Road Through 2077-78

January 9, 2077

Advancements in particle beam technology have extended their range to an impressive 200,000 kilometers, rivaling the railguns mounted on our Jaffa-class battlecruisers. This enhancement fundamentally shifts fleet tactics, enabling our vessels to engage targets from greater distances with precision, reducing their exposure to hostile fire. During simulations, this range advantage has already proven decisive, allowing Jaffa-class ships to operate effectively as fire-support platforms while retaining flexibility in fleet formations. Discussions are ongoing regarding integrating these particle beams into future ship designs, potentially redefining engagement strategies across the board. With this breakthrough, plans are underway to potentially arm our Red-class destroyers with these upgraded weapons. Meanwhile, microwave technology remains constrained by range limitations, delaying its deployment. Research will soon pivot to enhancing missile retargeting systems, aiming to eliminate the inefficiencies of self-detonation upon target destruction. If successful, we could see reliable systems operational by 2083.

January 11, 2077

A stabilized jump point has been revealed in the Danzig system, bringing us closer to locating the Marilith Empire’s home system. The effort marks another step forward in our exploration and expansion initiatives.

January 15, 2077

The Tau Ceti aliens have been detected in the Niven Black Hole System. Unlike previous encounters, their vessels have remained in the area. The UEF Harmony, a Beta II-class diplomatic ship, is 104 days away and will attempt to establish contact.

January 16, 2077

Our survey vessel pursued one of their ships into Codalus, encountering nine of their vessels. There were no hostilities, so our ship sat with them awaiting the Harmony’s arrival. Meanwhile, exploration beyond the stabilized jump point in Danzig revealed two terrestrial planets with oxygen atmospheres, though their extreme temperatures render them inhospitable to humans.



January 21, 2077

Before the Harmony arrived, our gravitational survey ship successfully established communications with the Tau Ceti aliens, who identify themselves as the Commonwealth of Sokcho. Their swift translation of our language is in stark contrast to the challenges faced with the Marilith Empire. The Harmony will proceed as planned to solidify diplomatic relations.

January 31, 2077

The Commonwealth has peacefully requested our withdrawal from Codalus, asserting it as their territory. We have agreed to their request, fostering a positive diplomatic precedent.

March 13, 2077

Battle Fleet training exercises have progressed steadily. The first ship to achieve full combat readiness is the UEF Advance, under the command of Ricky Cockram.

April 4, 2077

Both diplomatic vessels are now stationed to negotiate trade agreements with the Commonwealth of Sokcho and the Marilith Empire. These efforts aim to open new economic opportunities while bolstering interstellar diplomacy.

May 15, 2077

Our first ground company has completed training but our Alexandria-class Cruisers lack sufficient ammunition to tackle clearing the Sansibar System. Additional factories are being constructed to address this logistical shortfall. Terraforming efforts on Shayou II continue, preparing the planet for eventual colonization.

May 25, 2077

The first Idlev V-class freighters have rolled off the production line. These vessels surpass their predecessors in both speed and cargo capacity, with two Idlev Vs capable of carrying more than five Idlev IIIs combined. Their efficiency marks a significant milestone in logistical operations.

Code: [Select]
Idlev V class Freighter      200,000 tons       530 Crew       3,030.1 BP       TCS 4,000    TH 8,000    EM 0
2000 km/s      Armour 1-304       Shields 0-0       HTK 126      Sensors 1/1/0/0      DCR 1-0      PPV 0
MSP 9    Max Repair 250 MSP
Cargo 150,000    Cargo Shuttle Multiplier 18   
Lieutentant Commander    Control Rating 1   BRG   
Intended Deployment Time: 3 months   

MK IV Freighter Engine (8)    Power 8000    Fuel Use 2.24%    Signature 1000    Explosion 5%
Fuel Capacity 3,091,000 Litres    Range 124.4 billion km (719 days at full power)

MK II Commercial Thermal Sensor (1)     Sensitivity 1.6     Detect Sig Strength 1000:  10m km
MK II Commercial EM Sensor (1)     Sensitivity 1.6     Detect Sig Strength 1000:  10m km
June 2, 2077

The Gemini-class carriers have been redesigned into the Gemini II-class. They carry FACs rather than fighters and now include missile reloads for FACs, addressing logistical challenges in prolonged engagements. Concurrently, the Beta III-class diplomatic vessel has been conceptualized, boasting enhanced range and speed to support future operations across vast distances.

Code: [Select]
Gemini II class Carrier      36,000 tons       640 Crew       6,007.2 BP       TCS 720    TH 5,400    EM 0
7500 km/s    JR 3-50      Armour 7-97       Shields 0-0       HTK 136      Sensors 0/0/0/0      DCR 17-4      PPV 0
Maint Life 2.17 Years     MSP 7,175    AFR 592%    IFR 8.2%    1YR 2,042    5YR 30,635    Max Repair 900 MSP
Hangar Deck Capacity 10,000 tons     Magazine 768 / 0   
Commander    Control Rating 2   BRG   AUX   
Intended Deployment Time: 6 months    Flight Crew Berths 200    Morale Check Required   

MK I Carrier Jump Drive     Max Ship Size 36000 tons    Distance 50k km     Squadron Size 3

MK I Battlecruiser Engine (3)    Power 5400    Fuel Use 45.00%    Signature 1800    Explosion 15%
Fuel Capacity 4,711,000 Litres    Range 52.3 billion km (80 days at full power)

MK II Capital Ship Sensor (1)     GPS 19200     Range 99.6m km    Resolution 120

Strike Group
10x Warhorse Fast Attack Craft   Speed: 15314 km/s    Size: 19.98

This design is classed as a Military Vessel for maintenance purposes
This design is classed as a Carrier for auto-assignment purposes

Code: [Select]
Beta III class Diplomatic Ship      15,000 tons       182 Crew       1,038.7 BP       TCS 300    TH 2,100    EM 0
7000 km/s    JR 3-50(C)      Armour 1-54       Shields 0-0       HTK 46      Sensors 8/1/0/0      DCR 1-0      PPV 0
MSP 43    Max Repair 300 MSP
Captain    Control Rating 1   BRG   DIP   
Intended Deployment Time: 3 months   

MK III Diplomatic Jump Drive     Max Ship Size 15000 tons    Distance 50k km     Squadron Size 3

MK III Diplomatic Engine (3)    Power 2100    Fuel Use 2.67%    Signature 700    Explosion 5%
Fuel Capacity 404,000 Litres    Range 181.4 billion km (299 days at full power)

Diplomat Sensor (1)     Sensitivity 8     Detect Sig Strength 1000:  22.4m km
MK II Commercial EM Sensor (1)     Sensitivity 1.6     Detect Sig Strength 1000:  10m km

This design is classed as a Commercial Vessel for maintenance purposes
This design is classed as a Diplomatic Ship for auto-assignment purposes

July 16, 2077

A new alien vessel has been detected in the Thengo System, prompting a diplomatic response. The ship is slow, but its military engine signature has raised concerns. A Beta II-class vessel is 68 days away and will attempt contact.



August 26, 2077

Research into ECCM (electronic counter-countermeasures) has concluded, bolstering the fleet’s defenses against electronic warfare. This development reduces the necessity of closing range in engagements.

September 19, 2077

The Beta III-class shipyard expansion has been completed, with the first vessel entering construction. These ships will play a vital role in maintaining diplomatic ties across distant systems.

October 11, 2077

Diplomatic progress with the unknown aliens in the Thengo System remains slow, creating political pressure for President Joe Miga ahead of the upcoming election. His administration’s achievements in diplomacy with the Commonwealth and the Marilith Empire may bolster his chances, but unresolved tensions in Thengo linger.

November 17, 2077

Breakthroughs in linguistic translation have allowed communication with the Zambonga Imperium. They assert their claim over the Thengo System, escalating tensions.

December 2, 2077

A critical fuel shortage has emerged, prompting the deployment of more fuel harvesters to Jupiter and Saturn. Efforts to build additional refineries are underway to stabilize supply lines.

January 19, 2078

The Zambonga Imperium has formally rejected our territorial claims in Thengo and declared their intent to take the system. With conflict imminent, a Task Force of Jaffas and Reds is en route, though Oasis-class frigates stationed at Little Rose stand ready to defend the colony.

February 5, 2078

Our first encounter with the Zambonga’s Nagelring III-class ships proved costly. An attempted boarding operation led to the loss of 55 out of 75 Iron Striders, and only eight survived the capture of their ship. Future boarding actions will only proceed after enemy ships’ weapons have been partially disabled. The captured vessel will be studied and scuttled.

March 8, 2078

Exploration of Wolf 424 has led to the discovery of the Cannae System, though no evidence of the Zambonga homeworld has been found. The Task Force remains vigilant.

May 4, 2078

Resource shortages persist, with tritanium and fuel supplies critically low, placing a significant strain on both military operations and colony development. The fleet’s activity has been limited to essential deployments, while plans for further expansion and terraforming have slowed as resources are diverted to stabilize the supply chain. These shortages have also heightened the urgency for trade negotiations with other civilizations, as securing external resources could alleviate these growing pressures. Automated mines have been relocated to asteroid deposits, while refineries and harvesters work to stabilize the situation.

June 30, 2078

The final Zambonga ship has departed the Thengo System. A pursuit was briefly considered but ultimately dismissed to conserve critical resources essential for ongoing fleet operations. This decision reflects the United Earth Federation’s commitment to prioritizing strategic objectives over costly and uncertain engagements. The fleet remains focused on addressing known challenges, such as unraveling the long-standing mysteries of the Sansibar system. Allocating resources to a futile chase would jeopardize these efforts, ensuring the Federation stays aligned with its calculated, long-term goals. Pursuing it would drain vital resources,and our current efforts lie with investigating Sansibar’s long-neglected mysteries.

July 10, 2078

The first Warhorse-class FAC has entered service, equipped with surplus missiles. Its high speed and formidable missile payload promise to deliver swift and decisive strikes in future engagements.

July 18, 2078
In the Thengo System, while the Battle Fleet maintains position near the Cadmus jump point to defend Little Rose and Lucille, a new alien race has been detected in Orphicon. These unknown hostiles immediately destroyed the UEF Harmony, prompting urgent action. With limited fuel reserves, the fleet has been ordered to hold position, ensuring the colonies’ safety from potential incursions. Meanwhile, plans are underway to deploy the fleet more effectively against these new threats.



August 5, 2078
Research on missile retargeting has been completed, enabling the design of the improved Wasp Mk IV. The new missile sacrifices range for speed and accuracy, achieving 36,000 km/s and a maximum range of 30m km. Given the limitations of current fire control systems, designers deemed this trade-off essential to improve combat effectiveness. Production of the Mk IV has been fast-tracked with President Joe Miga’s approval.
While on station near the Cadmus jump point, the last Zambonga ship entered the Thengo System. The UEF Caesar intercepted and destroyed the vessel with a single railgun shot, marking the fleet’s continued vigilance in protecting UEF territories.

Code: [Select]
Missile Size: 8.00 MSP  (20.000 Tons)     Warhead: 12.92    Radiation Damage: 12.92
Speed: 36,000 km/s     Fuel: 1,700     Flight Time: 15 minutes     Range: 32.07m km
Active Sensor Strength: 0.28   EM Sensitivity Modifier: 8
Resolution: 100    Maximum Range vs 5000 ton object (or larger): 3,919,361 km
Cost Per Missile: 10.878     Development Cost: 521
Chance to Hit: 1k km/s 360%   3k km/s 120%   5k km/s 72%   10k km/s 36%

Note: I thought that missile retargeting meant they would find new targets, I could have had these missiles the whole time. The language could use improvement in that aspect

Sep 4, 2078
 There has been no sign on our sensor buoys of the new species of aliens jumping through to our systems, so our Battle Fleet has been ordered home to refuel. Once refueled, they will proceed to Sansibar to expend the last of our Wasp MK IIIs and finish clearing the system, marking it safe for civilian travel.

Sep 24, 2078
 The Battle Fleet has arrived in the Sansibar System and will make haste to secure each planet. We know there is at least one hostile ship in this system, as it escaped during our last encounter.

Sep 26, 2078
The Deathslayer that evaded us previously is in orbit of Sansibar II, where we last fought. It appears to be alone. We will move closer to confirm and launch a single salvo.
The Deathslayer is too small for the Alexandria-class cruiser’s sensors to lock onto accurately, so we’ll need to close the distance to fire. It has begun firing missiles at us, targeting Abdiel specifically. It seems to be retreating toward Sansibar I—or leading us into a potential ambush there.
Our angle of pursuit allowed us to close to 2.4 million kilometers, but that wasn’t close enough for our anti-missile missiles to engage. Knowing from prior encounters that those missiles are ineffective against Deathslayers, we will follow it to Sansibar I to investigate further.



Sep 27, 2078
As we approach Sansibar I, our sensors detect no large ships in orbit. However, Sansibar I does have surface-to-orbit defenses, evident from the debris of our Shianzpla III still floating in orbit after two decades.
The Deathslayer has entered orbit of Sansibar I and awaits us. The Jaffa-class battlecruisers have been given the green light to engage, as they have yet to record any kills. UEF King George successfully destroyed the last of the Deathslayer-class FACs. Efforts will now shift to neutralizing the ground-based STOs on both planets.
First Company will deploy from Mars to Sansibar I, while the fleet focuses on eliminating ground forces on Sansibar II. The planet is clear of STOs, and troop transports will arrive within 10 days to test our green troops.

Oct 8, 2078
A Zambonga ship has appeared in the Thengo System, but our main fleet is too far away to intercept it in time. The Oasis-class frigates stationed at Little Rose, intended primarily for citizen morale, will attempt to intercept the intruder. These frigates are extremely outdated, armed with 10 year old particle beams and 20 year old gauss turrets. However, the Oasis II-class refit is already planned, featuring updated weaponry with increased range and efficiency.
The Hyderabad-class ship, identified at 12,000 tons, is 2,000 km/s slower than our frigates and began fleeing as soon as we mobilized. Although it has a military engine signature, it has not returned fire.
After a prolonged chase and exchanges at close range, the UEF Andromeda claimed the kill, obliterating the larger Hyderabad-class vessel with its outdated cannons and particle beams. The frigates will return to Earth for well-deserved refits.



Oct 10, 2078
Our troops have secured Sansibar I and are advancing toward Sansibar II. During the occupation, a colossal dormant construct was discovered on Sansibar I—a massive, ring-like technological structure of unknown origin, intricately detailed with patterns that suggest a blend of functionality and artistry. Its size and complexity imply a purpose far beyond our current understanding.
“This world isn’t dead—it’s asleep. That thing down there, it’s not just a relic. It’s a question, waiting for an answer we might not be ready to give. Twenty years, we bled and built to get here, and now we stand on the edge of something older than our species. Mark your scans, keep your distance, and let history speak for itself. Our part in this story is just beginning.”
– Colonel Micaela Stolz
The defending forces encountered on Sansibar I appear to be robotic in nature, raising questions about their creators. Are they remnants of an extinct civilization, autonomous guardians, or something else entirely? Salvage and xenoarchaeology teams will prioritize uncovering the truth behind both the construct and these enigmatic defenders.



Oct 15, 2078
 After a grueling four-day battle on Sansibar II, we’ve confirmed that we are fighting autonomous machines, not an alien species. What fate befell their creators that led them to build these relentless war machines? The largest alien ship is undergoing salvage, expected to be complete within a month, and may provide answers. Unlike Sansibar I, Sansibar II does not contain a dormant construct.

Oct 21, 2078
While the Oasis-class frigates undergo refits, the UEF Advance and UEF Albany have been dispatched to safeguard the colonies at Little Rose and Lucille. These settlements remain secure under the legendary Red-class destroyers.

Oct 31, 2078
The black hole system of Plianzhnzhi, directly connected to Sol, has finally been opened for exploration after years of being deemed too vast and hazardous to survey. Its proximity to humanity’s home system makes it a key strategic region, demanding a comprehensive survey despite the inherent challenges.
Two jumps beyond Plianzhnzhi lies the newly discovered Cinnabar System, a treasure trove of resources. Rich in mineral deposits, including substantial reserves of gallicite essential for shipbuilding, and home to three gas giants for refueling, Cinnabar offers immense potential. Plans to establish colonies in this system are being accelerated, as it could serve as a self-sufficient industrial and logistical hub for future expansion into deeper space.

Code: [Select]
Cinnibar I
     Duranium 1,733,522   Acc 0.5
     Neutronium 1,500,625   Acc 0.1
     Tritanium 14,984,641   Acc 0.1
     Vendarite 8,934,121   Acc 0.1
     Sorium 1,882,384   Acc 0.9
     Gallicite 1,270,129   Acc 0.2

 Cinnibar II
     Sorium 7,497,000   Acc 0.8

 Cinnibar IV
     Duranium 17,672   Acc 0.2
     Neutronium 9,333,025   Acc 0.2
     Corundium 19,518,724   Acc 0.1
     Gallicite 17,892,900   Acc 0.1

 Cinnibar VI
     Gallicite 1,703,025   Acc 0.3

 Cinnibar VII
     Sorium 426,000   Acc 0.3

 Cinnibar VIII
     Duranium 2,384,928   Acc 0.1
     Vendarite 32,626,944   Acc 0.1
     Gallicite 10,732,176   Acc 0.3

 Cinnibar IX
     Sorium 15,682,500   Acc 0.5

 Cinnibar IX - Moon 9
     Duranium 122,018   Acc 0.8
     Mercassium 144,400   Acc 0.4
     Uridium 521,284   Acc 0.5
     Gallicite 2,547,216   Acc 0.6

Nov 9, 2078
The UEF Advance and UEF Albany intercepted a second Hyderabad-class ship in Thengo. Ricky Cockram aboard the UEF Advance claimed the kill with a devastating volley of railgun fire. The destroyers will return to their posts, ensuring the safety of Little Rose’s citizens.



Nov 11, 2078
Salvage efforts on the alien vessels from Sansibar have revealed that their technology is no more advanced than ours. The aliens, now designated as “Precursors,” remain an enigma.

Dec 25, 2078
In a tightly contested election, Joe Miga, despite strong leadership during turbulent times, was defeated. Laurent Bisson of the Federalist Party emerged victorious. Citizens can anticipate a shift toward individual rights under his administration.
Bisson, a seasoned leader, previously governed Earth, the largest population center by far. His tenure promises new policies that balance humanity’s expanding empire with the autonomy of its citizens.

Current map of our nearby systems, the Mirage Coalition are south of us
27
Humanity First / Re: Humanity First Comments Thread
« Last post by Kurt on December 10, 2024, 06:14:45 PM »
That's a huge battle, well done. Wonder why they didn't group up their ships properly.

I wondered that as well.  I would have beat them no matter what, I think, but if they had unified their groups it would have been harder, especially since some of the ships were anti-missile escorts. 
28
Humanity First / Re: Humanity First Comments Thread
« Last post by Garfunkel on December 08, 2024, 06:54:05 PM »
That's a huge battle, well done. Wonder why they didn't group up their ships properly.
29
Humanity First / Humanity First: Another Expedition to the Kraken Frontier
« Last post by Kurt on December 08, 2024, 12:05:35 PM »
July 20, 2153
A survey ship operating in the Phi Arietis system, adjacent to the 111 Virginis system, detects eight Hive Fleet Kraken ships in close proximity to a comet that was the target of the survey ship.  There are two Mors class escorts, and six new 15,432 ton ships designated as the Camazolz class.  The survey ship immediately turns away and runs for the jump point back to 111 Virginis, but fortunately the hive ships have no interest in fighting and they too turn to run. 

July 25, 2153
A long-range survey ship jumps into the 111 Virginis system from Phi Arietis and sends off a contact warning to the courier network ship on the 111 Virginis to Sigma Eridani jump point.  Once that ship received the message, it jumped out and then returned a few minutes later, after delivering the message to the next ship in the chain.  The message would then be passed back up the chain first to the 1st Expeditionary Fleet, and then to fleet HQ on Terra in a matter of hours.  Admiral Calligaris by then was in the 55 Bootis system headed home.  Because the hive ships didn’t attack the survey ship, she decided to continue home rather than detaching any of her ships, which were badly in need of overhauls. 

July 26, 2153
A group of four survey ships were assembled on the jump point in the 111 Virginis system that led to the Phi Arietis system.  They were waiting for the remaining two ships of their squadron when the eight Hive Fleet Kraken ships that had caused them to abandon the Phi Arietis system jumped into 111 Virginis, leaving them at point blank range of the two Mors class escorts that were accompanying the six other hive ships.  The survey ships immediately sent off a contact report, while the sensor buoy sitting just off the jump point sent off a contact report to the rest of the system. 

Once the survey ships jumped out, the hive ships broke into two groups, neither of which seemed to be headed anywhere in particular. 

August 22, 2153
The 1st Expeditionary Fleet has returned to Terra to honors and acclaim after destroying or scattering Hive Fleet Kraken.  The fleet’s ships have gone into a much-needed overhaul cycle, while the navy begins planning its next move to pacify the frontier. 

September 13, 2153
A survey ship operating in the Xi Bootis system, on the Hive Fleet Kraken frontier, two jumps beyond 111 Virginis, came under fire when approaching the third planet of the secondary star of the system.  The ship was rapidly destroyed by ground fire from Reaper batteries on the planetary surface, having barely enough time to get a warning out to the other ships in the system.  The other survey ships in the system immediately turned for the jump point out of the system. 

The destruction of the survey ship is alarming, for obvious reasons, but when news reaches Terra it will infuriate the admiralty.  After the initial contact with the Reapers, the Admiralty had instituted a requirement for all survey ships to probe planets with an oxygen-nitrogen atmosphere with automated sensor probes, and all survey ships had been refitted to allow them to do just that.  For some reason the survey ship in the Xi Bootis system failed to perform that step before approaching the planet. 

Xi Bootis system
Primary: G8-V Yellow Star
2xTerrestrial – one has a thin C02-Nitrogen atmosphere, the other is Venusian.
3xDwarf
1xSuper Jovian with 23 moons

Secondary: K4-V Orange star
5xTerrestrial with 4 moons, 2x Venusian, 1 with an oxygen-nitrogen atmosphere
1xDwarf with 2 moons
2xGas Giants with 49 moons

September 25, 2153
A survey ship from the 1st LR Survey Group jumps into the 111 Virginis system and dispatches a Reaper Contact report to the courier network ship on the jump point back to the Empire.  The report will reach Terra in nineteen hours. 

September 26, 2153
The Reaper contact report arrives on Terra.  In response, the Imperial Fleet begins organizing an expedition to Xi Bootis system, and requests Marine and Army support. 

The 1st Expeditionary Fleet is still in overhaul, so the ships will have to be drawn from the system defense fleet.  After much wrangling, the Xi Bootis Expeditionary Fleet will consist of 2xCVA, 3xBC, 4xDD, 5xDDG, 3xDDE, 60xStrikefighter, 4xAegis sensor fighters.  Support units will join the fleet en route. 

The ground contingent will consist of the 5th, 3rd, and 29th Marine Divisions, over five hundred thousand tons of ground force, bolstered by artillery and heavy armor attachments.  The ground transports will have to follow behind the fleet, as they will take time to load and are slower than the fleet’s warships. 

October 6, 2153
The ill-fated 1st LR Survey Group jumps into the 63 Hydrae system, adjacent to the 111 Virginis system, to probe the two jump points detected by an earlier survey.  Shortly after jumping into the system, they come under fire from the two Mors class ships detected earlier, last seen in 111 Virginis.  The survey ships run from the jump point as they will not be able to jump out for some time. 

It soon becomes clear that the hive ships are running from the jump point as well, so the survey ships turn back to jump back to the 111 Virginis system, all except for the lead ship which had lost its jump drive when it was targeted entering the system. 

October 25, 2153
The Xi Bootis Expeditionary Force has arrived in the 111 Virginis system and refueled from a waiting tanker group.  With that complete, Commodore Gabehart orders his force to proceed to the jump point to 63 Hydrae to determine if the Hive Fleet Kraken ships that attacked the survey group are still present.   

October 26, 2153
The Xi Bootis Expeditionary Force arrives at its assembly point two million kilometers from the jump point.  There is no sign of the hive ships, so Commodore Gabehart orders his force to divide into two groups.  His two assault carriers will jump through to the far side of the jump point, while his battlecruisers and destroyers will wait on this side of the jump point.  His DDG’s and DDE’s will wait at the assembly point. 

When the two assault carriers jump through to the 63 Hydrae system, they find the eight hive ships sitting just off of the jump point.  The assault carriers materialized 350,000 kilometers from the jump point, so they are just within range of their lasers.  The human ships turn towards the hive ships and begin moving back towards them and the jump point.  As expected, the hive ships run to the jump point and jump to the 111 Virginis system.  Right into the sights of three battlecruisers and four destroyers. 

The Terran warships gutted the Mors class escorts as they came through the jump point, and then turned their fire on the Camazotz class ships, which were clearly civilian ships of some sort, as they had never been observed to fire on any human ship.  Although they carried significant armor, all six Camazotz ships were destroyed in short order.  The fleet reassembled and then set course for the jump point to the 100 Ceti system. 

November 15, 2153
A survey ship working in the EQ Pegasi system discovers a ruined colony on the only planet of the system, a terrestrial world with an oxygen-nitrogen atmosphere, a little hot but otherwise ready for colonization without any terraforming.  EQ Pegasi is on the Hive Fleet Kraken frontier, three jumps from 111 Virginis.  This planet was probed for Reaper presence before the survey ship came near, and this time no Reapers were found, in spite of the ruins. 

November 24, 2153
The Xi Bootis Expeditionary Force has reached its observation point five million kilometers from Xi Bootis B-III.  The ship’s sensors detect a ground force present on the planet, but no ships.  After observing for a short time, Commodore Gabehart orders his force to close to 1,000,000 kilometer’s range. 

When the Terran ships reach one million kilometers, their sensors reveal the presence of an active sensor on the planet, but no additional information.  Commodore Gabehart orders his assault carriers and his battlecruisers to move to just within laser range of the planet, leaving behind his carriers and destroyers to wait out of range. 

When the big Terran ships reach firing range they begin bombarding the ground force targets with their heavy lasers.  At that range their chance of hitting anything is small, so Commodore Gabehart orders his ships to close to 200,000 kilometers range.  Reaper STO units begin firing on the oncoming ships as they close, and the Eternal Crusader begins taking damage to her shields.  However, the unmasking of the STO’s allows the Terran units to target them instead of random ground units.  While their chance of hitting has increase, Commodore Gabehart is still unhappy with their low accuracy, so he orders his ships to close to 100,000 kilometers. 

The Terran ships continue to fire as they close, but their accuracy is still lacking.  As no new STO’s have opened fire, Commodore Gabehart orders his ships to close to point blank range.  The STO’s opened up with everything they had as the Terran ships closed, including numerous gauss cannon point defense units, but they were barely able to scratch the shields of the big assault carriers.  The five Terran capital ships hovered over the planet and poured fire into the Reaper base, pounding it mercilessly with continuous laser fire.  It took several minutes of laser bombardment to eliminate the STO’s, but it was a forgone conclusion.  The Eternal Crusader’s shields never dropped below 95% during the bombardment, although the three battlecruisers reduced their maintenance stocks to an average of 79% before they were done.  With the threat eliminated, Commodore Gabehart sent a message to the courier at the jump point to signal the ground forces that the way was clear.  It would still take some time for them to arrive, as their transports were much slower than the fleet’s warships.  In the meantime, the survey command would be free to finish their survey of the system. 

Later that same day, a survey ship operating in the EQ Pegasi system (Hive Fleet Kraken frontier), probed a new jump point and discovered that it linked to a known system several jumps from Chi Draconis in the Leviathan frontier. 

November 29, 2153
Another survey ship working in the EQ Pegasi system probes another new jump point and finds itself in the 6 Centauri system, which is located on the frontier beyond Shield Base in the Monoceri system. 

December 11, 2153
The 1st Expeditionary Fleet’s ships have completed their overhauls and been transferred to Sol System Command.  With the ships freed up, a new expeditionary unit is put together to purge the remaining Hive Fleet Leviathan ships beyond Omicron Tucanae.  The new force is designated as the Hive Fleet Leviathan Expeditionary Force, and it consists of one dreadnought, one battleship, two battlecruisers, four missile cruisers, five missile destroyers, two destroyers, four destroyer escorts, a scout, and the dreadnought’s embarked fighters.    The force departs on this date, bound for the forward base in the Chi Draconis system. 

January 5, 2154
A survey ship working in the Kappa Ceti system, in the Hive Fleet Kraken frontier, three jumps from 111 Virginis system, had launched a sensor drone towards the system’s third planet some time ago.  At 1659 hours, the sensor drone bus reached the third planet, but before it could deploy its sensor buoy it was destroyed by a nuclear detonation. 

With the destruction of the sensor drone, the survey ship jumps out to report the contact. 

January 10, 2154
The 2nd LR Survey Group, working in the Xi Bootis system after it was cleared by the navy, discovers an ancient construct and ruins on the planet occupied by the Reapers.  In addition, the planet has massive deposits of eight TN resources at good availability levels, including gallicite, stocks of which have been shrinking. 

January 16,2 154
The contact report concerning possible Reaper presence in the Kappa Ceti system reaches the Xi Bootis Expeditionary Force.  As the ground force is still over two and a half months away, Commodore Gabehart decides to probe Kappa Ceti to determine the extent of the problem.  His expeditionary force sets out for Kappa Ceti on this date. 

February 7, 2154
Survey ships operating in the GJ 2097 system, on the Hive Fleet Kraken frontier, two jumps beyond 111 Virginis, discover a previously unknown alien race on the system’s second planet when the sensor bus deployed by one of the survey ships entered orbit of the planet and deployed its buoy.  The buoy immediately detected a small, outpost sized alien population on the planet, which was terrestrial and boasted an oxygen-nitrogen atmosphere and temperate climate.  The survey ships began their survey effort while a single ship returned to 111 Virginis to report the contact. 

February 24, 2154
The Xi Bootis Expeditionary Force had entered the Kappa Ceti system, location of the presumed Reaper infestation, several days ago and was headed inwards, towards the third planet.  It was still 2.3 days away when the fleet scout assigned to the expeditionary force detected a Reaper Charlie class ship 235 mkm’s ahead of the Terran ships.  The Charlie class had been encountered before, had a known speed of 8,03 km/s, and although its purpose was unknown it was known to mount a decoy missile launcher.  As the Reaper ship was faster than the Terran ships it could evade the expeditionary force, but it couldn’t run from the Terran fighters.  Commodore Gabehart ordered his force to continue on course towards the planet, curious what the Reaper ship would do. 

After closing for a bit, the Reaper ship turned and started running ahead of the Terran force.  Commodore Gabehart, after consulting with his staff, orders his assault carriers to launch their fighters and destroy the Reaper ship before it can join with other ships at the target.  Shortly after the fighters move away the Reaper ship turns back towards the Terran force and begins closing.  Shortly after that it turns and begins running again. 

At 0149 hours on the 25th, twelve of the sixty fighters launch their Sparrow IIb missiles at 2,000,000 million kilometers range, for a total of ninety-six missiles.  The missiles take forty-five seconds to reach their target and completely overwhelm it, destroying the Charlie in the first pass.  The fighters return to their carriers to rearm. 

Five hours later, when the fleet reached 1.3 billion kilometers from the third planet, the scout’s sensors detected a Reaper fleet closing on the Terran force.  The fleet consisted of six ships, four Deltas, an India, and a new class designated as the Ability class.  Deltas were 26,089 ton offensive missile launching ships, the India was a 17,399 ton defensive missile launching ship, and the Ability was 17,370 tons but otherwise unknown.  The Reaper fleet was just under the maximum range of the Terran scout’s sensors, 400 million kilometers, and closing at 5,333 km/s, which was fortunately below the Terran fleet’s speed of 7,500 km/s.  Once again Commodore Gabehart orders his fighters to launch. 

The sixty Eagle strike fighters raced away from the Terran expeditionary force at their maximum speed of 19,289 km/s while the expeditionary force came to a halt behind them.  When the fighters reached the limit of their escorting Aegis sensor fighter’s active sensors, two additional contacts appeared in close proximity to the Ability class unit, which was leading the other five units by 9.5 mkm’s.  The two new units were Golf class ships, each 8,689 tons and known to mount gauss cannons.  As the fighter’s primary target was the four Delta class ships, the strike commander, Lt. Commander Leota Stach ordered her fighters to detour around the lead force. 

The Terran fighters turned and began moving to the side, while the Reaper ships continued on their course towards the Terran ships.  Once the fighters reached their waypoint seven mkm’s to the side of the Reaper’s course they waited for the Reaper fleet to pass.  Shortly after reaching their waypoint three new contacts appeared trailing eight million kilometers behind the main force, all Foxtrot class ships.  Foxtrots are 8,691 ton ships with heavy particle beam weaponry, and are dangerous close-in combatants. 

One minute later the Reaper fleet grew again, as a single Golf class escort appeared with the main force and two Golf’s appeared with the trailing Foxtrot units.  Lt. Commander Stach waits another eight minutes and then orders her fighters to begin their attack run on the main Reaper force.  The Terran fighters close and the Reaper ships continue on their course until the fighters reach fifteen million kilometers, at which time the Reaper main group and the trailing force turns towards the fighters, while the lead group continues on towards the Expeditionary force. 

Eight minutes later, at near their maximum range of three million kilometers, the Terran fighters launch their missiles.  The Strike planners had no idea what the Reaper’s missile capability would be against the fighters, so they had decided on the maximum range strike as the safest approach.  The sixty fighters concentrated all of their missiles on the four Delta class offensive missile units, as they were the primary threat to the fleet.  Here, the strike planners had been divided.  Previous experience had shown that it was a better allocation of their missiles to eliminate anti-missile escorts first, allowing a later strike to finish off the unprotected offensive ships, but the bulk of the planners felt that the Sparrow IIb missiles, with their improved ECCM and ATG, along with their heavier warheads, would allow them to penetrate the Reaper’s defenses and eliminate the primary targets, leaving the escorts with nothing to protect. 

The four hundred and eighty missiles raced away from the fighters, towards the Reaper force, while the fighters turned away to maintain the range.  Reaper AAM’s began intercepting the missiles 678,000 kilometers from the Reaper force.  Sixteen Sparrow IIb ASM’s were stopped short of the Reaper force by the AMM’s, and then the Terran missiles closed to attack range.  The first attack by the missiles destroyed three of the Delta’s outright, and heavily damaged the fourth.  Point defense fire only took out a relative few of the attacking missiles, but did manage to take out the few missiles that survived the first attack as they came around to attack again.  The strike was a success, with three of the Deltas destroyed and the fourth crippled and reduced to 889 km/s. 

The fighters turned back to their waypoint to the side of the Reaper fleet, and then set out for their carriers, their job done.  The long-range missile threat from the Reaper force was eliminated.  The remaining ships of the main force tried to pursue the fighters, while the lead Reaper force continued on towards the Terran expeditionary force, and the trailing group, along with the damaged Delta, turned back.    After a short period, the lead group turned back as well, followed shortly thereafter by the remnants of the main force.  Shortly after the fighters left the Reaper ship’s detection range, they all turned back towards the Terran force and began closing again, except for the crippled Delta.         

Four hours later the fighters landed on their carriers and Commodore Gabehart ordered his force to close on the oncoming Reaper force, the lead unit of which was now 180 mkm’s away and closing.  As the two forces close on each other, the Terran scout detected a Charlie class ship closing on the damaged Delta from the inner system. 

When the Reaper ships reach 72 mkm’s from the Terran force they turn away and begin running for the inner system, all except the two remaining ships of the main force, which continue to close.  At 2213 hours the India and Golf class units are 27 mkm’s from the Terran force, and Commodore Gabehart orders his DDG’s to engage the oncoming Reaper ships.  The Terran Absolution class DDG’s are armed with forty-two box launchers equipped with the Archer III ASM.  The Archer III has a speed of 35,000 km/s, second generation ECCM and ATG, a range of 30 mkm’s, and a warhead 50% more powerful than the Sparrow IIb’s carried by the fighters.  In addition, the Archer III carries two decoys to help it penetrate fleet defenses.  The lead DDG, the Amnesty, launches twenty-five Archer III ASM’s in response, targeted on the two closing Reaper warships. 

Reaper interceptor missiles began attacking the missile wave when it reached five hundred and sixty-five thousand kilometers from the Reaper force.  For the most part they expended themselves on decoys, but two missiles were destroyed by the AMM’s in the first attack.  Three more missiles were destroyed, and twenty-five of the decoys, before the missiles reached attack range.  Only two missiles penetrated the point defense fire and the ship’s decoys to hit the Golf class escort, expending themselves against the ship’s shields.  Eight missiles survived to hit the India class ship’s shields, and another hit its armor but didn’t penetrate. 

For the next attack, two of the Amnesty’s sister ships launch a total of fifty missiles at the two oncoming Reaper ships at twenty-five million kilometers.  Once again, the interceptions began around 550,000 kilometers. This time the Reapers took out thirteen missiles before they reached attack range.  The India class had its shields stripped again, and took five armor hits, but none penetrated, but the Golf class took a penetrating hit that left it drifting, leaving the India to proceed on its own. 

The third attack consisted of forty Archer III ASM’s, all targeted on the India class ship.  Nineteen of the forty hit the India, stripping her shields again and getting seven penetrating hits, reducing her speed to 2,666 km/s.   

Commodore Gabehart decides that the two Reaper ships have been reduced to irrelevance and orders his fleet to close on them to beam range.  The India doggedly continues to close and managed to get several salvoes of missiles off at the Terran force before the Angel of Retribution’s heavy lasers swatted it from space.  Between the fleet’s point defense and the CVA’s heavy shields the India failed to inflict any damage.  The Terran force set its course for the planet again.  One shot with one of the Angel of Retribution’s 30cm soft X-ray lasers took the crippled Golf class out as the force advanced on the planet. 

In the meantime, the two other Reaper squadrons had turned and were closing on the Terran force, but later turned away. 

February 26, 2154
At 1234 hours, the Terran force picked up a missile salvo of twenty-six missiles closing on their position, apparently launched from the crippled Delta which was now 27 mkm’s away.  Commodore Gabehart decided to avoid wasting any more missiles on the Delta and ride out the attack.  The three DDE’s escorting the capital ships moved forward and prepared to engage, while the rest of the ships ready their point defense weapons. 

The Reaper missiles streaked towards the oncoming Terran ships at 30,085 km/s, while the Delta still limped along at 889 km/s, 30 mkm’s from the Terran fleet and closing.  When the incoming missiles reached three million kilometers AMM’s began racing away from the DDE’s.  The Terran AMM’s were almost three times as fast as the incoming missiles, and they sped away from their DDE’s as if eager to reach their targets.  A second salvo of fifteen AMM’s was launched ten seconds later, followed shortly by a third. 

The first wave of AMM’s only got three hits, two of which were decoys.  The second got seven hits, but again only one was a real missile.  A steady stream of AMM’s raced away from the defending DDE’s as the Reaper missile wave closed, stripping away the decoys.  In the meantime, a second missile wave had appeared on the Terran ship’s sensors, but this missile wave was only composed of eleven missiles. 

By the time the incoming missile salvo reached laser range of the Terran force, it was reduced to seven missiles.  Four more missiles were destroyed by the AMM’s, one more was taken out by last ditch laser fire, and two hit the armor of the DD Wei Zhao, causing minor damage to its armor belt. 

The DDE’s began launching again when the second missile salvo reached three mkm’s range.  Only one missile from the second wave got close, but it was finally shot down by an AMM just 80,000 kilometers short of the fleet.  Space was clear around the expeditionary force again. 

The Terran force chased down the slowly fleeing Delta, and once within range of its lasers, took out the Reaper ship with a single shot from the Angel of Retribution’s spinal laser. 

The next closest group of ships was the Ability class cruiser and its two Golf class escorts.  They were running for the planet at 5,340 km/s, and were sixty-two million kilometers from the expeditionary force.  The other group, composed of three Foxtrots and two Golf’s, was also headed towards the planet and was twenty-four million kilometers farther away than the first group.  Commodore Gabehart ordered his ships to chase them down. 

At 1732 hours the fleet scout attached to the expeditionary force detected two Alpha’s and two Bravo class units orbiting the third planet.  These have been encountered before, and are immobile bases used to protect Reaper anchorages.  The Bravos carry numerous small missile launchers, while the Alphas are suspected to be point defense bases, and possibly beam combatants.  Commodore Gabehart launches his fighters and orders them to close on the suspected Reaper base on the third planet while the expeditionary force continues to chase the Reaper ships. 

February 28, 2154, 0108 hours
The fighters are now within range of the sensors on the Aegis sensor fighters, and they pick up twelve Golf class and a Charlie orbiting the planet, along with the four bases.  The Golf class are small missile combatants, while the Charlie is a beam combatant. 

0144 hours
The fighters are now in their launch position, 1.75 mkm’s from the planet.  The sixty Eagle fighters launch their missiles, eight Sparrow IIb ASM’s each, targeting the four bases and the Golf class fast missile ships.  Twenty seconds later interceptions start, and sixty-eight missiles are destroyed short of the planet.  One hundred and twenty-two are destroyed by point defense fire, and two hundred and fifty-eight hit their targets.  Eight Golf class ships are destroyed outright, and the other four suffered several penetrating hits each.  The missiles were less successful against the bases.  All four bases carried decoy missiles, and succeeded in decoying eighty-six missiles.  Two of the bases suffered two penetrating hits, one suffered one penetrating hit, and one escaped unscathed.  Their missiles expended, the Terran fighters turned back towards their carriers to rearm. 

As the chase grinds on, the closer Reaper force suddenly turned towards the Terran expeditionary force and begins closing.  It quickly turns away again, but the range dropped precipitously for a period of time. 

At 0703 hours the Terran ships drew into range of their lasers and opened fire, with the CVA’s and the BC’s focusing on the Ability class, while the DD’s concentrated on the two Golf class units.  The first hits were low powered and few in number, due to the range, but as the range dropped their accuracy increased, as did the power of the lasers.  When the Terran ships reached 237,000 kilometers the fleeing Reaper ships began returning fire, hitting the Angel of Retribution with several energy weapons that barely scratched her shields. 

The next laser salvo from the Terran ships dropped the Ability’s shields and scored hits on her armor, several of which penetrated.  After several more lasers penetrated her armor, the Ability’s speed began dropping.  With the Ability reduced to 4,000 km/s, the two Golf class units turned back towards the Terran ships and suddenly raced towards them, closing rapidly.  Commodore Gabehart ordered his turreted weapons to focus on the Golf’s, along with the BC’s plasma cannons, which had so far remained silent, to augment the destroyer’s firepower. 

The plasma cannon fire, along with the increased laser fire, stripped the Golf’s remaining shields and shredded their armor, with one suffering a penetrating hit.  The next salvo, at 73,000 kilometers, holed both Golfs, leaving one drifting and the other barely underway.  Two more salvoes and the Golf’s were reduced to wrecks, leaving only the Ability.  One more round of fire from the capital ship’s heavy lasers put paid to the Ability, which had been vainly trying to close the distance. 

With the second group of Reaper ships eliminated, Commodore Gabehart ordered his force to run down the third and last mobile force. 

At 1047 hours the Terran expeditionary force had closed to twenty-eight million kilometers from the third planet and detects a ground force on the planet’s surface.  The third mobile force is now nine million kilometers from the advancing Terran force.  Commodore Gabehart ordered his DDG’s to launch a strike with their remaining Archer III ASM’s against the bases in orbit over the planet.  Seconds later the three DDG’s with missiles left were wreathed in fire and smoke as ninety-five ASM’s left their launchers bound for the planet.  Five minutes later the missiles raced past the last Reaper mobile force on their way to the planet, passing 320,000 kilometers from the ships.  Forty seconds later the active sensors on the missiles picked up nine Reaper missiles out-bound, headed for the fleet. 

As the Reaper missiles approached the fleet the DDE’s went into action again, spewing AMM’s ahead of the capital ships.  Once again, the missiles were stopped short of the fleet.  Reaper AMM’s reduced the Terran missile wave to fifty-six as they closed, and then point defense took a massive toll of the large Terran missiles, leaving only nineteen to hit the two Bravo class bases, neither of which lost their shields. 

Not wishing to face massive waves of small missiles from the two Bravo class bases, Commodore Gabehart authorizes one more strike by the fighters with the last of the expeditionary force’s fighter missiles.  The fighters launch and streak towards the planet shortly thereafter. 

Even as the fighters race towards the planet and its orbiting bases, the third mobile group turns back towards the Terran expeditionary force and races towards it, closing rapidly.  Commodore Gabehart assigns each of his capital ships to target each of the oncoming Reaper small ships, with his destroyers each picking a target as well. 

As the two groups closed the Reaper ships turned away while still out of range, forcing the Terrans into a chase again.  In the meantime, the fighters had reached their launch point and sent their missiles towards the orbiting bases.  All of the fighter’s missiles were targeted on the two Bravo class missile bases, in an attempt to overwhelm them.    As before the Reaper AMM’s began intercepting the fighter’s missiles short of their target, and then a veritable storm of point defense fire tore massive holes in the missile wave, but with two hundred and forty missiles targeted on the two bases there was just no way the Reapers could stop all of them, and the two missile bases disappeared in a series of massive explosions, leaving two point defense bases, a Charlie class beam combatant, and four Golf class escorts orbiting the planet. 

Five minutes later the Terran expeditionary force drew into range of the mobile group and opened fire on the Reaper combatants.  As before the hits were few and low power at long range, serving only to attrit the Reaper ship’s shields, but they increased in power and number as the range dropped.  When the range reached 200,000 kilometers the Terran ships turned to maintain the range just as their fire took down one of the Reaper ship’s shields.  So far, the Reaper ships had not got a shot off at the Terran fleet.  Soon after that the Terran lasers began penetrating the Reaper ship’s armor. 

One by one the Reaper ships were destroyed by the sustained laser fire.  One managed to get close enough to fire its particle lance at a Terran destroyer.  Fortunately, this was a Hero Flight IVd type destroyer, with the latest shields.  The Reaper particle beam took the DD’s shields down, but only scratched her armor.  It took time for the Terran ships to reduce the Reapers to scrap, but Commodore Gabehart was perfectly willing to take the time to do the job right. 

When the last Reaper ship blew up under sustained laser fire, Commodore Gabehart ordered his fleet forward, towards the planet and its remaining defenders.  Fourteen minutes later the fleet came to rest three million kilometers from the planet. 

After holding station for a short period of time, Commodore Gabehart ordered the fleet forward.  The fleet’s sensors still showed a considerable ground force contact on the planet, two Alpha class point defense bases, a Charlie class beam cruiser, and four Golf class small missile ships.  The priority target for the Terran ships would be the two point defense bases, and then the Charlie class cruiser. 

As before, the Terran ships opened fire when they came into range, at 384,000 kilometers, but this time they were all targeting the same Alpha class base.  The hits started becoming more powerful, and more common, as the fleet closed, but Commodore Gabehart ordered them to come to a halt at 300,000 kilometers.  At this range the Terran ships could engage with all of their lasers, and it appeared that the Reapers could not reach them. 

Unfortunately, the Terran weapons weren’t getting enough hits or doing enough damage to get through the Reaper’s shield in a reasonable amount of time, so Commodore Gabehart ordered his ships to close to 250,000 kilometers, and then 200,000 when that didn’t increase their effectiveness enough.  At 212,000 kilometers range the Angel of Retribution and the Eternal Crusader were attacked by twelve powerful ground-based particle weapons each, but fortunately most missed and the Eternal Crusader only took one hit to her shields.  The Terran ships were apparently still too far out to determine which ground units were attacking his ships, so Commodore Gabehart ordered his ships to move back to 250,000 kilometers and to bombard the enemy fleet from there.  Even as the Terran ships moved away, they finally penetrated their target’s shields.  They almost immediately began getting penetrating hits on the base.  It didn’t take long for the base to succumb to the sustained laser fire, at which time the Terran ships shifted to target the second Alpha class unit. 

The long-range laser bombardment soon wore through the base’s shields, and then its armor.  Soon it joined its fellow base as wreckage orbiting the planet.  The fleet then shifted fire to the Charlie class cruiser, and then took out the Golf’s one by one.  Once they were gone, the fleet shifted fire to the STO’s that had revealed themselves. 

After several minutes pounding the planet, Commodore Gabehart called a halt to the bombardment.  The chances of hitting the STO’s was too small, and the wear and tear on his ships was beginning to be a problem.  They had destroyed all of the Reaper mobile forces in the system, and the planet lay open to invasion when the ground forces arrived.  It was time to withdraw.  The Terran expeditionary force turned towards the jump point out of the system, on course to rejoin the tankers and supply ships in the 111 Virginis system. 
30
General C# Fiction / Re: AAR: The Dawn of the Second Era
« Last post by jahwillprovide on December 02, 2024, 02:12:56 PM »
United Earth Federation Timeline: 2075–2076
A Chronicle of Perseverance and Expansion

January 1, 2075
 The production timeline for a full ground combat company is approximately 2.5 years, with plans to field five companies initially. However, troop transports remain on hold due to critical Gallicite shortages. Stockpiles must first be replenished to refit existing ships and complete the vital Jump Tenders.



January 10, 2075
 Advancements in shield recharge technology are implemented into the Jaffa II-class vessels before their completion. Research has shifted toward sector command logistics, with plans to deploy construction facilities to Little Rose and Sagan Prime. These colonies aim to achieve self-sufficiency and support orbiting fleets in the near future.

January 16, 2075
 Freighters have returned with 2,300 tons of Gallicite, a third of the total required for the planned ship refits and Jump Tender production. While this is a positive step, the resource crisis persists.

January 31, 2075
 A gravitational survey of Tau Ceti has revealed no additional jump points. The search shifts back to Codalus, where the aliens must reside beyond an unexplored jump point.

February 6, 2075
 Three stabilized jump points are uncovered in the Orphicon System, possibly leading to new alien civilizations. A Beta-class exploration ship will be dispatched post-overhaul to investigate.

April 2075
 Diplomatic shipyards begin upgrades to support the Beta II-class, with advanced engines and Jump Drive technology. These upgrades will increase their range from 42 billion km to an impressive 106 billion km.

February 12, 2075
 New particle beam research offers incremental upgrades, though practical implementation must wait for Gallicite stockpiles to recover. Microwave and particle weapon-equipped frigates are slated for the future once resources allow.

March 17, 2075
The Alexandria II-class vessels have completed extensive engine and sensor package refits, marking a significant milestone in the United Earth Federation fleet’s development. For 15 years, the venerable Alexandria I-class ships have stood as a backbone of the fleet, their reliability and firepower serving as key assets in numerous engagements. Now, with the transition to the Alexandria II design, these ships are poised to continue their legacy with cutting-edge enhancements.

The refits include advanced engines, providing a substantial boost to speed and maneuverability. This upgrade enables the Alexandrias to close the distance to targets more effectively and reposition in battle with greater agility.

However, the most transformative improvement lies in their sensor packages. The new systems represent a quantum leap in tracking technology, allowing the Alexandria II-class to detect and lock onto hostile targets with unprecedented precision. This upgrade not only enhances their long-range strike capabilities but also significantly improves their effectiveness as command-and-control vessels during fleet engagements.

For the crews who have served aboard the Alexandrias since their inception, the transition to the Alexandria II is a moment of pride and renewal. Commodore Jacques Bonald, addressing the fleet upon the completion of the first Alexandria II, remarked, “These ships have carried us through the darkest moments of our expansion, and now, they are reborn to face the challenges of tomorrow. The Alexandria-class is not just a ship—it is a symbol of our resolve and ingenuity.”

As the Alexandria II-class takes to the stars, its enhanced capabilities will ensure that it remains a cornerstone of the UEF fleet, ready to confront any threat that arises in humanity’s relentless journey into the unknown.

Code: [Select]
Alexandria II B class Light Cruiser      18,000 tons       500 Crew       3,000.3 BP       TCS 360    TH 2,700    EM 0
7500 km/s    JR 3-50      Armour 6-61       Shields 0-0       HTK 101      Sensors 16/16/0/0      DCR 15-8      PPV 64
Maint Life 3.32 Years     MSP 3,112    AFR 173%    IFR 2.4%    1YR 427    5YR 6,399    Max Repair 675 MSP
Magazine 664 / 0   
Commander    Control Rating 1   BRG   
Intended Deployment Time: 6 months    Morale Check Required   

MK II Cruiser Jump Drive     Max Ship Size 18000 tons    Distance 50k km     Squadron Size 3

MK II Alexandria Engine (2)    Power 2700    Fuel Use 51.96%    Signature 1350    Explosion 15%
Fuel Capacity 2,878,000 Litres    Range 55.4 billion km (85 days at full power)

Size 8.00 Missile Launcher (8)     Missile Size: 8    Rate of Fire 45
MK II Cruiser MFC (1)     Range 34.5m km    Resolution 120
Wasp Anti-Ship Missile MKIII (83)    Speed: 22,525 km/s    End: 29.6m     Range: 39.9m km    WH: 18.802    Size: 8    TH: 75/45/22

MK II Cruiser ASS (1)     GPS 1920     Range 31.5m km    Resolution 120
MK II Thermal Sensor 100T (1)     Sensitivity 16     Detect Sig Strength 1000:  31.6m km
MK II EM Sensor 100T (1)     Sensitivity 16     Detect Sig Strength 1000:  31.6m km

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
This design is classed as a Warship for auto-assignment purposes

April 20, 2075
 The Jaffa II-class ships have been completed. With the Jump Tenders a year away, sensor package upgrades have begun for improved missile defense.

May 6, 2075
 A new stabilized jump point has been discovered in Codalus, likely leading to the Tau Ceti Alien’s home system. Survey efforts are redoubling in this area.

May 14, 2075
 The Jaffa II B-class vessels have successfully launched. These upgraded ships bring enhanced EM/Thermal sensors and their own missile tracking sensor.

Code: [Select]
Jaffa II B class Battlecruiser      36,000 tons       963 Crew       6,855 BP       TCS 720    TH 5,400    EM 3,120
7500 km/s      Armour 15-97       Shields 104-325       HTK 169      Sensors 0/0/0/0      DCR 18-5      PPV 156
Maint Life 1.68 Years     MSP 4,142    AFR 576%    IFR 8.0%    1YR 1,750    5YR 26,247    Max Repair 900 MSP
Troop Capacity 500 tons     Boarding Capable   
Commander    Control Rating 2   BRG   AUX   
Intended Deployment Time: 6 months    Morale Check Required   

MK I Battlecruiser Engine (3)    Power 5400    Fuel Use 45.00%    Signature 1800    Explosion 15%
Fuel Capacity 4,760,500 Litres    Range 52.9 billion km (81 days at full power)
MK II Battlecruiser Shields (4)     Recharge Time 325 seconds (0.3 per second)

MK II Battlecruiser Laser (20)    Range 192,000km     TS: 7,500 km/s     Power 6-4     RM 40,000 km    ROF 10       
MK III Battlecruiser Railgun (8x4)    Range 160,000km     TS: 7,500 km/s     Power 12-4     RM 40,000 km    ROF 15       
MK II Battlecruiser Laser BFC (1)     Max Range: 192,000 km   TS: 6,000 km/s    ECCM-0     95 90 84 79 74 69 64 58 53 48
MK I Battlecruiser Rail BFC (1)     Max Range: 168,000 km   TS: 6,000 km/s    ECCM-0     94 88 82 76 70 64 58 52 46 40
MK II Battlecruiser Reactor (3)     Total Power Output 113.9    Exp 10%

MK II Capital Ship Sensor (1)     GPS 19200     Range 99.6m km    Resolution 120
MK II Missile Tracker (1)     GPS 2     Range 2m km    MCR 181.7k km    Resolution 1

Ground Forces
1x Naval Boarding

This design is classed as a Military Vessel for maintenance purposes
This design is classed as a Warship for auto-assignment purposes

June 26, 2075
 The first Beta II-class vessel is ready and dispatched to Codalus to explore the newly stabilized jump point. The journey will take over 100 days.

July 13, 2075
 The Red II-class ships are rolling out of refit, with the last two expected to finish alongside the Broadsword Jump Tenders. They now wield the same railguns as our Jaffas and can perforate ship hulls out to 168,000 km.

September 18, 2075
 Beta II B 001 arrives in Codalus, while Beta II B 002 finishes its refit and sets course for Orphicon to explore its three stabilized jump points.

October 10, 2075
Beta II B 001 crosses through the stabilized jump point, uncovering the Niven system—a colossal expanse dominated by a black hole at its core, stretching nearly 50 billion kilometers across. The system’s sheer size and the intense gravitational forces emanating from the black hole promise a daunting and complex survey operation.

Adding to the intrigue, sensors detect the wreckage of an enormous vessel, approximately 110,000 tons in displacement. The ship’s design is unfamiliar, bearing no resemblance to any known alien factions encountered by humanity thus far. Its ruined state suggests a violent end, possibly from combat or the system’s harsh gravitational forces.

The discovery raises more questions than answers: Who built this colossal vessel, and what brought it to such a catastrophic fate? The Beta II crew marks the site for closer investigation, though caution will be paramount given the black hole’s perilous pull.



October 28, 2075
 A third stabilized jump point is discovered in Codalus. Beta II B 001 will investigate, while a gravitational survey vessel begins probing Niven for additional stabilized points.

November 15, 2075
 The stabilized jump point in Codalus leads to the Lassa system, a small, planetless region. A survey vessel will investigate further for potential connections.

December 25, 2075
 The diplomatic vessel UEF Harmony and the gravitational survey ship UEF Pathfinder entered the Orphicon System, tasked with surveying its jump points and celestial bodies. While scanning the inner system, their sensors picked up an anomaly: a massive, slow-moving object. Closer analysis revealed it to be a freighter of alien origin, distinct from anything encountered before.
 The discovery brought operations to a halt. Crews aboard both ships stared at their screens in awe, realizing the implications of their find. For the first time, humanity had encountered a spacefaring civilization that didn’t immediately raise weapons or remain frustratingly silent like the Tau Ceti aliens. Unlike the hostile forces encountered before, this was the first time humanity's presence wasn’t met with aggression or indifference.
 As the freighter continued its journey, diplomatic protocols were activated. The UEF Harmony transmitted standardized first-contact greetings in multiple forms: mathematical sequences, cultural references, and encoded star maps showing Earth’s position. Hours passed with no response. Then, just as hope began to wane, the alien vessel transmitted an encoded reply. Its cadence and structure suggested an intentional communication effort rather than an automated response or warning.
 Back on Earth, the UEF government and the scientific community erupted with excitement. Experts worked around the clock to decipher the alien transmission, while the Harmony and Pathfinder shadowed the freighter at a safe distance. Every precaution was taken to avoid any appearance of hostility, ensuring the alien crew felt no threat from humanity's presence.
 This encounter marked a turning point for the United Earth Federation. After years of costly and devastating conflicts with the Sansibar aliens and the Mirage Coalition, and prolonged uncertainty regarding the Tau Ceti aliens, this event offered hope. For the first time, humanity glimpsed the possibility of peaceful coexistence—and perhaps even collaboration—with an alien civilization.

July 29, 2076
 Over seven months of painstaking work had passed since first contact in Orphicon. Linguistic teams on Earth and aboard the UEF Harmony had pieced together fragments of the alien language, aided by repeated transmissions and reciprocal exchanges of information. Finally, on this day, a breakthrough was achieved.
 The aliens identified themselves as the Marilith Empire, a sovereign interstellar civilization. Their message, once translated, conveyed a cautious but unmistakable tone of cooperation. While wary of humanity's expansionist tendencies, the Marilith Empire seemed eager to open channels of communication and trade, noting their own interest in rare minerals and advanced technologies.
 The UEF’s diplomatic corps wasted no time. Commodore Victoria Langford, commanding the Harmony, exchanged greetings with her Marilith counterpart—a rare honor in interstellar relations. The discussion touched on mutual goals, shared interests, and the vast unknowns of the galaxy.
 Initial reports from this exchange painted the Marilith as an advanced, hierarchical society with a rigid caste system and a focus on efficiency. Their freighter’s presence in Orphicon was part of a trade route, and they seemed keen to ensure humanity’s presence in the system would not disrupt their operations.
 This successful communication marked humanity’s first peaceful interstellar diplomatic exchange, contrasting sharply with the hostilities faced in Sansibar and Scorpia/Sagittaron. The prospect of an alliance with the Marilith Empire offered hope—not just for trade, but also for an ally in the struggles ahead.

August 18, 2076
The Sansibar Offensive begins. The fleet, now jump capable due to the addition of Broadsword-class Jump Tenders, set course for the system where hostile aliens struck down a UEF Surveyor 20 years prior. Avenging the fallen at Aerelon and securing the habitable planets in Sansibar is paramount.

Code: [Select]
Broadsword class Jump Tender      36,000 tons       398 Crew       2,978 BP       TCS 720    TH 5,400    EM 0
7500 km/s    JR 3-50      Armour 8-97       Shields 0-0       HTK 88      Sensors 0/0/0/0      DCR 1-0      PPV 0
MSP 51    Max Repair 600 MSP
Commander    Control Rating 1   BRG   
Intended Deployment Time: 12 months   

MK II Broadsword Jump Drive     Max Ship Size 36000 tons    Distance 50k km     Squadron Size 3

MK I Jump Tender Engine (6)    Power 5400    Fuel Use 2.36%    Signature 900    Explosion 5%
Fuel Capacity 1,150,000 Litres    Range 244 billion km (376 days at full power)
Refuelling Capability: 60,000 litres per hour     Complete Refuel 19 hours

This design is classed as a Commercial Vessel for maintenance purposes
This design is classed as a None for auto-assignment purposes

The Battle of Sansibar: September 4, 2076
Aboard the UEF Caesar, flagship of the United Earth Federation fleet, Commodore Jacques Bonald reviewed the sensor displays. Reports indicated four unidentified vessels near the fourth planet in the Sansibar system. Their missile volleys suggested the presence of [/b]enemy cruisers[/b], a logical assumption given the volume of firepower. The fleet—3 Jaffa-class Battlecruisers (including the UEF Caesar and UEF King George), 5 Alexandria-class Light Cruisers, 6 Anaconda-class Missile Defense Destroyers, and 5 Red-class escort Destroyers—adjusted its formation. The Alexandrias prepared for long-range missile strikes, the Anacondas set their defensive systems to full alert, and the Reds flanked the fleet to bolster point defense.
Phase One: Sensor Suppression and the Hidden Threat At 25 million kilometers, the Alexandrias fired their first salvo at the sensor-jamming vessel. Within moments, the jamming field collapsed as the ship was reduced to debris. However, the elimination of the jammer revealed a grim surprise: 16 additional vessels, previously hidden. Combined with the original four, 20 Death Slayer-class FACs emerged, their formations tight and aggressive. “What we mistook for cruisers were fast-attack craft,” Bonald muttered. “And now they’ve drawn us in.” The Death Slayers maintained a cautious orbit near Sansibar II, drawing the UEF fleet closer while their missile barrages focused on the UEF King George and UEF Caesar. The volume of incoming fire tested the fleet's defenses, but the Anacondas, Reds, and Jaffas worked in unison, creating a near-impenetrable shield of interception fire.



Phase Two: FAC Engagement At 14 million kilometers, the Death Slayers broke orbit, accelerating directly toward the UEF fleet. The Alexandrias and Anacondas launched coordinated salvos, prioritizing the most immediate threats. Despite the overwhelming speed and maneuverability of the FACs, the long-range missiles struck true, destroying several before the enemy could close the distance. Meanwhile, the FACs unleashed another devastating wave of missiles. Their concentrated fire succeeded in overwhelming the UEF King George’s shields. Several projectiles punched through its armored hull, causing structural damage, but the battlecruiser held firm and returned fire with unrelenting resolve. “King George reporting,” came the voice of its captain. “Armor breached, but we’re still in the fight.”
Phase Three: The Wrath of the Fleet As the FACs drew closer, the UEF fleet prepared for railgun and laser engagements. Sensing the danger, the remaining Death Slayers attempted to withdraw. The Alexandrias and Anacondas launched their final salvos, depleting their missile reserves in a desperate bid to neutralize the retreating vessels. One by one, the Death Slayers were annihilated, their evasive maneuvers unable to outpace the fleet's superior firepower. By the end of the engagement, 19 of the 20 FACs were destroyed. The sole survivor escaped into deep space, leaving the battlefield silent except for the faint echoes of victory. Aftermath The fleet regrouped, counting its successes and examining the damage. Despite taking heavy hits, no UEF ships were lost. The UEF King George was damaged but operational, its crew hailed as heroes for their resilience under fire.



On Sansibar II, the wreckage of enemy surface-to-orbit weapons (STOs) and Death Slayers served as a stark reminder of the price of resistance. Commodore Bonald addressed the fleet: “Today, we were tested. Today, we prevailed. Sansibar is ours—not by luck, but by the strength of our unity and the courage of our crews.” The Battle of Sansibar marked another milestone in humanity's relentless expansion, a victory that would inspire generations as the UEF continued its march across the stars.


September 15, 2076
 The fleet had successfully turned back the Sansibar Aliens, something previously thought impossible, thanks to coordination, new technology, and exceptional bravery. Yet, something darker lingered over the Federation. Despite this victory, the enigmatic Marilith Empire and other threats had set humanity on a new path: one that might lead to both peace and war.

December 8, 2076
 Terraforming efforts accelerate, with additional units deployed to Shayou II. Mars’ habitability project receives renewed focus, prioritizing atmospheric development over temperature control.

December 29, 2076
 The first Pentagon-class Troop Transports roll off the assembly line. They will soon be ready to deploy troops to secure Sansibar's habitable planets once enemy STOs are neutralized.


Overview of our Terraforming efforts









Pages: 1 2 [3] 4 5 ... 10
SMF spam blocked by CleanTalk