Edit: Basically, unless the Cardassians get cloaks or mentats, I wouldn't count on there being support for putting Keplers on the battle lines

We're not talking about using them in the main battle line. We're talking about using them in the Minefield, Scouting, and Skirmish phases where S is important.

You want a non-Kepler for those phases? Go to Starship Design Bureau and build a refit for the Miranda or Centaur.
 
Last edited:
In other news, the Apiata have given a proper name to the 2 Dorsata site, naming the system Apruzza, which I am told is a term indicating the regrowth of "spring" among those planets which have a winter-time.
So if 2 Dorsata is now know as Apruzza...
Apiata Workerbee Team - Developing Mining Colony on Apruzza IX - ETC 2317.Q3
Apiata Colony Team - Developing Mining Colony on Apruzza IX - ETC 2317.Q3
-Apiata Task Force- Defending Apruzza (33 Dorsata)
[Apiata Mining colony on 2 Dorsata is operational]
...why is 33 Dorsata (the double SR colony site system) being called Apruzza here?

[Miele Subsector/Subsector 1e is now fully explored]
Isn't Dorsata (along with Camden) subsectors also follow explored, or at least "prospected"?


Up to 2 Cargo Ships may be scheduled for 2yr builds for free, with each additional costing 5pp
Up to 1 Freighter may be scheduled for 3yr builds for free, with each additional costing 5pp
Up to 1 concurrent Super-freighter may scheduled for 4yr builds for free, with each additional costing 10pp

Ouch, with this type of cost, I'm no longer so willing to go with the original 1 E-A, 5-7 Rennie, 2-3 Constie-A plans, because those relied on being able to build 2 super-freighters concurrently to match the aux builds of the 2 E-A, 4-5 Rennie, Constie-A plans.

10pp for a super-freighter... I may think that we're already building enough Excelsiors (would total 9 concurrent explorer builds/refits with the 2 E-A plans), I don't disagree with it enough to say its worth 10pp.

Has anyone proposed Nix's variant of Briefvoice's plan?

For this plan we could move the Miranda refit from 40EA-1 to Lor Vela-A (delaying the Excelsior refit there for 1 quarter) and move the Renaissance planned for Q1 2318 in 40EA-1 up a year. Advantages:
  1. We'd get a Rennie a year earlier.
  2. 40EA-1 would be open for 9 quarters before building the first production run Keplers, allowing to fit in an extra auxiliary ship.
  3. The Excelsior refits in Lor Vela would be aligned with the year, alleviating the tendency for SR to drop low in Q4 of some years and possibly allow us to squeeze in an extra ship in the next few years.
  4. The Exelsior that would be refit (clearly not an EC ship) can stay in service for an extra quarter.
  5. No gap before the USS Excelsior, fresh from refit, can replace it, simplifying deployment plans (or smaller gap before the new Excelsior form UP-A can replace it, if the Excelsior planned to be refit at Anna Font starting in 2318.Q1 is also a non-EC ship).
Disadvantages:
  1. We get an Excelsior-A a quarter later.
  2. None of our berths are free for repairs.
  3. Smaller resource stockpile available for repairs this year (but 63SR in Q4 is still not that bad all things considered, and we've done pretty well with resource collection recently so there's a good chance we'd have more than that).
(f) 2317 Boldly Go Shipbuild [2 EXA, 1 EXR, 5 RN, 2 CLA, 3 free 1mt, 1 free 3mt]
Ambassador: 2 continuing builds
Excelsior-A: 2 new builds, 2 continuing builds, 1 new refit
Renaissance: 5 new builds, 2 continuing builds
Constellation-A: 2 new builds, 2 new refits, 2 continuing refits
Miranda-A: 1 continuing build, 2 new refits
Free berths for auxiliary builds: 3 1mt (recommended: 2 cargo ships, 1 freighter), 1 3mt (recommended: 1 superfreighter)

(sorry, posting this from shitty tablet and it's a total pain to browse with)
 
Assuming I'm reading it right, it is basically drop an Excelsior-A, add a Rennie, rearrange to fit berths compared to the current BriefVoice plan.

Would set up a slightly larger resource stockpile for next years plans, but given Starfleets love of big ships (we get pp for building them now) and the threads tendencies to usually follow BriefVoice on these votes I do not expect it get much traction.
 
Do we know what happened to Scotty in this verse? I ask because I ran across a gif of Scotty at the Holodeck asking to see the bridge of his old ship the Original Enterprise no bloody A, B, C, or D. on a Kantai Worm crossover thread on Spacebattles.
 
Do we know what happened to Scotty in this verse? I ask because I ran across a gif of Scotty at the Holodeck asking to see the bridge of his old ship the Original Enterprise no bloody A, B, C, or D. on a Kantai Worm crossover thread on Spacebattles.
That was an episode of The Next Generation, in which Scotty had crashed in a remote location (in 2294 or so) and improvised a trick with the transporter to put himself in suspended animation for seventy-five years. The crew of the Enterprise-D found him (in the 2260s or early '70s).

So from the point of view of TBG, Scotty is "missing, presumed dead," just like Kirk.
 
Do we know what happened to Scotty in this verse? I ask because I ran across a gif of Scotty at the Holodeck asking to see the bridge of his old ship the Original Enterprise no bloody A, B, C, or D. on a Kantai Worm crossover thread on Spacebattles.

In Cannon he went into uncharted space and disappeared sometime between the TOS movies and TNG. His ship crash landed on a Dyson Sphere so he preserved himself in a transporter buffer until someone (Enterprise D) could respond to his distress beacon.

So from the point of view of TBG, Scotty is "missing, presumed dead," just like Kirk.

Wasn't he chief engineer on one of our Excelsiors or the Cheron?
 
That was an episode of The Next Generation, in which Scotty had crashed in a remote location (in 2294 or so) and improvised a trick with the transporter to put himself in suspended animation for seventy-five years. The crew of the Enterprise-D found him (in the 2260s or early '70s).

So from the point of view of TBG, Scotty is "missing, presumed dead," just like Kirk.
And if we do find Scotty early expect to get a resource sink garrisoning and investigating the episode mcguffin.
 
That was an episode of The Next Generation, in which Scotty had crashed in a remote location (in 2294 or so) and improvised a trick with the transporter to put himself in suspended animation for seventy-five years. The crew of the Enterprise-D found him (in the 2260s or early '70s).

So from the point of view of TBG, Scotty is "missing, presumed dead," just like Kirk.
Unlike Kirk, though, he's only one very lucky EC event from being found again at any time. Then again, I'd hate to find out how an Excelsior deals with an event roll that was hard even for the Galaxy-class Enterprise.
 
Unlike Kirk, though, he's only one very lucky EC event from being found again at any time. Then again, I'd hate to find out how an Excelsior deals with an event roll that was hard even for the Galaxy-class Enterprise.

All contact lost with Courageous
...
Searchers found hull material with indications that she ran into something
...

(Head on with a Dyson Sphere that evidently has crazy stealth if no-one can find the thing. And of course its Courageous that fails, as it needs to continue it's record of getting beat up everywhere)
 
And if we do find Scotty early expect to get a resource sink garrisoning and investigating the episode mcguffin.
They should have done another episode investigating that Dyson Sphere. Hell we could have had an entire story arc just so we could explore the thing before the Enterprise moved on to another assignment. Scotty could have been found anywhere else. In game if we find that thing early we will have a massive source of BR/SR/RP to mine for future construction elsewhere.
 
Wasn't he chief engineer on one of our Excelsiors or the Cheron?
Scotty was chief engineer of the USS Excelsior during the events immediately after Wrath of Khan and prior to Search for Spock. He ended his tour of duty on Excelsior by sabotaging the ship so it wouldn't be able to catch up with Kirk when he (accompanied by Scotty) stole the Enterprise to go resurrect Spock.

Scotty appeared as chief engineer of the Enterprise-A in both The Final Frontier and The Undiscovered Country, which together cover most of the beginning and end of the Enterprise-A's career. We can be pretty sure he didn't serve aboard the Enterprise-B because he wasn't there in Generations.

There is no compelling reason to assume he ever served aboard Cheron, Courageous, or Sarek, since those ships didn't exist in canon and there are no obvious 'holes' in Scotty's career to suggest service on one of those ships.

They should have done another episode investigating that Dyson Sphere. Hell we could have had an entire story arc just so we could explore the thing before the Enterprise moved on to another assignment. Scotty could have been found anywhere else. In game if we find that thing early we will have a massive source of BR/SR/RP to mine for future construction elsewhere.
Conversely... that the Dyson Sphere in that episode never showed up again in a prominent role, it would be reasonable to assume that FOR SOME REASON (rolls eyes), it did not have a major effect on TNG/DS9-era Starfleet. In which case it's probably not a huge BR/SR/RP source after all. So no, no magic windfalls for us.
 
I wonder when we'll get the first temporal anomaly that involves a ship coming through from the future, rather than our ships ending up in the past.
 
I wonder when we'll get the first temporal anomaly that involves a ship coming through from the future, rather than our ships ending up in the past.
The canon crews never went to this time period onscreen, but that doesn't entirely rule out the possibility of seeing them. Still, if there's a time travel ep where we're the past, I'd bet more on the Enterprise-C or interdimensional shenanigans being involved as well (so as not to railroad us into the course of action required to make the time travelers exist in the first place).
 
An early Captain's Log featured the chief engineer of a starship speaking in Scottie's accent.
Yeah well, there are a lot of Scotsmen. Not all of them are Montgomery Scott, former chief engineer, USS Enterprise.

I wonder when we'll get the first temporal anomaly that involves a ship coming through from the future, rather than our ships ending up in the past.
Those are the ones Temporal Affairs hushes up really hard and doesn't tell us about.

But wait, you ask, why would the commander of Starfleet not be informed about an event involving future Starfleet actions? When you think about it, the answer is obvious: the person who makes constant day-to-day critical decisions affecting the future of Starfleet is the LAST person you want to expose to the butterfly effect.

Suppose someone had told Admiral Sousa about the recurring 'ship of aeons' incident involving the Enterprises and the Aga Carmide system early in her tenure. It is fairly likely that at some point during her admiralty, Sousa would have given different orders as a result. Say, because she believes the Enterprise-B has to be kept safe at all costs, in order to avoid a temporal paradox. Thing is, those same orders would alter the history of the Enterprise-B herself.

And then the ship's history would change. Say, Enterprise might not have been assigned to lead Task Force 2, because risking the ship in battle might result in losing her before she went to Aga Carmide. But then the Battle of the Ixaria Approaches would never happen, or happen differently, because even with Nash present, Enterprise being absent would have had effects. The emperor might have survived and wound up in captivity, or survived and escaped. Betarre might never have been motivated to rewrite history. Paradox!

It's a classic example of the old 'Oedipus's prophecy' scenario: by knowing in advance what is going to happen, you take steps that distort events in ways you never would have wanted, resulting in a tragedy that confirms (or worse yet, destroys) the future you thought you had.

...

So basically, if you tell the admiral commanding Starfleet information that gives detailed information about the future of Starfleet, and you have to worry about cause and effect leading to temporal paradoxes... You're creating a situation where things have a lot of potential to get screwed up, unless the admiral commanding Starfleet never acts on the knowledge you've given them.

Much better to just never tell them what happened, or only tell them what happened after the event is safely "over" and the ship from 'the future' has returned home to its own timeline.

Thus, for instance, it may well be that Admiral Sousa was the first commander of Starfleet ever to know what happened at Aga Carmide back in the Miocene. Telling any of her predecessors, or telling Sousa herself at any time prior to when the Enterprise-B flew into a time portal and never came back out, could have led to paradox.
 
Last edited:
So we'd get something like...

USS Whomever, Captain's Log, Stardate, Pick a number
Mapped a star today. Nothing interesting happened at all.
Personal Log, Stardate, Pick a number.1
Well, at least I keep my hair. That's nice.
+5RP, Don't break the timeline. Yet at least.
Then it turns out Future Picard was wearing a wig, because he just didn't have the heart.
 
Assuming I'm reading it right, it is basically drop an Excelsior-A, add a Rennie, rearrange to fit berths compared to the current BriefVoice plan.

Would set up a slightly larger resource stockpile for next years plans, but given Starfleets love of big ships (we get pp for building them now)

In the long run, it doesn't change quantities of ships - it just shifts a Rennie build 4 quarters earlier, and delays an Excelsior refit by a quarter.

It basically has no serious downsides that I can see. It technically slightly deviates from the trailing end of the fleet distribution, but such votes should seriously not restrict shipyard op votes.

If I had the time (edit: or rather, proper equipment), I'd propose and advocate it.

and the threads tendencies to usually follow BriefVoice on these votes I do not expect it get much traction.

Eh, I'd like to think the voters are doing critical thinking rather than "appeal to authority". If it does turn out that the vote is getting so complex that voters are mostly delegating - and I really hope that's not what's happening here - then this doesn't bode well for these types of votes going forward. Because they're going to get more and more complex as Starfleet continues to scale up.

(Fleet distribution and research plan votes already suffer from this, with plans taking multiple pages.)

edit: that said, Nix does a heroic effort boiling down the important research options into several task votes. Maybe this can be done in the future for the types of votes with "scaling problems": shipyard ops, fleet distribution, snakepit if somehow we get so much pp and so many options to choose from.
 
Last edited:
I was under the impression that with the ones under construction and the 4 new ships we would be mainly caught up with the needs as of last quarter. 4 more berths (8 total for aux command) would in my view allow them to maintain the numbers of ships needed. Also I can see us continuing to have a few cargo ships and freighters under construction in normal Starfleet yards until we get caught up.

My reading was that there is a 18 ship deficit, any AUX ships made from general berths are subtracted from that. The current ships under construction are just maintaining our position, and 3 new AUX berths are needed to keep the Status Quo. Which means we need either more General berths to use initially on AUX ships or to work out how to build them in Idle member berths of which there's plenty of capacity.

@OneirosTheWriter , If we wanted to build AUX ships in Idle member yards, should it be voted on here (with these costs)? or wait for an option in Snakepit?
 
Last edited:
In the long run, it doesn't change quantities of ships - it just shifts a Rennie build 4 quarters earlier, and delays an Excelsior refit by a quarter.

It basically has no serious downsides that I can see. It technically slightly deviates from the trailing end of the fleet distribution, but such votes should seriously not restrict shipyard op votes.

If I had the time (edit: or rather, proper equipment), I'd propose and advocate it.

I just tried plugging it in and it produced an SR deficit.

 
My reading was that there is a 18 ship deficit, any AUX ships made from general berths are subtracted from that. The current ships under construction are just maintaining our position, and 3 new AUX berths are needed to keep the Status Quo. Which means we need either more General berths to use initially on AUX ships or to work out how to build them in Idle member berths of which there's plenty of capacity.
We should (fingers crossed) get a fresh logistics update once the next tactical report rolls around.
That should help us see just how quickly we're digging the hole we find ourselves in.
If memory serves, the Docana had a similar incident.
Stardate 25026.4 (2313.Q1.M2)
There was a complete log at some point, perhaps, but things got redacted. Except for the chroniton surge. That got left in.
 
Back
Top