Remove ads

To Boldly Go... (a Starfleet quest)

Linked contents
To Boldly Go... (a Starfleet quest) Starfleet Ship Design Bureau, Refit ("To Boldly Go...")
Reader mode
OneirosTheWriter said:
Is this voting system preferred, then? Easily understood?

As a silly aside, the movement speed does, I think, help bring out those odd "Enterprise is the only ship in the area" comments :D
Click to expand...
Click to shrink...

I like it so far. But I'm fully expecting that if some disaster happens or some "oh I thought this case plan included this and that" complaints, some will blame the system and clamor for more control :V
 
OneirosTheWriter said:
But I did...? Case Epsilon...
Click to expand...
Click to shrink...

While it's not urgent because the available case options work fine, it would be nice if you would lay out rules for write-in cases.

Specifically, what granularity of orders are allowed? Order around individual ships including non-FYMs? Group up ships into task forces and order them around? Designate approximate fleet movements and key areas like the given case options?
 
Last edited:
Well, it worked in one sense; it was easy to understand, which is the advantage of offering us canned options.

On the other hand, we basically got a landslide vote in favor of the plan that had lacked any glaring defects, which is the disadvantage of offering us canned options. Plans Beta and Gamma both had major flaws (angry Dawiar, "abandon the frontier and order our Explorer Corps out of the action") so virtually no one voted for them. It's telling that more people voted for a plan that amounts to "do nothing" than for plans Beta and Gamma (or both of them put together).

The biggest problem I see with doing this going forward is that when you're crafting the vote options, you're likely to find yourself doing one of two things.

...

One is to make one option that is fairly obviously a good choice, or at least not a grossly flawed choice, and others that appear to be alternatives but seem like bad alternatives. In that case the vote becomes something of a rubberstamp, as happened here.

You could have just told us "Starfleet is concentrating at the borders as per a pre-existing plan from Tactical, at locations X, Y, and Z..." and there would probably have been more discussion about what our deployment strategy should look like what we should do than there was with this vote. Instead, more or less everyone migrated to the plan that didn't explicitly list downsides, with very few people even sticking up for Beta or Gamma and a few people voting for Delta since they liked 'all ships sit more or less where you are' better than any of the plans on offer.

...

The other option is to make two or three or however many plans that ALL have very obvious advantages and disadvantages. The problem with that approach is that people are going to really, really want to have their cake and eat it too. And that's not even unrealistic, because in real life militaries generally try to avoid making plans that have huge glaring disadvantages. They try NOT to leave one flank totally undefended while concentrating all their force on the other. They try to get the rewards of concentrating force, without automatically parking that force concentration in the bad spot where it will cause problems. If they perceive a specific detailed flaw in a plan, like it not making good use of a single isolated element of the overall force, they fix that flaw without changing the rest of the plan.

So in this scenario, there will surely be discussion- because we're trying to make the best out of three plans that all have major strengths and weaknesses. But ultimately it'll be like arguing over which is best in a game of rock-paper-scissors; all three options will ultimately be mediocre plans (if their strengths and weaknesses cancel out), or an exercise in gambling (if picking a plan amounts to betting on whether the enemy will attack from the left/right/center or whatever).

...

Personally, I think that while we can certainly get easy resolutions to our debates, with a lot of (rubberstampy) participation by having this kind of vote... writing our own plans has a lot of advantages. Strategy is at its best when you let people devise their own plans.

But in this case that may not have turned out too well, for three reasons.

1) A lot of people, me among the worst offenders, were distracted by Linderley's show of what at first whiff smells like incompetence. This diverted the discussion away from actually planning our fleet deployment.

2) A couple of the people who are best at this kind of plan didn't really participate, for reasons of their own (e.g. Briefvoice, who cuts our ship deployment orders like half the time as far as I can remember).

3) We started out with a paradigm of "order around individual ships." Like the research plans, this involves so many interlocking variables that it's hard to make decisions.

If I had it all to do over again, here is what I would have done in your shoes.

Copy-paste a current listing of ships and locations. This would be rather lengthy, but it breaks down into sub-elements.The reason for doing this is that one of the biggest obstacles to forming a meaningful plan here was that all the information we need is scattered over multiple pages and multiple posts and is somewhat less than clear. A lot of us may not even know where to look that stuff up, even if it IS fully updated and on the front page.

So putting it all in one post right before we begin discussion of deployment would be really helpful. Sort of like how you list all our options in the snakepit.

You might have, inside one spoiler, something like

STARFLEET ORDER OF BATTLE
-Vulcan Sector
--USS ___, ___-class
--USS ___, ___-class
...
-Sol Sector
...

And so on.

Then at the bottom of this you say "Issue orders for grouping these ships into the fleets that will act as your maneuver units for the rest of the emergency." A plan would look something like:

-Ships in Vulcan Sector form First Fleet, concentrated at Vulcan.
-Ships in Sol Sector form Second Fleet, concentrated at Vega, except USS Whozit, which will move to ___.
-Et cetera.

Basically, the idea here is that we're mostly using the existing sector garrison fleets as the core of our 'numbered fleets' for the emergency.

...

Then you have a second spoiler:
MEMBER WORLD FLEETS
-United Earth
-- ___, __-class
-- ___, __-class
...
-Amarkia
--CAS Riala, Riala-class
...
...

And at the bottom of that you say either:
"Issue orders for distributing these ships within their own sectors," OR
"Issue general directives to the member world fleets notifying them of which direction you intend to have them defend against attack from," OR
[whatever level of order-giving we have with the member worlds under these circumstances]
_______________________________________

Now, all this discussion would take a while, and we might actually have to give a vote two days or so to "simmer" rather than the usual 12-24 hours. But I really think it could work, IF we adopt a healthy stance to the problem of issuing orders to ships collectively rather than individually.
 
Last edited:
Hmm, question, what do we have available to use in case the worst occurs so that even if we fall, we take our enemy down with us? I hope and pray that such never needs to be used, but I would like to know what we have in case the worst does occur.
 
@OneirosTheWriter, a few questions in order of importance.
  1. Yesterday you said that the cloaking related research from the biophage crisis didn't apply since that was focused on the particular Romulan cloaking actually used by the Inflictor, and this makes perfect sense. However, Anti-Cloaking II does apply, right? The cloaking module, which was already suspected to be Chang's, was the whole reason for switching the Vulcan Science Academy team to short range sensors, and then they even got inspiration to finish it that year. Also even before that we didn't definitely know IC that the Klingons didn't have more of that tech, so excluding it from general anti-cloaking research would have made no sense.
  2. From the suspected position of the Kadak-Tor I suppose we can conclude it was constructed at Galundun and it has been 2 weeks since the message now? And also that we don't think cloaking limits their warp speed like it does for the Romulans, presumably for the same reason it allows firing weapons.
  3. The other Cardassian forces from Galundun and Balogot are also in f-4 which is why we think the Kadak-Tor is there, right?
  4. Which of our other major colonies also have outposts, the ones for which it seems the most important to know would be Landle IV and Shrantet III.
  5. Do basic outposts still have the stats from the biophage crisis, C6 S3 H12 L12 P4 D4?
 
Last edited:
Nix said:
@OneirosTheWriter, a few questions in order of importance.
  1. Yesterday you said that the cloaking related research from the biophage crisis didn't apply since that was focused on the particular Romulan cloaking actually used by the Inflictor, and this makes perfect sense. However, Anti-Cloaking II does apply, right? The cloaking module, which was already suspected to be Chang's, was the whole reason for switching the Vulcan Science Academy team to short range sensors, and then they even got inspiration to finish it that year. Also even before that we didn't definitely know IC that the Klingons didn't have more of that tech, so excluding it from general anti-cloaking research would have made no sense.
  2. From the suspected position of the Kadak-Tor I suppose we can conclude it was constructed at Galundun and it has been 2 weeks since the message now? And also that we don't think cloaking limits their warp speed like it does for the Romulans, presumably for the same reason it allows firing weapons.
  3. The other Cardassian forces from Galundun and Balogot are also in f-4 which is why we think the Kadak-Tor is there, right?
  4. Which of our other major colonies also have outposts, the ones for which it seems the most important to know would be Landle IV and Shrantet III.
  5. Do basic outposts still have the stats from the biophage crisis, C6 S3 H12 L12 P4 D4?
Click to expand...
Click to shrink...
Anti-Cloaking general tech applies, yes.

2 is correct
3 is correct
4 - I'm in the middle of making the status page, I'll try to list the places with full outposts.

I'm shifting outposts so that they have
C4 S3 H8 L8 P4 D4

This still gives them tougher shields and hull than anything mobile, but prevents them from being full battlestations, which is something that I think should be reserved for Starbases. This also applies to outposts from opposing factions.
 
OneirosTheWriter said:
I'm shifting outposts so that they have
C4 S3 H8 L8 P4 D4

This still gives them tougher shields and hull than anything mobile, but prevents them from being full battlestations, which is something that I think should be reserved for Starbases. This also applies to outposts from opposing factions.
Click to expand...
Click to shrink...

While you're in an informative mood, can you also please clarify how the outpost/starbase defense stat helps out? Can an outpost/starbase "respond" to events like a ship (like the higher the defense, the higher a chance of occurring at a outpost/starbase)? Or does it just provide some sort of bonus to ships in the sector?

4 - I'm in the middle of making the status page, I'll try to list the places with full outposts.
Click to expand...
Click to shrink...

Can you also clarify which of the outposts are Starfleet managed for garrison requirements (and event?) purposes?
 
Yes.

Especially since for now, the best thing we can probably do with our member world assets is tell each member world "these are the threats we face, this is what our ships are doing to meet the threat, do what you think best to defend yourself."

Aside from the Amarki (who have two capital-class explorers), most of the member world fleets consist of ships that are pretty small potatoes by galactic standards. No one or two ships they send are likely to make a decisive difference in the resolution of this crisis. Whereas having all those ships around on the home front is valuable.

Some of the member worlds will want to deploy their fleets to defend against the Sydraxian threat. Others will want to 'turtle' and concentrate their defenses around their homeworld in case the Kadak-Tor comes knocking. Both of those are logical reactions to the situation.

About the only actual orders I feel we need to issue to a member fleet is that the Betazoids should move their ships to link up with the United Earth forces. Betazed is extremely unlikely to be a target, and the reinforcements could come in really handy.

...

You know, with a bit more organized information, I'd be willing to draft a plan myself. Though right now it's too late in my time zone, so I probably won't get around to it until eight hours or so from now.

Sometimes I have trouble believing how late I stay up these daynights...
 
Remove ads
Ghosts and Whispers - Current Status
  • Threadmarks
    • Ghosts and Whispers - Current Status

    Starfleet Status: High Alert (Can travel 1 Sq Length per Week)
    Federation Status: Normal

    Member World Fleets: High Alert
    Caitian: High Alert
    Apiata: High Alert
    Indoria: High Alert
    Orion: State of Emergency
    Rigel: Normal
    Caldonia: Normal
    Risa: High Alert
    Gaen: Normal
    Seyek: High Alert

    W4 Changes - Caitian and Risa go to High Alert

    Kahurangi's Opinion of Starfleet Intelligence: Annoyed

    Known Details
    The CDF Kadak-Tor departed on its shakedown cruise from Galundun shipyards a a week before the new year. It has sent a message back to Cardassia, after which a very large portion of the Cardassian fleet has departed their space, heading towards the Federation.

    Starfleet Assets

    First Fleet
    -Stationed at Vega
    --USS Endurance, Excelsior, NCC-2007
    --USS Bull, Centaur-A, NCC-2107
    --USS Lion, Miranda, NCC-1654
    --USS Bon Vivant, Miranda, NCC-1621

    Second Fleet
    -Stationed at Tales Har
    --USS Salnas, Excelsior, NCC-2009
    --USS Vigour, Constellation, NCC-1804
    --USS Dryad, Miranda, NCC-1631

    Third Fleet
    -Stationed at Ord Grind Duk
    --USS Excelsior, Excelsior, NCC-2001
    --USS Stalwart, Constellation, NCC-1807
    --USS Sappho, Constellation, NCC-1812
    --USS Lightning, Centaur-A, NCC-2105
    --USS Gale, Centaur-A, NCC-2106
    --USS Calypso, Miranda, NCC-1632
    --USS Svai, Miranda, NCC-1658

    Fourth Fleet
    -En Route to 15 Themis Outpost
    --USS Avandar, Excelsior, NCC-2010

    --USS Docana, Constellation, NCC-1810
    --USS Eketha, Miranda, NCC-1655
    --USS Suvek, Oberth, NCC-1508

    Sol Sector Fleet
    -Stationed at Earth
    --USS Fidelity, Miranda, NCC-1634
    -Stationed at Betazed
    --USS Selaya, Constellation, NCC-1803

    Vulcan Sector Fleet
    -Stationed at Vulcan
    --USS T'Kumbra, Miranda, NCC-1659

    Andor Sector Fleet
    -Stationed at Andoria
    --None

    Tellar Sector Fleet
    -Stationed at Tellar Prime
    --None

    Amarkia Sector Fleet
    -Stationed at Amarkia
    --USS Hawking, NCC-1509

    Fifth Fleet
    -Stationed at 21 Themis
    --USS Kumari, Excelsior, NCC-2005
    --USS Enterprise, Excelsior, NCC-1701-B
    --USS S'harien, Excelsior, NCC-2008
    --USS Cheron, Constitution, NCC-1720
    --USS Challorn, Constellation, NCC-1809
    --USS Zephyr, Centaur, NCC-2103
    --USS Winterwind, Centaur-A, NCC-2104

    Klingon Border Zone Fleet
    -Stationed at Biroth
    --USS Kearsage, Constellation, NCC-1811
    --USS Thunderhead, Miranda, NCC-1656
    --USS Intrepid, Miranda, NCC-1657
    --USS Inspire, Oberth, NCC-1510

    Romulan Border Zone Fleet
    -Stationed at Beta Indi Starbase
    --USS Shield, Miranda, NCC-1661

    Explorer Corps
    -USS Courageous (at Gaen, close to completion of repairs, available Q2.M1.W1)
    -USS Sarek (-3d, heading core-ward)
    -USS Miracht (4a)

    Orion Operations
    -Stationed at Alukk
    --USS Yukikaze, Centaur-A, NCC-2101

    Starfleet Sector Infrastructure

    "Critical" - One of very few (or even only one) of its given type of infrastructure within Starfleet's control, the loss of which will cause major loss of function
    "Key" - Important assets, the loss of which will impair functions for Starfleet

    Sol Sector
    -Sol (0a) - Starbase, 2 Shipyards, Critical Political Assets, Critical Research Assets [SDB teams], Critical Logistical/Industrial Assets [Main Academy, Warp Cores, Weapons Assembly]
    -Alpha Centauri (0A) - Political Assets, Critical Industrial Assets[Dilithium Refurb Plant], Resource Assets
    -Subiaco (0a) - Outpost, Critical Industrial Assets [Anti-Deuterium Plant]
    -Lalande (1A) - Resource Assets, Industrial Assets [Deflector Emitters]
    -Betazed System (1B) - Outpost, Key Political Assets

    Vulcan Sector
    -Vulcan (-2A) - Starbase, 1 Shipyard, Critical Political Assets, Key Research Assets, Critical Industrial Assets [Sensor Fabrication], Key Logistical Assets, Resource Assets
    -Atatan (-1B) - Political Assets, Resource Assets, Key Industrial Assets [Deflector Fabrication]
    -Meridia (-2A) - Research Assets
    -P'Kanath (-2B) - Research Assets

    Andor Sector
    -Andor (-3A) - Starbase, 1 Shipyard, Critical Political Assets, Logistical Assets, Critical Research Assets, Key Industrial Assets [Deflector, Warp Drive Fabrication], Resource Assets
    -Machado (-3B) - Outpost, Logistical Assets
    -Josephine (-3a) - Resource Assets
    -Ranford (-4A) - Logistical Assets, Industrial Assets [Deflector, Sensor Fabrication]
    -Sardry (-3a) - Industrial Assets [Transporter Fabrication]

    Tellar Sector
    -Tellar (-2a) - Starbase, 1 Shipyard, Critical Political Assets, Logistical Assets, Resource Assets, Research Assets, Key Industrial Assets [Transporter, Weapon Fabrication]
    -Lagh Cheg (-1b) - Critical Industrial Assets [Dilithium Refurb]
    -Sar Alpha (-3a) - Key Industrial Assets [Warp Core Fab]
    -Ord Grind Duk (-3b) - Logistical Assets, Critical Industrial Assets [Anti-Deuterium Plant]

    Amarkia Sector
    -Amarkia (-2d) - Starbase, Critical Political Assets, Critical Logistical Assets, Research Assets, Resource Assets
    -Tales Har (-1c) - Resource Assets, Industrial Assets [Transporter, Weapon Fabrication]
    -Hophos (-2c) - Resource Assets
    -Leas Akaam (-2d) - Outpost, Political Assets, Key Logistical Assets

    RBZ
    -Beta Indi (-3C) - Starbase, Key Logistical Assets
    -Solitude (-4C) - Outpost
    -Claystock (0C) - Outpost

    KBZ
    -Tipperary (-5A) - Outpost, Key Logistical Assets
    -Biroth (-5a) - Resource Assets, Research Assets

    CBZ
    -21 Themis (-4e) - Outpost, Resource Assets

    Apinae Sector
    -Vintus (-2e) - Outpost, Key Logistical Assets
    -Aelin (-2f) - Outpost, Research Assets
    -Beta Corridan (-1e) - Outpost, Resource Assets
    -Galus V (-3e) - Resource Assets
    -15 Themis (-3e) - Outpost

    Ferasa Sector
    -Pygmalion (-4b) - Resource Assets

    Unclaimed Space
    -Yel'usulausu (-6b) - Research Assets)


    Member World Assets

    United Earth
    -Stationed at Earth
    --2 Miranda
    -Stationed at Vega
    --1 Constellation
    --1 Centaur-A
    -Stationed at Joburg
    --1 Constellation
    --1 Miranda
    -Stationed at Alukk
    --1 Centaur-A
    --2 Miranda

    Vulcan
    -Stationed at Vulcan
    --3 Constellation
    --5 Miranda
    --2 Soyuz
    --1 Oberth

    Andor Guard
    -Stationed at Andoria
    --1 Constellation
    --2 Miranda
    --1 Soyuz
    -Stationed at Landle IV
    --1 Constellation
    --2 Centaur-A
    --1 Miranda
    -Stationed at Alukk
    --1 Constellation
    --1 Centaur-A
    --2 Miranda

    Tellarites
    -Stationed at Klivvar Proxima
    --1 Constellations
    --3 Miranda
    --1 Soyuz
    -Stationed at Ord Grind Duk
    --2 Constellations
    --1 Centaur-A
    --3 Miranda

    Amarki Confederacy Fleet
    -Stationed at Selindra
    --CAS Riala, Riala-class
    --CAS Friec, Riala-class
    --CAS Hebrinda, Hebrinda-class Cruiser
    --CAS Hilindia, Hebrinda-class Cruiser
    --CAS Odala, Hebrinda-class Cruiser
    --CAS Perciar, Perciar-class Cruiser
    -4 Light Escorts
    -4 Heavy Escorts

    Betazoid Defence Force
    -Stationed at Betazed
    --3 Cruisers
    --6 Patrollers

    Member World Sector Infrastructure

    UE = United Earth
    V = Vulcans
    A = Andorian Empire
    T = Tellarites
    M = Amarkian Confederacy
    B = Betazoids

    Sol Sector
    -Sol (0a) UE - Outpost, 1 Shipyard, Critical Political Assets, Critical Industrial Assets [UE Warp Core, Drives, Weapons]
    -Alpha Centauri (0A) UE- Critical Political Assets, Agricultural Assets
    -Subiaco (0a) UE - Research Assets
    -Lalande (1A) UE - Resource Assets, Agricultural Assets
    -Vega (0b) UE - Political Assets, Agricultural Assets
    -New Seoul (0B) UE - Political Assets, Key Industrial Assets [UE Deflectors, Transporters]
    -Joburg (1a) UE - Key Industrial Assets [UE Sensors]
    -Motara (0A) UE - Mining Colony - Resource Assets
    Various Minor Colony Worlds, including on Moons and Satellites

    -Betazed System (1B) B - Outpost, Key Political Assets, Agricultural Assets
    -Onos (1B) B -Major Colony, Agricultural Assets
    -Tawxa (1B) B - Mining Colony - Resource Assets
    -Costaun (1C) B - Minor Colony - Research Assets


    Vulcan Sector
    -Vulcan (-2A) - Shipyard, Homeworld
    -Atatan (-1B) - Political Assets, Resource Assets, Key Industrial Assets [Deflector Fabrication]
    -Meridia (-2A) - Research Assets
    -P'Kanath (-2B) - Research Assets
    -82 Eridani (-1B) - Political Assets, Industrial Assets
    Various Minor Colony Worlds, including on Moons and Satellites


    Andor Sector
    -Andor (-3A) - Shipyard, Homeworld, Critical Industrial Assets [A All Items]
    -Machado (-3B) - Industrial Assets, Logistical Assets
    -Ranford (-4A) - Key Resource Assets, Industrial Assets
    -Sardry (-3a) - Political Assets, Key Agriculatural Assets
    -Jhaylyk (-3A) - Mining Colony, Industrial Assets, Resource Assets
    -Mu Proxima (4a) - Agricultural Assets
    Various Minor Colony Worlds, including on Moons and Satellites

    Tellar Sector
    -Tellar (-2a) - 1 Shipyard, Homeworld, Critical Industrial Assets [T, All Items]
    -Lagh Cheg (-1b) - Outpost, Key Logistical Hub
    -Klivvar Proxima - Outpost, Shipyard, Key Agrilcultural Assets, Political Assets
    -Sar Alpha (-3a) - Shipyard, Agricultural Assets
    -Ord Grind Duk (-3b) - Outpost, Shipyard, Key Industrial Assets, Key Political Assets
    -Vurglurk (-2b) - Mining Colony - Key Resource Assets
    -Tag Kut Mork (-1a) - Mining Colony
    -Certunn Epsilon (-1b) - Mining Colony
    Various Minor Colony Worlds, Moons, Satellites

    Amarkia Sector
    -Amarkia (-2d) - Homeworld, Shipyard, Critical Industrial Assets
    -Tales Har (-1c) - Outpost Shipyard, Political Assets, Resource Assets, Key Industrial Assets
    -Leas Akaam (-2d) - Shipyard, Logistical Assets,
    -Selindra (-2c) - Outpost Shipyard, Political Assets, Key Agricultural Assets
    -Delfriebh (-1d) - Mining Colony, Resource Assets
    -Gaiar Har (-2d) - Outpost, Key Resource Assets
    -Tiankaria (-1c) - Research Assets
    Various Minor Colony Worlds, Moons, Satellites


    Affiliate Worlds

    Seyek
    -Rethelia (-5f) - Starbase, Shipyard, Critical Political Assets, Critical Industrial Assets, Critical Resource Assets, Critical Research Assets
    -Fiiral (-5e) - Outpost, Key Political Assets, Resource Assets, Research Assets, Key Industrial Assets
    -Celepisos (-6d) - Outpost
    -Saritcos (-6f) - Resource, Research Assets
    -Hacitorus (-5f) - Shipyard, Resource Assets, Key Industrial Assets, Political Assets
    -Hassonus (-5e) - Outpost, Shipyard, Research Assets, Key Industrial Assets

    Affiliate Fleets
    -Caitian Fleet @ Ferasa
    --3 Fatherships, 8 Modern Swarmers, 3 Old Swarmers
    -Caldonian Fleet @ Caldonia
    --4 Science Cruisers, 6 Escorts
    -Indoria @ Indoria
    --1 Ship-of-the-Line, 2 Frigate, 2 Heavy Escorts, 4 Patrol Escorts
    -Apiata Fleet @ Apinae
    --1 Queenship, 1 Little Queenship, 2 Stingers, 2 Old Stingers, 1 Forager
    -Apiata Fleet @ Alrizzine
    --2 Little Queenship, 3 Stingers, 2 Old Stingers, 2 Foragers
    -Apiata Fleet @ Burrizz
    --2 Little Queenship, 3 Stingers, 2 Old Stingers, 2 Foragers
    -Rigellian Fleet @ Rigel
    --1 Megatortoise, 5 Turtleships, 5 Cutters, 3 Old Cutters
    -Orion Union @ Alukk
    --2 Cruisers, 8 Escorts
    -Risan Hedony Fleet @ Risa
    --4 Heavy Corvettes, 4 Corvettes

    Starfleet/Federation Supply Lines
    Amarkia <-> Tellar Prime
    Tellar Prime <-> Sol
    Sol <-> Vulcan
    Vulcan <-> Andor
    Andor <-> Tellar Prime

    Andor <-> Ranford <-> Tipperary -> KBZ
    Andor <-> Machado <-> Beta Indi -> RBZ
    Amarkia <-> Leas Akaam <-> Vintus -> CBZ

    Cardassian Assets (Known)

    Group A
    Kadak-Tor, Modified Kaldar
    Suspected to be in -3c

    Group B
    'Frontier Group'
    3 Jaldun (Trager, Karnack, Ronagot)
    1 Science Escort (Parok)
    Apprx -5c

    Group C + D
    2 Kaldar
    2 Jaldun
    3 Escort-grade
    Apprx -4d

    Group E + F
    3 Jaldun
    1 Kaldar
    1 Lorgot
    2 Escort-grade
    Apprx -4e

    Group G
    ~4 Warp Signatures
    Apprx -4g

    Group H
    ~2 Warp Signatures
    Apprx 1d

    Known Cardassian Worlds

    Cardassia (?) - Homeworld

    Karadoc (0i) - Starbase, Shipyard, Sector Lead

    Vedarot (-1i) - Outpost

    Trangot (-2i) - Outpost

    Balogot (-3h) - Outpost

    Galundun (-4h) - Starbase, Shipyard, Sector Lead

    Kamey Prime (-1h) - Mining Colony

    Logistics Routes
    All Unknown

    However, Starfleet Tactical presumes with strong confidence that a line runs from Karadoc through to Galundun.

    Known Cardassian AFfiliates

    Sydraxian Hierarchy

    Lecarre

    Dawiar

    Suspected: Yrillians, Bajor
     
    Last edited:
  • Threadmarks
    • Lots of new stuff to put on the map. I guess I should put down any federation colony that does not get a Councilor as a minor colony, even if its strategically important?
     
    Reader mode
    You must login or register to reply here.
    Remove ads
    Back
    Top