They stared at each other. Eventually, Yang looked away. "The Imperial Navy is supposed to be apolitical. Serve the state and only the state and no one else... not even each other," he said.
Only minor nitpick is they should probably say "Serve the Praetor," as per this quote in Nemesis:

"RIKER: The Praetor's power's always been the Romulan fleet. They must be behind Shinzon for him to have overthrown the Senate."

It implies the Praetor has special domain over the fleet. Or at least a solid connection.
 
Anyway, vote time. Lots of MWCO options this time around - I like :)

Comments on member fleet incomes:

As previously indicated, member fleets that advanced their mobilization level in the Arcadian crisis (UESPA, TSF, RDS from 100% peacetime to 125% early mobilization; VHC and BDF from 75% pacifist to 100% peacetime mobilization) haven't returned to their original economic mobilization levels just yet. But they'll likely do so starting from now.

Except the crazy Amarki staying with their limited 150% mobilization level. Heck, even if they were on peacetime mobilization, their income would still rival the Apiata's income. It may not be sustainable, but as long as they can establish new successful colonies in the GBZ, it'll pay off and their current "limited mobilization" could turn into their new "peacetime mobilization" economic levels. It already happened before in 2312 as a legacy of the Lironh bombing!

Other than that, incomes haven't changed at all. Not even the Apiata, which is a bit surprising because I would've thought their new GBZ mining colonies would've increased it.


Priorities:

As I pointed out, Betazoids already have a 2nd 1000kt berth and will struggle to fully utilize all their 5 berths with their paltry income, so the 'Change Betazoid Long Term Priority to "Second One-Megaton Berth"' vote doesn't make sense.
edit: Oh, the Betazoids are building Centaur-As. Huh, they and the Vulcans are actually the most likely to build them due to their near 1-to-1 BR to SR income ratios.

I thought about a Rigel budget increase, since they have the lowest resource to crew income rate in the whole Federation, but their priorities strongly imply that they're constrained by lack of raw resources, and thus they're expanding to address this problem.

I find it very interesting that the Apiata Amarki (edit: oops) effectively told us "we're not idiots, shove off" when last year, we voted to tell them to "focus more on cargo shipping". Because they were already crash building more cargo ships and did not drop their "Riala-A '17" priority at all. In fact, they jumped ahead on prioritizing new frigate classes (which were voted on in the SDB thread). Let's not annoy them again this year, m'kay? ;)

Andorians and Apiata are struggling to find ways to use up their growing crew pools. Apiata in particular - they have a whopping 52 enlisted!! The Apiata are addressing their resource to crew ratio imbalance by developing in the GBZ. But the Andorians don't have such an out. They're already in a rut with overdeveloping Centaur-As instead of saving for Renaissances (they're only building one). There's nothing else they can do except invest in resource income development, which it looks like they're already planning to do. And the fact they're aiming for mine development instead of budget increase indicates that they can't feasibly do the latter.

Finally, Humans - poor guys. They actually only lost a single Miranda last year, but they also need to recover from all the casualties and ship damage costs. UESPA now has the 2nd weakest member fleet out of the whole Federation, dropping down from a tie of 3rd weakest with the Andorian Guard last year. They're even below the Vulcans now! Fortunately, they have they the 3rd strongest income (or 4th, if Rigel ever had a resource surplus), so they should be able to catch up.

In conclusion, I can't find any priority that obviously needs changing this year.

[ ][PRIORITY] Change nothing [Weighted 1.5x]


No-brainers:

[ ][GAENI] 100sr for 150br
[ ][REN] Endorse the tech transfer


Cats:

Let's not mess up the standard Caitian battle group in their GBZ force. They have 4 Fatherships and 14 Modern Swarmers, with 2 more of the latter on the way. That implies that their standard formation is intended to be 1 Fathership + 4 Swarmers. (Contrast that with the Apiata [Little] Queenship + 2 Stinger battle groups.)

[ ][CATS] 1 Fathership, 4 Swarmers


Bees:

First off, the Apiata's need for a Stinger replacement is less important for the overall health of the Federation than helping the developing Orion Union. Well, the Qloathi are also an option, but there's no evidence that they're struggling like the Orions.

Additionally, the development of a Heavy Stinger that would utilize more BR would require a >600kt design, which would in turn require upgrading most of their berths which are 600kt in size. That's a very large and non-obvious investment.

[ ][BEE] Exchange resources with the Orion

The Apiata may have 1 2500kt and 6 600kt free berths and an impressive treasury of 315br 130sr and income of 165br 115sr, but they still can't populate all those berths with new Stinger builds. Starting this year, they can only afford to start 2 Stingers or Foragers per year. Meanwhile, I think they're already building two Bumblebees (cargo ship) and a Dorsata (super freighter), so it's not likely they'll be starting new auxiliary builds this year; at most just one more auxiliary.

So asking to use 2 of their 600kt berths for cargo ships should be of minimal burden to them. It would still leave 2 600kt and 1 2500kt berths free for repairs, not to mention the repair yards that have been built in the GBZ. And with how deep in the hole we are with logistics, 8pp is a worthy investment for 2 more cargo ships.

[ ][LOG] Start 2 Starfleet Cargo Ships at Irrizizza for 8pp


Dings:

While I still think its important to improve the less experienced EC Excelsiors to improve early overall event non-failure rates for compounding rewards/non-failures, along with greater survival of our greenies, and I will grant it needs to be balanced against experience efficiency. I'm also amenable to the idea that we need one elite flagship for those rare yet critical occasions we can direct important EC missions.

Of the veteran candidates to make elite, there's Sarek and Courageous. Sarek is closer to dinging then Courageous, and I'm a bit tired of the Courageous blowing up, so Courageous it is.

On the less experienced side, the completely green yet-to-launched Tarrak is in. Green Voshov is another candidate, but it looks like she's going to level up soonish anyway. That leaves one of the blooded EC ships to level up. The just dinged Odyssey would be the obvious candidate.

...but I'm gonna do a 180 here and vote for something outside the box Federation:

[ ][ENTER] Send the survivors to existing ships
-[ ] USS Courageous, USS Tarrak, USS Stargazer

:D


Scientology:

I agree that sending an Explorer Corps ship should be sufficient for handling the Caldonian issues, and since she would still have quarterly events, it won't incur an opportunity cost. That obviates the need for pp-expensive Andorian Guard reinforcements, and they would be an unnecessary provocation anyway.

The question of which ship to send boils down to either Odyssey or Voshov. Odyssey would have better bonuses, including the crew rating. However, there's a decent argument that the Caldonian situation is relatively safe and unimportant. The latter because we have a shitload of member ratifications upcoming anyway. But on the other hand, a Caldonian crisis right on the Klingon border and the escalations that could provoke could be very destabilizing.

[ ][CAL] Ignore
[ ][EC] Pick an Explorer Corps ship to carry this out: USS Odyssey


Collated vote:

[X][PRIORITY] Change nothing [Weighted 1.5x]
[X][CAL] Ignore
[X][EC] Pick an Explorer Corps ship to carry this out: USS Odyssey
[X][LOG] Start 2 Starfleet Cargo Ships at Irrizizza for 8pp
[X][GAENI] 100sr for 150br
[X][CATS] 1 Fathership, 4 Swarmers
[X][REN] Endorse the tech transfer
[X][BEE] Exchange resources with the Orion
[X][ENTER] Send the survivors to existing ships
-[X] USS Courageous, USS Tarrak, USS Stargazer
 
Last edited:
Public Spreadsheet Index
Spreadsheet index:

Official:
ToBoldlyGo CustomShipWorkbook2 [ask @OneirosTheWriter for a link in a personal conversation]
Maintainers: @OneirosTheWriter, @lbmaian, @SynchronizedWritersBlock
Function: Custom design of new ship classes, also used for other our members, affiliates and other powers (though they can have their own parts with different stats).
Completeness: Complete with regard to currently existing rules because it defines what those are. Inclusion of future parts varies. Secret parts used by other powers not included.
Currency: Marking of parts as currently unavailable may reflect the state at the start of a design process rather than the latest in game date.
Usage:
Copy the whole spreadsheet if you want to work without interfering with anyone. You can try out some things on the main sheet if no one else is currently using it, or copy only the main sheet if you want your design to be immediately accessible to others, but be aware that this might cause slowdowns for everyone and be sure to delete any sheets that you don't need anymore as soon as possible. Also see Sci-Fi - Starfleet Ship Design Bureau ("To Boldly Go...")

Starfleet Economy [used to be available through ShipWorkbook, currently no officially sanctioned way of getting the URL? You could ask Oneiros.]
Maintainer: abandoned?
Function: tracking Starfleet logistics and assessing freighter needs.
Completeness: ???
Currency: Seems to have been abandoned?
Usage: Difficult to even understand what any of it means.

Semi-official:
Database for To Boldly Go
Maintainer: @anon_user
Function: Track characters, ships and planets.
Completeness: Tries to be complete vs actually available data, but of the data that would belong there is currently unavailable.
Currency: Updated very frequently, often multiple times a day.
Usage:
Information sheet. Mark characters you wish to be tracked in rat-race posts in yellow. If you came up with a character you might want to add missing details, particularly year of birth.

Boldly Go Shipbuild
Maintainer: @Briefvoice
Function: Planning ship building and berth usage, also Starfleet fleet strength projections.
Completeness: Usually complete for the next year or two and for mile stones like prototypes, builds several years down the line usually don't represent concrete plans but placeholders to access possible crew and/or resource shortages.
Currency: Reliably updated well before the ship building phase, essentially always up to date regarding our plans because it largely defines what those plans are, but plans can and do change on short notice.
Usage:
Information sheet, copy the spreadsheet if you e. g. want to propose a plan of your own or play around with resource income assumptions.

ToBoldlyGo Audit Ledger
Maintainer: @lbmaian
Function: Track income and help double-check for the official EOY reports.
Completeness: Generally complete, missing data is rare.
Currency: Generally up to date in time for EOY reports.
Usage: Information sheet.


Unofficial:
To Boldly Go Council Members
Maintainer: @aeqnai
Function: Overview of the composition of the Federation Council
Completeness: Complete
Currency: Updated for the 2314 election, which should make it up to date until 2317.
Usage: Information sheet.

To Boldly Go Ships & Deployments
Maintainers: @aeqnai, @Vebyast
Function: Tracking and playing around with deployments, viewing aggregate stats of task forces/fleets
Completeness: ???
Currency: ???
Usage: Probably best to copy the spreadsheet if you want to avoid interfering with other people?

Boldly Go Shipyards
Maintainer: @Briefvoice
Function: Federation-wide overview of shipyard berth sizes.
Completeness: Complete for Starfleet and full members, incomplete data for affiliates.
Currency: ??? (seems reasonably up to date as of 2316.Q1)
Usage: Information sheet.

To Boldy Go - Event Analysis
Maintainer: formerly @SynchronizedWritersBlock
Function: Analyzing event types and factors that seem to have played a role in determining outcome.
Completeness: Based on event text, which may obscure what kind of rolls happened behind the screen in unpredictable ways.
Currency: up to date to 2312.Q2
Usage: Information sheet.

Boldly Goes-Member and Affiliate Fleets
Maintainer: @Void Stalker
Function: Track Starfleet, member and affiliate fleet strength.
Completeness: ??? (seems reasonably complete as of 2316.Q1)
Currency: Usually updated after quarterly MWCO reports.
Usage: Information sheet.

To Boldly Go-Neutral and Great Power Fleets
Maintainer: @Void Stalker
Function: Track fleet strength of other powers.
Completeness: Limited by available intelligence data.
Currency: Marked on the sheet.
Usage: Information sheet.

To Boldly Go-Civilian-Member and Affiliate Fleets
Maintainer: @Void Stalker
Function: Track civilian fleet strengths.
Completeness: ???
Currency: Usually updated after quarterly MWCO reports.
Usage: Information sheet.

To Boldly Go- Part and Frame Unlock
Maintainer: @Void Stalker
Function: Allow looking up the technologies that unlock a specific part, rather than the other way round.
Completeness: Complete for parts actually listed in the research megapost
Currency: ???
Usage: Information sheet.

To Boldly Go - Logistics Projections
Maintainer: @nocarename
Function: Plan future logistic ship requirements.
Completeness: Takes all known components of the logistic requirements into account.
Currency: ???
Usage: Information sheet.

Ship crew
Maintainer: @anon_user
Function: Tracking what named characters served on which ship when
Completeness: ???
Currency: ???
Usage: Information sheet, you can also add missing info yourself. Certain positions are color-coded.

Boldly Go Logistics Tracker
Maintainer: @SynchronizedWritersBlock
Function: Provide an estimate of how many logistics ships we need about 3-4 years into the future.
Completeness: ???
Currency: ???
Usage: guide
 
Last edited:
I don't know if crewing Stargazer with Enterprise personnel makes any sort of sense, @Ibmaian , but otherwise that looks like solid reasoning.
To Boldly Go Council Members
Maintainer: @aeqnai
Function: Overview of the composition of the Federation Council
Completeness: ??? (appears to be complete)
Currency: Updated for the 2314, which should make it up to date until 2317.
Usage: Information sheet.
That sheet is complete, yes, and Oneiros went through and added all the data I didn't have a couple Snakepits ago. Also I made this:
To Boldly Go Ships & Deployments
(credit to @Vebyast for a lot of the fiddly coding work)
 
Last edited:
Boldly Goes-Member and Affiliate Fleets
Maintainer: @Void Stalker
Fuction: Track Starfleet, member and affiliate fleet strength.
Completeness: ??? (seems reasonably complete as of 2316.Q1)
Currency: ??? (seems reasonably up to date as of 2316.Q1)
Usage: Information sheet.
Other Void Stalker spreadsheets:
To Boldly Go-Neutral and Great Power Fleets
To Boldly Go-Civilian-Member and Affiliate Fleets
They all tend to be updated at the same time.

I don't know if crewing Stargazer with Enterprise personnel makes any sort of sense, @Ibmaian , but otherwise that looks like solid reasoning.
Yeah, it's a throwaway joke vote. The "USS Courageous, USS Odyssey, USS Tarrak" vote has an insurmountable lead. Just wanted to mention the Stargazer again -_-
 
Well more along the lines that the both member and affiliate fleets get updated every quarter whenever we get the posts with commissioned or commenced ship buildings. neutral and greatpower tends to be updated during the well they try. I added dates into the neutral and great power fleets so people will now the last time we had information on them.
 
You have so many original characters that I couldn't tell who your character would be, but comment-wise, you sure seem to like Eddie Leslie and the [spirit of] Enterprise a lot :p
They're the two who have fun things to say about stuff most often. Besides them, there's Lt. Bessle whose main schtick is being very passionately convinced of things that are an interesting mix of true and false, and Halkh. I can't think of anyone else off the top of my head in my half-dazed state.

Only minor nitpick is they should probably say "Serve the Praetor," as per this quote in Nemesis:

"RIKER: The Praetor's power's always been the Romulan fleet. They must be behind Shinzon for him to have overthrown the Senate."

It implies the Praetor has special domain over the fleet. Or at least a solid connection.
Perhaps in the 2310s they made a clear distinction between the two? Or perhaps in the minds of Romulan navy officers, they are serving the state and not just fanatically loyal to a single individual? I mean, I'll trust the consensus of the People What Know More. But Romulus isn't as, for lack of a better term, feudal, as... say, the Klingons.

Priorities:

As I pointed out, Betazoids already have a 2nd 1000kt berth and will struggle to fully utilize all their 5 berths with their paltry income, so the 'Change Betazoid Long Term Priority to "Second One-Megaton Berth"' vote doesn't make sense.
It made sense in the context of me going to a page I commonly use(d) as a lookup table of shipyard facilities, that happened to be 6-7 years out of date, and goes back to a time before the Betazoids constructed that second one-megaton berth.
 
Aight, I did some revisions to my list:

Oneiros: Commander, Starfleet
Nix: Rear Admiral, Starfleet Explorer Corp/Supreme High Technocrat, Illuminated Technocracy of Gaen
Briefvoice: Vice Admiral, Starfleet Shipyard Operations
UbeOne: Vice Admiral, Starfleet Ship Design Bureau
anon_user: Rear Admiral, Starfleet Personnel
SWB: Vice Admiral, Starfleet Intelligence

Like, I've spent enough time working the ship design sheet that I've had to learn research out of necessity. I couldn't tell you the odds or times on boosts or anything unless they were blindingly obvious, but I might maybe be able to sketch out a research plan with an hour or two of work.

Nix does that every in-game year, complete with probabilities. I can only assume he has a spreadsheet or program to crunch the numbers for him because while doing the research teams by hand is possible, the inspiration bonus would be way too much work if it's not automatically calculated.

I am not sure if the fact that the quest has grown so complex that only a handful of people understand its core-mechanics is a good thing or something to be proud of. I am currently re-reading the quest and in my eyes it is quite depressing to see how its decision making and voting process grows ever more exclusive with every revision adding even more complexity to it, with nowadays it being pretty near impossible to actually make an indepedent decision in any part of the quest without spending several hours researching the material. A quest that relies so heavily on write-ins/plans like this has always a tendency to move towards a "council" like style (since the number of players that have the time to actually to do the work requried is relatively low) but at beginning you had at least some opportunities to parcipate which have nearly all disappeared which is quite sad im my opinion.
 
I am not sure if the fact that the quest has grown so complex that only a handful of people understand its core-mechanics is a good thing or something to be proud of. I am currently re-reading the quest and in my eyes it is quite depressing to see how its decision making and voting process grows ever more exclusive with every revision adding even more complexity to it, with nowadays it being pretty near impossible to actually make an indepedent decision in any part of the quest without spending several hours researching the material. A quest that relies so heavily on write-ins/plans like this has always a tendency to move towards a "council" like style (since the number of players that have the time to actually to do the work requried is relatively low) but at beginning you had at least some opportunities to parcipate which have nearly all disappeared which is quite sad im my opinion.
Well, at least some part of this ties back to fifteen in game years of history being behind most of the decisions. There are probably a number of areas that could be simplified, but some of it can't be avoided.
 
I am not sure if the fact that the quest has grown so complex that only a handful of people understand its core-mechanics is a good thing or something to be proud of. I am currently re-reading the quest and in my eyes it is quite depressing to see how its decision making and voting process grows ever more exclusive with every revision adding even more complexity to it, with nowadays it being pretty near impossible to actually make an indepedent decision in any part of the quest without spending several hours researching the material. A quest that relies so heavily on write-ins/plans like this has always a tendency to move towards a "council" like style (since the number of players that have the time to actually to do the work requried is relatively low) but at beginning you had at least some opportunities to parcipate which have nearly all disappeared which is quite sad im my opinion.
There are quite a lot of non-plan based votes. Very few of them require any deep understanding of the mechanics, many don't even have any explicitly spelled out mechanical effects, others something relatively simple like a pp cost. In other cases the mechanical merits of either choice are being debated and you basically just need to follow the discussion.

Right now of the 9 ongoing votes one requires serious background knowledge (the priority change vote), one requires some rough idea about how experience and events work (the crew distribution vote), one requires knowing where to find ship stats, but the others only require very basic information like that we have an SR shortage relative to BR, that pp are good or who the Caldonians are. So 1 high threshold, 2 medium and 6 low threshold votes. The round before that was 1 plan vote, 1 medium, 2 low and 3 zero threshold votes.

Sure, there is a very high threshold for being able to propose a plan of your own for votes that are plan based, but that's far from the only way you can participate.
 
I suspect if someone died in a car crash we could probably work this stuff out, it's just, somebody is already working this stuff out, so the rest of us get to just vote.
 
Priorities:

As I pointed out, Betazoids already have a 2nd 1000kt berth and will struggle to fully utilize all their 5 berths with their paltry income, so the 'Change Betazoid Long Term Priority to "Second One-Megaton Berth"' vote doesn't make sense.

edit: Oh, the Betazoids are building Centaur-As. Huh, they and the Vulcans are actually the most likely to build them due to their near 1-to-1 BR to SR income ratios.

God damn it! Is there a place where this is written down?

I'll go back and edit my vote again and go back to 'Betazoids switch from Centaur-As to Constellation-As.'
 
Last edited:
Only minor nitpick is they should probably say "Serve the Praetor," as per this quote in Nemesis:

"RIKER: The Praetor's power's always been the Romulan fleet. They must be behind Shinzon for him to have overthrown the Senate."

It implies the Praetor has special domain over the fleet. Or at least a solid connection.

To which I would reply:

"I'm a student of history, and it amazes me how people can think that the way things are today is the way that things have always been. Even people who lived through the past themselves! Fifty years ago, things really were different.

Sure Riker. "Always."
 
How many species are ready to join the federation now or in the immediate future.
 
Back
Top