7 Dictators- Players

[Gidoran]

January 1, 1 Feudal Calendar
Standing Orders: Epsilon Indi
Issuing Officer: Adm. Mikhail Mikoyan, CO Sector Epsilon Indi

Order 1: Epsilon Indi-A II to be renamed "Harvest".
Order 2: Gravitational Survey Ships to continue survey of Epsilon Indi jump points.

- First Contact Protocols: Ships which establish contact with nonhuman sentient life forms are hereby required to avoid leading potentially hostile forces to Sol or any of her Colonies. Friendly contact will be attempted. If contact has been made with an alien civilization, all active battlegroups are to be mobilized and prepared for defense. Survey ships are not to return to Epsilon Indi or Sol if spotted, but are to find a secure sector to wait in while a battlegroup is mobilized to escort it home.

Order 3: Geological Survey Ships to prepare themselves to investigate potential worlds in discovered systems which have been classified BLUE/CLEAR, GREEN/SWEEP IN PROGRESS. Geological Survey may proceed in YELLOW/NO SWEEP only with an escort consisting of Two (2) Frigates and One (1) Destroyer. Under no circumstances is a survey to proceed in a RED/HOSTILE system.

Order 4: Diplomatic issues are to be held for Admiral Mikoyan or Vice Admiral <Admiral 666's Character>.
Order 5: In the event of a potential hostile fleet heading towards Epsilon Indi, Initiate Order BLACKJACK.
Order 6: In the event of Admiral Mikoyan being made unavailable for a significant period of time, command is delegated to Vice Admiral <Admiral 666's Character> until contact has been re-established.

Order 7: The following designs are to be broadcast back to Sol for use by all of Terra's Children at no cost.

Merchant-class Light Cargo Ship: Intended for support of Asteroid Mining Operations, and transportation of PDC components.

Code: [Select]

Merchant class Cargo Ship    9,000 tons     67 Crew     359 BP      TCS 180  TH 240  EM 0
1333 km/s     Armour 1-38     Shields 0-0     Sensors 1/1/0/0     Damage Control Rating 1     PPV 0
MSP 25    Max Repair 68 MSP
Intended Deployment Time: 3 months    Spare Berths 2    
Cargo 5000    Cargo Handling Multiplier 20    

CV120-0.8 Ion Commercial Drive (2)    Power 120    Fuel Use 6.07%    Signature 120    Exp 4%
Fuel Capacity 250,000 Litres    Range 82.4 billion km   (715 days at full power)

Indi Arms "TEMPLAR" CIWS-400 (1x8)    Range 1000 km     TS: 40000 km/s     ROF 5       Base 50% To Hit
GES-S1-R1 Small Threat Detection Array (1)     GPS 36     Range 2.2m km    Resolution 1
GES-S1-R160 Area Search Sensor (1)     GPS 5760     Range 27.3m km    Resolution 160

This design is classed as a Commercial Vessel for maintenance purposes
Hipflask-class Tanker: Small, cheap transport for fuel. Intended to support Gas Giant mining operations, and to support smaller fleets as part of the support train.

Code: [Select]

Hipflask class Tanker    9,000 tons     45 Crew     676 BP      TCS 180  TH 240  EM 0
1333 km/s     Armour 1-38     Shields 0-0     Sensors 1/1/0/0     Damage Control Rating 1     PPV 0
MSP 47    Max Repair 68 MSP
Intended Deployment Time: 3 months    Spare Berths 0    

CV120-0.8 Ion Commercial Drive (2)    Power 120    Fuel Use 6.07%    Signature 120    Exp 4%
Fuel Capacity 5,520,000 Litres    Range 1818.3 billion km   (15788 days at full power)

Indi Arms "TEMPLAR" CIWS-400 (1x8)    Range 1000 km     TS: 40000 km/s     ROF 5       Base 50% To Hit
GES-S1-R1 Small Threat Detection Array (1)     GPS 36     Range 2.2m km    Resolution 1
GES-S1-R160 Area Search Sensor (1)     GPS 5760     Range 27.3m km    Resolution 160

This design is classed as a Commercial Vessel for maintenance purposes

[Maharava (OP)]

Excellent set of orders Gidoran

[3_14159]

Whoooh, Capital Sector! So, looks like no expansion for me ;-)

I'll wait with the standing orders for the save. If you want to rename the Admiral, you can take Alan Kepler, Lord Protector of Earth.

I'll post some designs later, too, mostly civilian ships.

[Maharava (OP)]

So I've been writing everyone's orders etc down and saving them in files on my PC. I'm keeping them backed up as well, of course. I'm writing them in an RP-style, so that in 20-30 game years, we may decide to release these early orders and plans as 'Freedom of Information'

[Maharava (OP)]

You have SEVEN (7) Days from the date of this post until it auto-deletes. Let me know if ther's an issue or if I've forgotten something in the game

http://www.fileconvoy.com/dfl.php?id=g8047c7c7d2c368e7999251550d88233fb39c20153

[3_14159]

Cooperation is paramount. As such, here's my SOP and doctrine introduction, with the designs still missing.

Code: [Select]

January 1, 1 FC,
Doctrine introduction for Capital sector.
From: Kepler, Alan. Lord Protector of Earth.
To: Subordinates over clearance Beta (Capital Sector), Admirals

I. Designations
a) Systems:
Systems will be designated in the following way:
- BLUE: System secured; Human population.
- GREEN: System secured;
- YELLOW: System not secured. No civilians allowed. All unknown systems are treated as YELLOW.
- RED: Enemy fleet in system. No civilians allowed.

b) Ships:
Ships will be designated depending on operational radius and size:
Independent With Fleet
Small: Corvette Frigate
Medium: Cruiser Destroyer
Big: Battlecruiser Battleship

II. Exploration
a) Exploration is done by grav- and geo-scouts in GREEN systems. YELLOW systems need to be explored by warship first to make sure no enemy is present in-system.

b) Exploring new JPs is done by a group of warships.

c) Contact with potential enemies or aliens: Initiate protocol PATHOGEN.

III. Contingency plans
a) Global Alert System, Defcon:
5: No danger: Standard peaceful operations. Pickets on jump points, PD active sensors on planets online. Refits and overhauls with higher frequency (All that are available are getting overhauled). Two reloads of ordnance in stores.
4: Low danger: Peaceful operation with dangers, like pirates or possible contacts due to unexplored systems. Refits and overhauls with normal frequency, at least one JPDefense Vessel deployed per jump point. Three reloads of ordnance in stores.
3: Medium danger: Contacts or stronger tensions. Produce four reloads. Refits and overhauls when necessary, but with keeping parts of the fleet in store.
2: High danger: Recall all survey vessels. Deploy forward scouts, recall all expeditionary forces where possible and not resulting in a weaker strategic position. Six reloads producing.
1: War: Recall all civilians. All battle fleets not on active operations return to their bases. Producing as much ordnance as possible.

b) Battle Plans:
- KEROSINE, TENURE, CIRCLET, POSITRON: Escalating attack protocols.
- PATHOGEN: Do not return to any known system, instead retreat to save systems. DO NOT RETURN TO HUMAN SYSTEMS! Wait for relief by battle groups.

c) Plans:
- Alien contact: Launch KEROSINE on the system to evaluate. Initiate PATHOGEN for the contacted ships.
If you find mistakes or things missing, by all means notify me.

By the way, @ Mahavara: The geo scout is of my design, as can be seen due to being absolutely over-engineered and too expensive. ;-)

I plan on making the ship building facilities of Earth available to all of you, too. You can order ships for a small amount of additional cost to cover retooling.

[Maharava (OP)]

a) Systems:
   Systems will be designated in the following way:
      - BLUE: System secured; Human population.
      - GREEN: System secured;
      - YELLOW: System not secured. No civilians allowed. All unknown systems are treated as YELLOW.
      - RED: Enemy fleet in system. No civilians allowed.

I think we should make that standard, just for ease of play and communication (as opposed to having 6 different systems). I think you Admirals should also agree on a standardised Ship Class System by weights eg less than 10k Tons = Corvette, less than 20k tons = Frigate etc. Frigate Leaders, Jump Frigates etc are all okay within that weight class. That seem alright?

[Gidoran]

a) Systems:
   Systems will be designated in the following way:
      - BLUE: System secured; Human population.
      - GREEN: System secured;
      - YELLOW: System not secured. No civilians allowed. All unknown systems are treated as YELLOW.
      - RED: Enemy fleet in system. No civilians allowed.

I think we should make that standard, just for ease of play and communication (as opposed to having 6 different systems). I think you Admirals should also agree on a standardised Ship Class System by weights eg less than 10k Tons = Corvette, less than 20k tons = Frigate etc. Frigate Leaders, Jump Frigates etc are all okay within that weight class. That seem alright?

I'll agree to a STANAG for System and Ship nomenclature. If we're assuming a 'wet navy' bent, then we'd probably want to establish it both on tonnage, design purpose, and endurance. So a Monitor would be a ship similar to a Battleship, but with inferior speed/endurance to put on greater firepower, etc etc. I've got a plan that I'm working on for Epsilon Indi, but I'll wait to see if anyone else has a proposal they'd like to bring forth before I do so. I don't wanna steal everyone's spotlight just because I happen to be awake to post before everyone else.

Also, I find it amusing that 3_14159 and I are the only ones who actually have set up a "Don't bring the Covenant home, morons!" order.

[MagusXIX]

Alright, starting basically now I am gone until late Friday night.  The standing orders I left should be sufficient until then, I hope.  See you all in a little less than a week. 

[3_14159]

Yes, STANAG or something similar sounds good, and combining and standardizing our fleet's sizes (At least calling it the same) sounds good. I can't wait until the first 'What? Your destroyers have no PD? My have no offensive weapons' panics ;-)

As for another design, I present the Basilisk class Jump Point Customs and Orbital Traffic Control station: Built in fighter factories, the station can position itself on any jump point up to 128bkm away, where it uses its active sensor to detect all (or nearly all, some later techs might sneak by) inbound and outbound traffic. And, while a buoy of similar capabilities for detection would only cost about half that amount, it'd be about size 52 or so, which is prohibitively high. Plus, after the eighty years of duty the basilisk can be scrapped and recovers some costs.
Warning: Only deploy them on the 'inner' side of Jump Points, because otherwise they're just beacons to guide enemies to JPs.

Code: [Select]

Basilisk class Customs Station    500 tons     18 Crew     126 BP      TCS 10  TH 6  EM 0
600 km/s     Armour 1-5     Shields 0-0     Sensors 1/1/0/0     Damage Control Rating 2     PPV 0
Maint Life 79.13 Years     MSP 315    AFR 1%    IFR 0%    1YR 0    5YR 1    Max Repair 36 MSP
Intended Deployment Time: 840 months    Spare Berths 0   
6 EP Ion Drive (1)    Power 6    Fuel Use 14%    Signature 6    Exp 5%
Fuel Capacity 50,000 Litres    Range 128.6 billion km   (2480 days at full power)
Active Search Sensor MR2-R1 (1)     GPS 36     Range 2.2m km    Resolution 1
This design is classed as a Fighter for production, combat and maintenance purposes
By the way, hi Gidoran. I knew I knew your name from somewhere ;-)

[dgibso29]

Although I agree on standardised nomenclature, I would say 10kt is a bit large to still be calling something a corvette? Generally my frigates are only between 5kt and 7kt.. What do you guys think?

PS - I'll go with Vice Admiral (Dan) Gibson. Cheers, Gidoran!

[icecoldblood]

For me:
Corvette: 1000-4000t
Frigate:4000-8000t
Destroyer: 8000-12000t
Cruiser:10000-14000
Battle Cruiser: >15000
Dreadnought: >20000

P.S. I have taken interstellashadow as my Vice Admiral. Still working on character names.

[Gidoran]

For me:
Corvette: 1000-4000t
Frigate:4000-8000t
Destroyer: 8000-12000t
Cruiser:10000-14000
Battle Cruiser: >15000
Dreadnought: >20000

P.S. I have taken interstellashadow as my Vice Admiral. Still working on character names.

Close to what I had worked up for myself.

Sub-1000 tonnes = Specialist or Fast Attack Craft
1000-6000 tonnes = Corvette
6000-9000 tonnes = Frigate
9000-15000 tonnes = Destroyer or Escort Carrier
15000-18000 tonnes =  Light Cruiser or Light Carrier
18000-21000 tonnes =  Cruiser
21000-24000 tonnes =  Heavy Cruiser or Fleet Carrier
27000-30000 tonnes =  Battlecruiser

Currently with how my test designs are going, a 4000km/s fleet speed is 3000 tonnes per engine, with 3750km/s being 3200 tonnes. So most of my vessels are coming out to multiples of 3200, so Frigates are 6400, Destroyers are 9600, Light Cruisers are at 16000, and my Cruiser is resting at 19200.

In terms of mission role, I'm undecided on what Corvettes will really do, but Frigates are mostly AMM, Destroyers are ASM, and by the time we've reached Cruiser they've begun generalizing into both onboard AMM and ASM capabilities.

Also, missile size. I'm currently using size 5 because of how our technology rolled out, even though I normally use size 4s. Any dissenting opinions?

P.S. Loyalist Brofist, 3_14159.

[3_14159]

Let me vote very strongly against designating capital ships (that is, ships only based upon a certain size) as Battle Cruisers. My historical naval knowledge is irritated ;-)

Instead, how about:

Fighters: < 500t
LAC/FACs: 500t - 1000t
Corvette: < 5000t
Light Combatants: 5000t - 10,000t: Frigate, Destroyer and so on
Medium Combatants: 10,000 - 20,000t: Cruisers, Escort/Light Carriers
Capital Ships: > 20,000t: Carriers, Fleet Carriers, Battleships, Battlecruisers, Dreadnaughts, and so on.
Each Admiral having enough wiggle room to for example designate a 22,000t design as a Heavy Cruiser, or a 7000t as Light Cruiser.

As for missile sizes... size 6 is usually what I use (maximum for smalles detection), but we can, of course, take 5.

P.S.: Let's develop AIs ;-)

[dgibso29]

Let me vote very strongly against designating capital ships (that is, ships only based upon a certain size) as Battle Cruisers. My historical naval knowledge is irritated ;-)

Right there with you on that. I always place them between a Battleship and a Heavy Cruiser when a scale is needed, though.

I also agree that there should be wiggle room - This should be a broad guideline, nothing more.