Daystrom Institute: Automated Ship Systems



+10

38 / 60 Majel 3.5 (Ship Operating System III)
33 / 60 Targeting Computer III
35 / 40 Navigational Computer I
30 / 40 Barret-V System Automation (Crew Saving I) (Reduce Enlisted Crew Requirements)

[Frame complete]

Ah, what Frame?


@OneirosTheWriter, a suggestion: In future votes as important and volatile as the retconned politics stuff, maybe it would be helpful to declare several hours of vote moratorium, so there's more time to make sure we understand the situation and run write-in ideas by you before a hasty landslide bandwagon vote makes any more careful later votes irrelevant?
 
So there is a third tier of Cardassian Research available now, which has the same cost as the second tier and will presumably grant the same benefits, including a third Cardassian report. That probably means we will want to assign the Tiger Team to it (who will finish it in 6 years, boosts not very useful as even 5 boosts will only mean a 98% chance to finish it a year early), so we will probably want another foreign analysis team in the snakepit like @Briefvoice suggested(to finish tier 1 of Klingon Research and perhaps then T1 of Commonweath Research). Let's say Foreign Analysis/Xenopsychology because that's a combination that makes sense and we don't have yet. Also Xenopsychology is a field that we can rely on to be able to usefully employ this team if we somehow end up with too many foreign analysis teams. I don't particularly expect us to ever assign that team there, but you never know.
 
Last edited:
Ah, what Frame?


@OneirosTheWriter, a suggestion: In future votes as important and volatile as the retconned politics stuff, maybe it would be helpful to declare several hours of vote moratorium, so there's more time to make sure we understand the situation and run write-in ideas by you before a hasty landslide bandwagon vote makes any more careful later votes irrelevant?
The problem is that on weekdays I rarely get to update before late in the evening, so I'm not really around to support the discussion during the moratorium. So unless I restrict important voting posts to the weekends...?

which has the same cost as the second tier

That should be 0/90, sorry.
 
Last edited:
The problem is that on weekdays I rarely get to update before late in the evening, so I'm not really around to support the discussion during the moratorium. So unless I restrict important voting posts to the weekends...?
Post an announcement during the week so we can ask questions before we get to the vote? Sounds like quite a bit of work though.
 
The problem is that on weekdays I rarely get to update before late in the evening, so I'm not really around to support the discussion during the moratorium. So unless I restrict important voting posts to the weekends...?

Possibly write the update in the evening, but delay posting it until the next day or so when you have some time to check in occasionally and answer feedback?


And could you explain what the "Frame Completed" quoted above refers to?
 
Last edited:
So check this out based on the new Defense requirements.

Proposed 2317 Fleet Distribution

Fleet Strength Changes
2316.Q4 – 2 year Caldonian Peacekeeping Operation (D8) begins and 1 year Ataami Defense Operation (20C) begins.
2316.Q4 – (PROPOSED) Slightly draw down Gabriel Expanse by sending the Kumari, 2 Constitution-Bs and 1 Centaur-A to cover Ataami Defense Operations. Draw down Licori Border zone by 1 Constitution-B and 1 Constellation to cover Caldonian Peacekeeping Operations.
2317.Q1 – Tarrak [Excelsior in Ana Font Berth A] completes (Explorer Corps)
2317.Q1 – Pleezirra [Excelsior in SF Berth A] completes
2317.Q1 – Excelsior [Excelsior] goes into refit for Excelsior-A pattern
2317.Q1 – Lion completes refit as Miranda-A
2317.Q1 – Svai completes refit as Miranda-A
2317.Q1 – Dryad [Miranda] goes into refit
2317.Q1 – Calypso [Miranda] goes into refit
2317.Q2 – Renaissance [Ana Font Berth 1] completes
2317.Q3 – Challorn completes refit as Constellation-A
2317.Q3 – Sappho completes refit as Constellation-A
2317.Q3 – Kearsage [Constellation] goes into refit
2317.Q3 – Vigour [Constellation] goes into refit
2317.Q4 – Miranda-A [SF Berth 1] completes
2317.Q4 – Ataami Defense Operations ends. Kumari [Excelsior] Goes into refit for Excelsior-A pattern. Other ships go to other sectors.

2316.Q3 = "Current".

Sol Sector – Requires D18
  • Current - 1 Excelsior (6) [Pathfinder], 1 Centaur-A (3) [Lightning], 2 Starbase I (10) [Earth, Betazed] = 19D
  • 2317.Q1 – No change
  • Notes: No change.
Vulcan Sector – Requires D10
  • Current – 1 Constellation (3) [Docana], 2 Miranda (4) [Dryad, Calypso], Starbase I (5) = 12D
  • 2317.Q1 – 1 Constellation (3) [Docana], 1 Miranda-A (2) [Lion], Starbase I (5) = 10D
  • Notes: In 2317.Q1 Dryad and Calypso go into refit, and are replaced by Lion.
Andor Sector – Requires D7
  • Current – 1 Constitution-B [Huascar], Starbase I (5) = 10D
  • 2317.Q1 – No change.
  • Notes: No change.
Tellar Sector – Requires D7
  • Current – 1 Constellation (3) [Vigour], Starbase I (5), Extra Outposts (5) = 13D.
  • 2317.Q3 – 1 Constellation-A (4) [Challorn], Starbase I (5), Extra Outposts (5) = 14D.
  • Notes: In 2317.Q3 Challorn arrives from refit, and Vigour goes into refit.

Amarkia Sector – Requires D7
  • Current - 1 Constellation (3) [Kearsage], 1 Centaur-A (3) [Zephyr] Starbase I (5), Extra Outposts (5) = 16D
  • 2317.Q3 - 1 Constellation-A (4) [Sappho], 1 Centaur-A (3) [Zephyr] Starbase I (5), Extra Outposts (5) = 17D
  • Notes: In 2317.Q3 Sappho arrives from refit, Kearsage goes into refit.
Ferasa Sector – Requires D10
  • Current - 1 Excelsior-A (6) [Endurance], 1 Centaur-A (3) [Bull], Starbase I (5) = 14D
  • 2317.Q4 – 1 Excelsior-A (6) [Endurance], 1 Constitution-B (5) [Defiant], 1 Centaur-A (3) [Bull], Starbase I (5) = 19D
  • Notes: No change.
Rigel Sector – Requires D7
  • Current – 1 Excelsior (6) [Avandar], 1 Constellation (3) [Selaya], Starbase I (5) = 14D
  • 2317.Q4 – 1 Excelsior (6) [Avandar], 1 Constitution-B (5) [Korolev], 1 Constellation (3) [Selaya], Starbase I (5) = 19D
  • Notes: No change.
Apinae Sector – Requires D10
  • Current - 1 Constitution-B (5) [Valiant], 1 Centaur-A (3) [Yukikaze], Starbase I (5) [Grand Hive of Apinae], Extra Outposts [5] = 18D
  • 2317.Q2- 1 Constitution-B (5) [Valiant], 1 Centaur-A (3) [Yukikaze], 2 Starbase I (5) [Grand Hive of Apinae, Indorian Starbase], Extra Outposts [5] = 23D
  • Notes: Indorian Starbase completes in 2317.Q2
Romulan Border Zone – Requires D15
  • Current – 1 Excelsior (6) [Excelsior], 1 Centaur-A (3) [Cloudburst], 1 Oberth (1) [Inspire], Starbase I (5) = 15D
  • 2317.Q1 - 1 Excelsior (6) [Pleezirra], 1 Centaur-A (3) [Cloudburst], 1 Oberth (1) [Inspire], Starbase I (5) = 15D
  • 2317.Q4 - 1 Excelsior (6) [Pleezirra], 2 Centaur-A (6) [Cloudburst, Winterwind], 1 Oberth (1) [Inspire], Starbase I (5) = 18D
  • Notes: In 2317.Q1, new Excelsior build Pleezirra in SF Berth A comes in and Excelsior goes into refit. In 2317.Q4, Winterwind arrives from Ataami Defense Operation.
Klingon Border Zone – Requires D10
  • Current – 1 Excelsior (6) [Thirishar], 1 Centaur-A (3) [Typhoon], 1 Oberth (1) [Hawking] = D10
  • 2317.Q2- 1 Excelsior (6) [Thirishar], 1 Centaur-A (3) [Typhoon], 1 Oberth (1) [Hawking], 1 Starbase I (5) = 15D
  • 2317.Q4 - 1 Excelsior (6) [Thirishar], 1 Centaur-A (3) [Typhoon], 1 Miranda-A (2) [SF Berth 1], 1 Oberth (1) [Hawking], 1 Starbase I (5) = 17D
  • Notes: Starbase complete in 2317.Q2. New Miranda-A SF Berth 1 arrives in 2317.Q4
Cardassian Border Zone – Requires D12
  • Current - 1 Excelsior (6) [Salnas], 1 Oberth (1) [T'Mir], 1 Starbase I (5) [Lapycorias] = 12D
  • 2317.Q2 – 1 Excelsior (6) [Salnas], 1 Renaissance (5) [Ana Font Berth 1], 1 Oberth (1) [T'Mir], 1 Starbase I (5) [Lapycorias] = 17D
  • Notes: In 2317.Q2 Renaissance [Ana Font Berth 1] sent here after completion.
Sydraxian Border Zone – Requires D11
  • Current – 1 Constitution-A (5) [Cheron], 1 Centaur-A (3) [Gale], Starbase I (5) [Vega] = 13D
  • 2317.Q1 – 1 Constitution-A (5) [Cheron], 1 Miranda-A (2) [Svai], 1 Centaur-A (3) [Gale], Starbase I (5) [Vega] = 15D
  • Notes: Svai arrives from refit in 2317.Q1.
Gabriel Border Zone – Requirement Left to Starfleet judgment
  • Current - 1 Excelsior-A (6) [Sojourner], 1 Excelsior (6) [Kumari], 5 Constitution-B (25) [Korolev, Defiant, Exeter, Saratoga, Republic], 4 Renaissance (20) [Renaissance, Epiphany, Enlightenment, Insight], 1 Centaur-A (3) [Winterwind], 11 Miranda-A (22) [T'Kumbra, Agile, Bantam, Clarion, Fidelity, Bon Vivant, Shield, Intrepid, Eketha, Eclipse, Firefly] = 95 C.
  • 2316.Q4 - 1 Excelsior-A (6) [Sojourner], 3 Constitution-B (15) [Exeter, Saratoga, Republic], 4 Renaissance (20) [Renaissance, Epiphany, Enlightenment, Insight], 11 Miranda-A (22) [T'Kumbra, Agile, Bantam, Clarion, Fidelity, Bon Vivant, Shield, Intrepid, Eketha, Eclipse, Firefly] = 75 C.
  • Notes: In 2316.Q4, take the Kumari, Korolev, Defiant, and the Winterwind out to Ataami Defense operations.
Licori Border Zone – Requires D11
  • Current – 1 Excelsior (6) [Rru'adorr], 2 Constitution-B (10) [Lexington, Hood], 1 Constellation (3) [Stalwart], 1 Oberth (1) [Torbriel] = 20D
  • 2317.Q1- 1 Excelsior (6) [Rru'adorr], 1 Constitution-B (5) [Lexington], 1 Oberth (1) [Torbriel] = 12D
  • Notes: Send Hood and Stalwart to Caldonian Peacekeeping Mission.
Caldonian Peacekeeping Mission – Requires D8 from 2316.Q4 through 2318.Q3
  • Current – Nothing
  • 2316.Q4 - 1 Constitution-B (5) [Hood], 1 Constellation (3) [Stalwart] = D8
  • Notes: Sending Hood and Stalwart from Licori Border Zone.
Ataami Defense Operation – Requires 20C Starfleet from 2316.Q4 through 2317.Q3
  • Current – Nothing
  • 2316.Q4 – 1 Blooded Excelsior (7) [Kumari], 2 Constitution-B (10) [Korolev, Defiant], 1 Centaur-A (3) [Winterwind] = 20C
  • 2317.Q4 – Operations end, ships go to other sectors. Kumari goes into refit, Korolev goes to Rigel Sector, Defiant goes to Ferasa Sector, Winterwind goes to RBZ.
 
Last edited:
The problem is that on weekdays I rarely get to update before late in the evening, so I'm not really around to support the discussion during the moratorium. So unless I restrict important voting posts to the weekends...?
What you could do when you finish a post with a new type of vote on something important would be to just post the update, answer questions the next day (and perhaps open the vote if it wasn't already open) and only close the vote the day after that? If you feel like writing a post during the voting time you can probably do something like a captain's log, GBZ report, or results post, whoever is running the vote counter would need to explicitly specify the starting post instead of using threadmarks but that shouldn't be too much of an issue?
 
Okay looking at research results now:

Finished-
40 Eridani A Shipyards: Kepler Project- this will go to part 2 of the project next year
San Francisco Fleet Yards : 2320s Construction Techniques- 10% boost in berth capacity (so our 3mt now function as 3.3mt)
Andorian Academy: 2310s Navigational Deflectors- T2 Nav Deflectors are now unlocked for use, more parts are always good for designing the next ship which looks to be an escort
Cdr Kuznetsova's Tiger Team: The Mission Unending- 5 pp for every explorer when we complete a build and -1 to their combat against our cap? Yes this is good, plus it finishes up the lone ranger doctrine letting a skill 5 team be reassigned
Admiral Lathriss : Border World Focus -our first defense doctrine finishes, the -1 against combat cap for ships in border zones combined with the D rebalance to border zones is nice. The followup tech, mutual support is going to make it even better (lets ships in the border zone respond to events in neighboring home sectors)
Starfleet Tactical Command - Games & Theory Division: Cardassian Research- frees up a team for offensive doctrine and gets us another Cardassian report (so we can have 3 if the listening post procs!) plus bonus to our combat and penalty to theirs and a little evasion makes a nice add

One Year-

Yoyodyne Propulsion Systems: 2320s Core Power- This gets us T3 warp cores and injectors which is a very nice part to gain improvements on as power is needed for all systems and more power gives us more flexibility in sizes and designs
Caitian Frontier Police R&D: 2310s Personal Protection- +1 and reduced casualties to events involving boarding/away team combat has come up quite a bit, reduction to crew loss from damage is nice, less casualties from combat is always good
Vulcan Science Academy: 2320s Geological Sensors- Unlocks the geo sensor part which helps with mapping missions (which can lead to resource colonies!)
Starfleet Medical Research Command : 2320s Preventative Care - we got 1 finished for +.25 to all crew with another +.25 to crew finishing next year and +2 to roll against botched plague checks so better chance of survival
Taves Nar Orbital Engineering: 2310s Starbase Design - Control- +1 D to installations means our starbases cover more of a sectors D requirements and +1 to response rolls in sectors that have a starbase is great

Two Year-
Amash Hagan Research Office: 2320s Research Centers- -.5 RP per team to activate is huge (30 teams this year equals savings of 15 RP) oh and each research colony produces +1 RP so a nice boost to income
Daystrom Institute: Automated Ship Systems- unlocks reduced crew frame and reduces Enlisted requirements (no idea if this is for the frame only or for all ships and if it applies to existing ships or to new ships)
Generic Team 1: 2310s Long -Range Sensors - hi, I heard +1 D from starbases is nice, have some more
Weapons Fabrication Division: 2310s Phaser Development- +4% burn through chance on hits... so better chance of ignoring shields in combat, yes please (just wait until we get that burn-through crit from a Elite Excelsior-A or Ambassador)
Starfleet Tactical Prograde Operations Team : 2310s Torpedo Development- needs one boost to finish in two years, unlocks the next set of Torpedo parts
Federation Broadcast Service : 2320s Long-Range Comms- +1 to response rolls is always nice (works well with Chen's bonus and mutual support as well), also increases distress call event rate, for me I am assuming that increases the chance a generated event is a distress call as opposed to more events
Starfleet Science Academy: 2320s Decryption- improved intel phase info and getting intel reports on new powers sooner? Yes please to better and more intel
All-Pyllix Geological Institute : 2310s Bulk Resources- needs one boost on the final year, more BR from missions and +5 to BR mining colonies, and we have burned through a lot of our BR stockpile
Starfleet Infectious Diseases Institute: 2320s Trauma Medicine- needs one boost to finish in two years, bonuses to crew survival, always useful
Intazzi Team : 2320s Fusion Power- may need boost final year, depends on which tech gets inspiration, Stations gain +1 L, +1 S; Outposts gain +1 L, +1 S; Starbases gain +1 C, +1 L, +1 S, so I heard we like Starbases and Outposts
Apinae Protective Engineering Bureau : To Boldly Go- more events in the border zones and +1 to response rolls there
Utopia Planitia Design Group: 2320s Explorer - Science- may need a boost last year, Unlockes operations subframes for explorers

So that is actually most teams due to finish in the next two years
 
Ataami Defense Operation – Requires 20C Starfleet from 2316.Q4 through 2317.Q3
  • Current – Nothing
  • 2316.Q4 – 1 Blooded Excelsior (7) [Kumari], 2 Constitution-B (10) [Korolev, Defiant], 1 Centaur-A (3) [Winterwind] = 20C
  • 2317.Q4 – Operations end, ships go to other sectors. Kumari goes into refit, Korolev goes to Rigel Sector, Defiant goes to Ferasa Sector, Winterwind goes to RBZ.
Interesting. I'd been presuming that we'd need to take from closer sectors than the GBZ, thus I'd done more shuffling to assemble the Ataami TF.
Probable overall Ataami TF:
2 Excelsiors (1 Blooded)
3 ConnieBees
1 Centaur-A, 3 Miranda-As
C40 S29 H26 L35 P26 D36
Weaker than my proposals, but more responsive.

I see you're still giving Saratoga the ability to redeem herself against the Cardies in the GBZ.

Overall, I like the plan. You could maybe consider swapping the Miranda-A you assigned to the KBZ in 2317Q4 with the Zephyr out in Amarkia, but there's no real need.

@OneirosTheWriter - do we get to pick a Gaeni tech team?
 
Last edited:
That 15 point bonus to phase arrays is sweet... Only need 3 boosts over 4 turns to finish it up that way.
 
The problem is that on weekdays I rarely get to update before late in the evening, so I'm not really around to support the discussion during the moratorium. So unless I restrict important voting posts to the weekends...?
Specifically for political stuff, that might actually not be such a bad idea.

It's like, snakepits are fairly routine and everyone understands what's going on. There are disagreements but nothing likely to turn bitterly personal over misunderstandings of what's involved. Shipbuilding votes, fleet deployment votes, research votes, even intelligence committee votes? Likewise. Those are all things that have become 'routine,' most of the key players will reliably understand what's at stake for that reason.

Votes involving Federation politics and significantly reshaping the future of Starfleet? Unique one-off votes where the options are new, the situation is new, and the proposed solution is different enough from past experience that people aren't sure how to interpret its results? Especially when an NPC is involved who's been a focus of controversy in the past?

Maaaaaybe something like that could/should wait for the weekend.

It's not going to turn the game inside out if the vote on whether to have Federation peacekeepers or the vote on how to handle Starfleet logistics are delayed another quarter or two. Or, for that matter, front-loaded a quarter or two.

So actually, maybe it wouldn't be that bad if you said to yourself "you know, this is a weird one-off vote I'm about to hold, it could be misunderstood and need some 'tech support' to discuss it properly, let's wait until the weekend." It'd also give you more time to double-check the flavor- make sure that the conversation says what you want it to say. You could run it past a beta reader or something.
 
What you could do when you finish a post with a new type of vote on something important would be to just post the update, answer questions the next day (and perhaps open the vote if it wasn't already open) and only close the vote the day after that? If you feel like writing a post during the voting time you can probably do something like a captain's log, GBZ report, or results post, whoever is running the vote counter would need to explicitly specify the starting post instead of using threadmarks but that shouldn't be too much of an issue?

Problem is that that's still a long time for misconceptions to set in without corrective feedback.
 
2) The Hishmeri threat, being nomadic raiders and all, may move and threaten an adjacent area (perhaps even sector), and the task force assigned to defend against them would have to follow them, making stationary defense less useful.

I was under the impression that this fleet is specific to defending that one planet/region, not an all encompassing answer to the Hishmeri.

3) Stationary defenses effectively stake a claim to this area, which is something the Council is leery of doing until maybe the Qloathi join as a full member, or the Dawiar exit the Ashalla Pact.

Some people would say parking a 40D fleet in orbit is staking a claim as well.

4) If this stationary defense is to be constructed over the Ataami world, then there's a Prime Directive question here: although the Ataami have been exposed to external (and hostile) influences, if the Federation removes such influences, should the Federation remain in official contact to the point of allowing visible defenses to be constructed in the system? This falls into exceptional territory with regards to the Prime Directive, and there's no clear answer in my eyes.

I guess this is unanswerable until we know what the Council decides to do about that civilisation, my suggestion was predicated on if the federation is going to be uplifting them for the next few decades we might as well help ourselves by laying down infrastructure now.

OneirosTheWriter said:
Emergency construction isn't really an option there, the Snakepit has you stretched to the limit for those logistics.

Moving on then. I'm not sure I like the sound of the next snakepit though, I was hoping we could start laying the foundation for the Cardassian forward defence.
 
Last edited:
So there is a third tier of Cardassian Research available now, which has the same cost as the second tier and will presumably grant the same benefits, including a third Cardassian report. That probably means we will want to assign the Tiger Team to it (who will finish it in 6 years, boosts not very useful as even 5 boosts will only mean a 98% chance to finish it a year early), so we will probably want another foreign analysis team in the snakepit like @Briefvoice suggested(to finish tier 1 of Klingon Research and perhaps then T1 of Commonweath Research). Let's say Foreign Analysis/Xenopsychology because that's a combination that makes sense and we don't have yet. Also Xenopsychology is a field that we can rely on to be able to usefully employ this team if we somehow end up with too many foreign analysis teams. I don't particularly expect us to ever assign that team there, but you never know.
Tiger team will finish the first level of Klingon Analysis in 1 year which gets us a bonus intel report for them and would let us work towards looking into their new ship classes any new team will take 2 years. Also we should be getting a vote on the Gaeni team soon so that my cover it. Having said that if I am not missing anything we only have two teams with foreign analysis (Tiger Team and Games and Theory) with Generic Team 5 becoming a Comms/Foreign Analysis team in two years. So yeah I would be down for a third Foreign Analysis team at the next snakepit since as you mentioned we will be getting the ISC research as well. And with four areas with no known endpoint and Generic 5 possibly on comms and Games and Theory doing offensive doctrine work having a second team that can work foreign analysis would be useful.
 
Federation Broadcast Service : 2320s Long-Range Comms- +1 to response rolls is always nice (works well with Chen's bonus and mutual support as well), also increases distress call event rate, for me I am assuming that increases the chance a generated event is a distress call as opposed to more events
Logically speaking, it makes more sense that it's a flat increase in events, since what's actually happening is we're picking up distress calls from further away - so less are being missed.

I actually suspect this is how the quest's difficulty is going to "scale" as we improve our techbase and ships - the number of Easy DC events are going to remain the same or only be mildly boosted by these techs (or only be flat boosted by across-the-board boosts for events) whilst increases in event rates like this are going to be skewed towards higher DCs. It even makes sense - we're picking up distress calls from further away, which means that the situations have more time to deteriorate before we arrive.
 
Last edited:
So check this out based on the new Defense requirements.

Proposed 2317 Fleet Distribution


Amarkia Sector – Requires D7
  • Current - 1 Constellation (3) [Kearsage], 1 Centaur-A (3) [Zephyr] Starbase I (5), Extra Outposts (5) = 16D
  • 2317.Q3 - 1 Constellation-A (4) [Sappho], 1 Centaur-A (3) [Zephyr] Starbase I (5), Extra Outposts (5) = 17D
  • Notes: In 2317.Q3 Sappho arrives from refit, Kearsage goes into refit.
Ferasa Sector – Requires D10
  • Current - 1 Excelsior-A (6) [Endurance], 1 Centaur-A (3) [Bull], Starbase I (5) = 14D
  • 2317.Q4 – 1 Excelsior-A (6) [Endurance], 1 Constitution-B (5) [Defiant], 1 Centaur-A (3) [Bull], Starbase I (5) = 19D
  • Notes: No change.
Rigel Sector – Requires D7
  • Current – 1 Excelsior (6) [Avandar], 1 Constellation (3) [Selaya], Starbase I (5) = 14D
  • 2317.Q4 – 1 Excelsior (6) [Avandar], 1 Constitution-B (5) [Korolev], 1 Constellation (3) [Selaya], Starbase I (5) = 19D
  • Notes: No change.

With the GBZ losing 20D of ships, would it be possible to pull some ships from Amarkia, Rigel and Ferasa in Q3/4? or is it not worth it with the mission ending in Q4?
 
With the GBZ losing 20D of ships, would it be possible to pull some ships from Amarkia, Rigel and Ferasa in Q3/4? or is it not worth it with the mission ending in Q4?

It'd make Amarkia into a one-ship sector as far as I can see, which we want to avoid because those risk us failing to respond if those sectors get multiple events and that's costly for us.
 
With the GBZ losing 20D of ships, would it be possible to pull some ships from Amarkia, Rigel and Ferasa in Q3/4? or is it not worth it with the mission ending in Q4?

It would be possible, but Amarkia contains the Orion homeworld, Rigel sector contains the Honiani and the Yan-Ros, and Ferasa seems to hold damn near eveything. I'm reluctant to strip them down to one ship no matter what the nominal defense requirement is.

Of those, I'd be most comfortable pulling the Centaur-A from Amarkia if we really had to.

It'd make Rigel and Amarkia into one-ship sectors as far as I can see, which we want to avoid because they risk failing to respond if those sectors get multiple events and that's costly for us.

Right. I find it acceptable for Andoria and Tellar sectors because those don't contain any affiliates, just the one homeworld each.
 
Tiger team will finish the first level of Klingon Analysis in 1 year which gets us a bonus intel report for them and would let us work towards looking into their new ship classes any new team will take 2 years.
A new team would take 3 years unless we boost twice and get lucky (83% chance), but the Tiger Team would also need a boost to finish in 1 year. The next stage of Cardassian Research would be delayed by 1 year if we delay assigning the Tiger Team (from almost certainly 8 years to 9, whether we assign the new team for that year doesn't matter that much). Judging by the reaction of the thread last time someone proposed pausing Cardassian Research I don't think 1 year of Cardassian research for ~1.5 years of Klingon Research will be very popular.
 
Last edited:
The problem is that on weekdays I rarely get to update before late in the evening, so I'm not really around to support the discussion during the moratorium. So unless I restrict important voting posts to the weekends...?
Some votes could probably be announced a day ahead of time. Days:
  1. Story prompting Vote A (simple) goes up. Vote A (simple) opens. Story prompting Vote B (contentious) goes up. Moratorium on Vote B.
  2. Vote A closes. Story resolving Vote A goes up. Vote B opens.
  3. Vote B closes. Story resolving Vote B goes up.
I think you'd be around during the second half of the moratorium and during the second half of voting. This isn't quite as good as doing it on the weekend, since people could still have bad first impressions, but it's better than not being around at all.
 
It'd make Amarkia into a one-ship sector as far as I can see, which we want to avoid because those risk us failing to respond if those sectors get multiple events and that's costly for us.
Plus Amarkia Sector seems, informally, to be a magnet for 'double stack' events, PLUS it seems to be the location where (strangely enough) a lot of events related to the Sydraxian Civil War take place.

Some votes could probably be announced a day ahead of time. Days:
  1. Story prompting Vote A (simple) goes up. Vote A (simple) opens. Story prompting Vote B (contentious) goes up. Moratorium on Vote B.
  2. Vote A closes. Story resolving Vote A goes up. Vote B opens.
  3. Vote B closes. Story resolving Vote B goes up.
I think you'd be around during the second half of the moratorium and during the second half of voting. This isn't quite as good as doing it on the weekend, since people could still have bad first impressions, but it's better than not being around at all.
Well, the big problem is that you don't want to blow up the discussion of Vote A by having everyone fixate on Vote B. Like, you don't want the little practical questions of what to research getting entirely ignored because everyone's busy arguing about Starfleet peacekeepers.
 
A new team would take 3 years unless we boost twice and get lucky (83% chance), but the Tiger Team would also need a boost to finish in 1 year. The next stage of Cardassian Research would be delayed by 1 year if we delay assigning the Tiger Team (from almost certainly 8 years to 9, whether we assign the new team for that year doesn't matter that much). Judging by the reaction of the thread last time someone proposed pausing Cardassian Research I don't think 1 year of Cardassian research for ~1.5 years of Klingon Research will be very popular.
Ugh, I applied Lathris Doctrine bonus there, without that you are right we would need to boost it.


Tiger Team straight away (6 years at skill 5)
Best Case:8 years
Worst Case: 9 Years

Tiger Team After 1 year on Klingon Analysis (5 years at skill 5)
Best Case:8 years
Worst Case: 8 years

ISC Report (skill 2 for 4 years, skill 3 for 5)
Best Case: 6 years
Worst Case:6 years

ISC Report( skill 2 for 2 years, skill 3 for 5)
Best Case:5 years
Worst Case: 5 years with boost final year, 6 years without

ISC Report( skill 2 for 1 years, skill 3 for 5)
Best Case:5 years
Worst Case: 5 years


This is of course with no bonuses and no boosts. I think it is worth it, as depending on how our luck works out we could end up needing 9 years if we start straight away, and this way we get that Klingon tactical report a year or two sooner and at the same time get the ISC report that much sooner since we can start the new team working there right away.

ISC Report I looked at a skill team starting right away, finishes 6 years or after two years to finish Klingon research (assuming we got lucky) which is 5-6 years so 1 to 2 years more, and that is locking in two boosts as opposed to just one. If it ends up taking 3 years than we just get the ISC report in 5 years either way.

So Tiger Team+ Boost on Klingon-> Cardassian
New Team on ISC Report
Klingon: 1 Year
Cardassian: 9 years
ISC: 6 Years

Tiger Team on Cardassian
New Team Klingon-> ISC (boost Klingon twice)
Klingon: 2 years (3 years w/o boost)
Cardassian: 8 to 9 years (more likely to be 8 years)
ISC: 7 to 8 years (8 years w/o boost)

My preference her is to use Tiger Team on the Klingons as it requires one fewer boost (potentially two) and gets us two reports faster by 1 or 2 years each in exchange for a possible year delay on the Cardassians (who we already have 2 tactical reports and a 25% chance for a 3rd with listening posts) as opposed to two powers we have no tactical reports on, and the Klingons have two ships we need to do intel on as it is. At best the tiger team unlocks 1 years earlier at skill 6, the new team would be 1 to 2 years earlier guaranteed at skill 3.
 
Back
Top