lbmaian
a thirsty squirrel
- Location
- USA
One final question @OneirosTheWriter: now that we've launched our first Excelsior-A last year, does this mean that this now gets us 230br 160sr for an Excelsior-A, rather than 230br 150sr for an Excelsior?
To Boldly Go... (a Starfleet quest)
- Thread starter OneirosTheWriter
- Start date
- Sci-Fi
-
- Tags
- star trek exploration fully automated luxury gay space communism top level canon (canon) #hashtagcontent all-encompassing space amoeba cardassian boy bands cardassian magical girls darkest bureaucracy debate makes the qm cackle like palpatine hoh is an empire quest it has to be foreign infiltrators more ships ship happens singers delenda est starfleet this is not an empire quest ur waifu is collective?
One final question @OneirosTheWriter: now that we've launched our first Excelsior-A last year, does this mean that this now gets us 230br 160sr for an Excelsior-A, rather than 230br 150sr for an Excelsior?
- Location
- Australia
No, so I don't have to worry about rebalancing it.
I don't think it's really needed but here is a tally:
Vote Tally : Sci-Fi - To Boldly Go... (a Starfleet quest) | Page 2098 | Sufficient Velocity [Posts: 52467-52789]
##### NetTally 1.9.4
Task: COUNCIL
[X][COUNCIL] Plan ALL THE THINGS and KEPLER
No. of Votes: 41
[X][COUNCIL] Plan Drop Kepler and Ferasa Shipyard for Indoria Starbase
No. of Votes: 6
[X][COUNCIL] Plan develop no Kepler
No. of Votes: 1
[X][COUNCIL] Plan Even More Things and KEPLER
No. of Votes: 1
Total No. of Voters: 49
##### NetTally 1.9.4
Task: COUNCIL
[X][COUNCIL] Plan ALL THE THINGS and KEPLER
No. of Votes: 41
Plan: ◈ALL THE THINGS and KEPLER
Aeondrac
AKuz
Alastor Mobius Toth
aledeth
Ato
Briefvoice
Captain Hunt
CeBrudras
Chacmon
Chimeraguard
ClawClawBite
dacsan
Deathbybunnies
Gingganz
Goat
Godwinson
Gravitas Hunt
ilbgar123
Iron Wolf
Joshrand1982
karmaoa
KnightDisciple
LaggPlaguedDuke
Leila Hann
Mr Tebbs
MTB
Muramasa
Night
pbluekan
pheonix89
Random Member
random_npc
Shadows
Simon_Jester
SynchronizedWritersBlock
SyntheticTrevor
Theunderbolt
UbeOne
UberJJK
Vebyast
Winged One
Aeondrac
AKuz
Alastor Mobius Toth
aledeth
Ato
Briefvoice
Captain Hunt
CeBrudras
Chacmon
Chimeraguard
ClawClawBite
dacsan
Deathbybunnies
Gingganz
Goat
Godwinson
Gravitas Hunt
ilbgar123
Iron Wolf
Joshrand1982
karmaoa
KnightDisciple
LaggPlaguedDuke
Leila Hann
Mr Tebbs
MTB
Muramasa
Night
pbluekan
pheonix89
Random Member
random_npc
Shadows
Simon_Jester
SynchronizedWritersBlock
SyntheticTrevor
Theunderbolt
UbeOne
UberJJK
Vebyast
Winged One
[X][COUNCIL] Plan Drop Kepler and Ferasa Shipyard for Indoria Starbase
No. of Votes: 6
[X][COUNCIL] Plan develop no Kepler
No. of Votes: 1
[X][COUNCIL] Plan Even More Things and KEPLER
No. of Votes: 1
Total No. of Voters: 49
- Location
- Mid-Atlantic
Suffice to say that while the smallest Bird-of-Prey designs might well be thirty kilotons and have extremely minimal armament and be designed so a crew of half a dozen spacers that barely read Klingonese can operate them, there are so many different "Bird-of-Prey" sizes that it's kind of hard to make definitive statements. It's very likely in my eyes that the "Mark Two" Bird of Prey design is simply a physically larger craft built using similar technology and only slightly more advanced, for example. A reaction to the Klingons taking at least a partial step back from swarm doctrine and trying to design ships that can take on enemy frigates at 3:1 odds instead of 5:1 or something.
[Applies the "oh my" stamp of approval.]
Because it is really freaking expensive and we have a number of other high-priority major commitments to think about? We're spending 115pp on that industrial park, 40pp on an Academy expansion that is pretty much obligatory for now, and another 40pp on a resource infusion without which our build plan collapses and we lose the chance to build a new Enterprise-C for six years. That's just off the top of my head. On top of that we've got pushes, tech teams, starbases... It's not that the 70pp is undesirable, it's that we've got a lot else to spend money on.
I don't think you'll get much traction for this this year. Maybe next year when it's not competing with so many other things we want or need.
I'm not sure that's how threat works. Militarization points last, they don't go away. Ramping up Militarization when Threat is high can mean we suddenly appear hyper-militaristic and have political problems if the Threat subsides. And remember that our own successes can cause Threat decrease; low Threat is arguably a sign that we're keeping the Federation extra-safe.
What you're proposing strikes me as more like saying "It's summertime and warm outside, so I'm going to knock big holes in my walls for ventilation," and forgetting that later it's going to be freezing cold and those huge holes in the walls will become a serious problem.
Getting the option now versus next year just means we lose one intelligence report this year specifically. Some of the other options we're picking are significantly more time-critical (i.e. stopping the Ashidi from becoming stuck as a Cardassian affiliate if possible, getting our twin Ambassador prototypes up and running in a timely fashion without gutting our naval budget).
I agree that this is desirable but not critical. Once we have a little more information about the stance of our enemies, we should look into this. I'd actually rate it as more important than learning about the Klingon battleship. Just knowing it IS a Klingon battleship and roughly how big it is gives us a pretty good idea of how badass it is (very). And whereas we're likely to encounter these new Birds-of-Prey, we're very unlikely to encounter the Klingon battleships for quite some time, since they are likely to be deployed to the Romulan Front.
Last edited:
- Location
- alphen aan den rijn
[X][COUNCIL] Plan Even More Things and KEPLER
some minor thing i do not agree with but over all plan sounds good
some minor thing i do not agree with but over all plan sounds good
I guess we talked ourselves out yesterday. Okay, here's something to spur discussion. I'm figuring the next time we get to do a fleet distirbution vote will likely be in 2317.Q1, after Gaen joins the Federation and adds additional garrison results for Sol. Since the Licori Border Zone is apparently dropping to 9D requirement, here are my thoughts on a fleet redistribution. You'll see that I reinforce all the non-GBZ border zones... even the KBZ and RBZ, which I have wanted to get up to four ships for a long time now.
2317 Fleet Distribution
Fleet Strength Changes
2317.Q1 – (PROPOSED) Draw down Gabriel Expanse by 2 Constitution-Bs and 1 Centaur-A to reinforce other sectors. Draw down Licori Border zone by 1 Constitution-B and 1 Constellation to reinforce other sectors.
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 – Kumari [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
2316.Q3 = "Current".
Sol Sector – Requires D18 / Assume D21 on Gaeni Ascension
2317 Fleet Distribution
Fleet Strength Changes
2317.Q1 – (PROPOSED) Draw down Gabriel Expanse by 2 Constitution-Bs and 1 Centaur-A to reinforce other sectors. Draw down Licori Border zone by 1 Constitution-B and 1 Constellation to reinforce other sectors.
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 – Kumari [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
2316.Q3 = "Current".
Sol Sector – Requires D18 / Assume D21 on Gaeni Ascension
- Current - 1 Excelsior (6) [Pathfinder], 1 Centaur-A (3) [Lightning], 2 Starbase I (10) [Earth, Betazed] = 19D
- 2317.Q1 - 1 Excelsior (6) [Pathfinder], 1 Centaur-A (3) [Lightning], 1 Constellation (3) [Stalwart], 2 Starbase I (10) [Earth, Betazed] = 21D
- Notes: Stalwart comes from Licori Border Zone in 2317.Q1
- Current – 1 Constellation (3) [Docana], 2 Miranda (4) [Dryad, Calypso], Starbase I (5) = 12D
- 2317.Q1 – 1 Constitution-A (5) [Defiant], 1 Constellation (3) [Docana], Starbase I (5) = 13D
- 2317.Q3 – No change.
- Notes: In 2317.Q1 Dryad and Calypso go into refit, and the Defiant arrives from the GBZ.
- 2316.Q3 – 1 Constitution-B [Huascar], Starbase I (5) = 10D
- 2317.Q3 – No change.
- Notes: No change.
- 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.
- 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.
- Current - 1 Excelsior-A (6) [Endurance], 1 Centaur-A (3) [Bull], Starbase I (5) = 14D
- 2317.Q1 - 1 Excelsior-A (6) [Endurance], 1 Constitution-A (5) [Korolev], 1 Centaur-A (3) [Bull], Starbase I (5) = 19D
- 2317.Q1- No change.
- Notes: Korolev brought in from GBZ in 2317.Q1
- Current – 1 Excelsior (6) [Avandar], 1 Constellation (3) [Selaya] Starbase I (5) = 14D
- 2317.Q1 - 1 Excelsior (6) [Avandar], 1 Constitution-A (5) [Hood], 1 Constellation (3) [Selaya] Starbase I (5) = 19D
- Notes: In 2317.Q1 Hood arrives from Licori Border Zone..
- 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
- 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 Miranda-A (2) [Svai], 1 Oberth (1) [Inspire], Starbase I (5) = 17D
- Notes: In 2317.Q1, new Excelsior build in SF Berth A comes in and Excelsior goes into refit. Svai arrives from refit.
- 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
- Current - 1 Excelsior (6) [Salnas], 1 Oberth (1) [T'Mir], 1 Starbase I (5) [Lapycorias] = 12D
- 2317.Q1 - 1 Excelsior (6) [Salnas], 1 Centaur-A (Winterwind), 1 Oberth (1) [T'Mir], 1 Starbase I (5) [Lapycorias] = 15D
- 2317.Q2 – 1 Excelsior (6) [Salnas], 1 Renaissance (5) [Ana Font Berth 1], 1 Centaur-A (Winterwind), 1 Oberth (1) [T'Mir], 1 Starbase I (5) [Lapycorias] = 20D
- Notes: In 2317.Q1 the Winterwind sent here from GBZ. In 2317.Q2 Renaissance [Ana Font Berth 1] sent here after completion.
- Current – 1 Constitution-A (5) [Cheron], 1 Centaur-A (3) [Gale], Starbase I (5) [Vega] = 13D
- 2317.Q1 - 1 Constitution-A (5) [Cheron], 1 Centaur-A (3) [Gale], 1 Miranda-A (2) [Lion], Starbase I (5) [Vega] = 15D
- Notes: In 2317.Q1 Lion comes in from refit.
- 2316.Q3 - 1 Excelsior-A (6) [Sojourner], 1 Excelsior (6) [Kumari], 5 Constitution-B (25) [Korolev, Defiant, Exeter, Saratoga, Republic], 4 Renaissance (20) [Renaissance, UP Berth 1, UP Berth 2, UP Berth 3], 1 Centaur-A (3) [Winterwind], 11 Miranda-A (22) [T'Kumbra, Agile, Bantam, Clarion, Fidelity, Bon Vivant, Shield, Intrepid, Eketha, Eclipse, Firefly] = 95 C.
- 2317.Q1 - 1 Excelsior-A (6) [Sojourner], 3 Constitution-B (15) [Exeter, Saratoga, Republic], 4 Renaissance (20) [Renaissance, UP Berth 1, UP Berth 2, UP Berth 3], 11 Miranda-A (22) [T'Kumbra, Agile, Bantam, Clarion, Fidelity, Bon Vivant, Shield, Intrepid, Eketha, Eclipse, Firefly] = 75 C.
- Notes: In 2317.Q1, take the Korolev, Defiant, and the Winterwind out to reinforce other sectors, and Kumari goes into refit.
- Current/2316.Q3 – 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 to Rigel Sector and Stalwart to Sol Sector.
What actual proof do we have of the 9D requirement. I can't see that happening.
It's what's written on the front page as the Defense requirement, and just after the Snakepit vote was put up Oneiros said in reference to building a starbase in the LBZ:
I must presume it's gone back to a "normal" defense requirement now that the peace treaty has been signed at the Treaty of Gaen.
- Location
- Austin, TX
What's the refit schedule for next year? Could we delay any ships that are planning to do a refit by a year or so, to increase our forces by a bit?
- Location
- United States
i would much much rather take the some of the ships from down below and put them up above so that we have at least 2 ships in each sector.
maybe the Bull to Andor and the Hood to Tellar
Here's my thinking about Tellar and Andor sectors:
1. They have no "open borders" to non-Federation space, and any missed events in those sectors are likely to be not that important.
2. They contain only one Member homeworld each, and no affiliates.
3. Chen's bonus means that a cruiser has at least a chance to handle two events in those sectors.
On the other hand, Rigel Sector has been getting a lot of the Yan-Ros and Honiani events and is "open"... new species could show up there at any time. In fact, it will probably contain the Honiani as 300+ affiliates.
Ferasa sector contains the Caitians, the Seyek, the Qloathi, Risa, and a bunch of nomadic barbarian invaders on it's rimward border.
So yes, I don't think a two ship per sector even distribution is the best call.
- Location
- United States
unless the mechanics have changed without us being informed, all sectors have the same chance to spawn an Event.
Event chances are now based on the number of major worlds in that sector, I believe.
Excuse me, we have no confirmation that the nomadic invaders are not, in fact, operating off a recovered copy of the History of Rome podcast and therefore do not consider themselves barbarians.
Furthermore, they could be really civilized, like holding their pinky out when they lift a teacup and shit
Thors_Alumni
Proud member of Thors Class VII from Liberl
- Location
- Liberl Zemuria.
With our luck! Are you Kidding?! I wouldn't be surprised if they are hostile. if however they turn out to be like the Quarians of M.E. I will be very surprised. I have a soft spot for the Quarians even if some of them (The Admiralty board) are a bunch of whiners.
Last edited:
pheonix89
Wants to be Seven Of Nine
- Location
- North American Plaguelands
- Pronouns
- She/Her
Fairly sure you're correct.
I believe the specifics are something like
1 base roll.
1 roll per major world.
Possible additional border rolls?????
- Location
- United States
even still, i would rather have the second roll to respond in the lighter sectors than the third in the heavier. especially since we just got Chens bonus which will let ships potentially respond twice.
Just because they're not barbarians doesn't mean they can't be absurdly violent, and vice-versa!
#endthestigma
Forgothrax
Not Going Gently
- Pronouns
- He/Him
Given the need to staff the GBZ, it does make me wonder if we might want to hold off on the events-increasing tech from Forward Defense. Although the flipside of it is that the T3 version of it would offload events from the interior to the border zones, letting us staff the border zones more heavily and making single-ship coverage of the interior less of a problem (especially with Mutual Support).
- Location
- USA
@Briefvoice I would rather refit the Tarrak otherwise it would be 5 years before we could start it and we have no EC ships finishing this year
EC:
- USS Courageous, Excelsior-A-class, 2315-2320
- USS Sarek, Excelsior-class, Veteran, under going refit
- USS S'harien, Excelsior-class 2314-2319
- USS Odyssey, Excelsior-class 2313-2318
- USS Atuin, Excelsior-class 2314-2319
- USS Voshov, Excelsior-class 2315-2320
Tarrak would be 2317 to 2322. Otherwise if we push it back a year with a refit we can then use that same dock to refit the Odyssey in 2318. This would bump either the Excelsior or Kumari from the refit schedule this coming year, and the Plezarria would go and replace which ever one we bring into refit which will keep the GBZ stronger and still let us get 2 done that year. In 2318 we would have two refits finished and two new Excelsior-A done. At that point Odyssey would go in for refit and two of our garrison Excelsior would go in for refit to be replaced by the one new construction and one refit. I figure at that point we can keep rotating out two garrison Excelsiors, replaced by the ones finishing refit until all are in the A refit. EC ships would of course undergo refit as soon as they finish the 5 year mission, so some years we will have 4 Excelsiors undergoing refit (2 normal and 2 EC).
EC:
- USS Courageous, Excelsior-A-class, 2315-2320
- USS Sarek, Excelsior-class, Veteran, under going refit
- USS S'harien, Excelsior-class 2314-2319
- USS Odyssey, Excelsior-class 2313-2318
- USS Atuin, Excelsior-class 2314-2319
- USS Voshov, Excelsior-class 2315-2320
Tarrak would be 2317 to 2322. Otherwise if we push it back a year with a refit we can then use that same dock to refit the Odyssey in 2318. This would bump either the Excelsior or Kumari from the refit schedule this coming year, and the Plezarria would go and replace which ever one we bring into refit which will keep the GBZ stronger and still let us get 2 done that year. In 2318 we would have two refits finished and two new Excelsior-A done. At that point Odyssey would go in for refit and two of our garrison Excelsior would go in for refit to be replaced by the one new construction and one refit. I figure at that point we can keep rotating out two garrison Excelsiors, replaced by the ones finishing refit until all are in the A refit. EC ships would of course undergo refit as soon as they finish the 5 year mission, so some years we will have 4 Excelsiors undergoing refit (2 normal and 2 EC).
pheonix89
Wants to be Seven Of Nine
- Location
- North American Plaguelands
- Pronouns
- She/Her
Go for Mutual support, THEN the events shuffler. With Mutual support we put JUST enough ships in the interior sectors to meet D requirements, then allocate everything else to border zones as needed.
The event shift to border zones helps that even more because it means more rolls are proccing without the minus two.
Of course, we also need to set up a rimward frontier zone to get the bonuses that way, and we'll probably need to set up a coreward border zone because Yan-Ros/Honiani membership is going to take the LBZ and SBZ off the coreward frontier.
The event shift to border zones helps that even more because it means more rolls are proccing without the minus two.
Of course, we also need to set up a rimward frontier zone to get the bonuses that way, and we'll probably need to set up a coreward border zone because Yan-Ros/Honiani membership is going to take the LBZ and SBZ off the coreward frontier.
We now have two Defensive Doctrine teams. The new one we just purchased will presumably start at Skill 2.
I'm thinking this year we start it on To Boldly Go (the event increasing one). It should take 3 years to complete. In the meantime, the Admiral Lathriss team can finish Border World Focus this year, and go to Mutual Support next year. Because of the Lathriss's team's greater skill, it should take them only two years to complete Mutual Support. Then Mutual Support and To Boldly Go finish in the same year, nicely complementing each other.
So basically make the Tarrak a five year build, refitting it as soon as it's complete? I can see that.
Forgothrax
Not Going Gently
- Pronouns
- He/Him
See Briefvoice's post for my presumption on how things would go, but we will have 2 teams. The question is whether or not to hold off on the events enhancer entirely, but Mutual Support and the events+ are some of the best techs in the chain.
- Location
- USA
I can confirm that Lathriss team will only take 2 years to complete any of the Forward Defense techs without boosts except for Forward Logistics which is a single 50pt. Thanks to him giving a +2 to doctrine research the skill 2 team will take 3 years, no boosts needed. Originally we would have needed boosts the next two years on Lathriss to finish mutual support in 2 years (at which point he would level up) so his bonus saved us needing to boost research there.
And yeah it will be a five year build, on the flip side it will start operations as a Blooded A class which will make it more likely to pass events.
- Location
- Mid-Atlantic
We already voted to give the Tarrak a shot of Enterprise crew to put them at Blooded immediately. I'd rather NOT then delay their launch by a year to pile on even more bonuses; at some point we're just needlessly denying ourselves Explorer Corps assets. Refitting the regular garrison fleet Excelsiors is important too, especially since they're the ships that keep getting yanked into warzones.
We've already had "triple stack" events hurt us repeatedly in border sectors and heavily populated locations. With reason to expect all manner of drama in Ferasa Sector as the nomads approach, and on the Sydraxian border as we deal with the Sydraxian political issues and the Gretarians thinking about the merits of Federation affiliate status... I think we might want to avoid pinning down TOO much of our fleet on interior patrol duties.
I think we're safe leaving a lone modern cruiser to cover a sector with a single homeworld at least for a while. Obviously we don't want this state of affairs to last forever.
We've already had "triple stack" events hurt us repeatedly in border sectors and heavily populated locations. With reason to expect all manner of drama in Ferasa Sector as the nomads approach, and on the Sydraxian border as we deal with the Sydraxian political issues and the Gretarians thinking about the merits of Federation affiliate status... I think we might want to avoid pinning down TOO much of our fleet on interior patrol duties.