As you can see from observing quarters one through three there is usually a jump of around +90 units between quarters. However between Q3 and Q4 the Stardate went backwards by 612.5 units. By my estimate that's a loss of about one and a half years.
1 unit per day (~90 per quarter) has been the default since the beginning of 2302. There were two other occasions when stardates went backwards, between 2304.Q2 and 2304.Q3 and between 2301.Q3 and 2301.Q4, though only enough to overlap with the previous quarter. The increase between 2307.Q4 and 2308.Q1 also was unusually small and also correlates with a known temporal anomaly. Clearly anyone wanting to write an omake about temporal anomalies we don't know about should put them in late 2301 or mid 2304.
 
What did u do Nash. WHAT DID U DO!?!?!?!?
At a guess I'd say she, or rather that glimpse at Steller Cartography, inspired Thalisar such that she unified Andoria faster. This then had ripple on effects that presumably lead to the Federation being founded earlier and so everything happened ~1.5 years sooner then in the OTL.
 
At a guess I'd say she, or rather that glimpse at Steller Cartography, inspired Thalisar such that she unified Andoria faster. This then had ripple on effects that presumably lead to the Federation being founded earlier and so everything happened ~1.5 years sooner then in the OTL.
That doesn't make sense. Her unifying Andoria wouldn't influence the Earth calendar, so if the Federation was founded earlier stardates should be higher relative to the Earth calendar. It's more likely that it influenced the exact system used, like the anomaly in late 2301 also did (the progess between quarters was smaller before then).
 
Last edited:
That doesn't make sense. Her unifying Andoria wouldn't influence the Earth calendar, so if the Federation was founded earlier stardates should be higher relative to the Earth calendar. It's more likely that it influenced the exact system used, like the anomaly in late 2301 also did (the progess between quarters was smaller before then).

Butterflies, right? The Andorians contacted and started interacting with the Vulcans a bit sooner, the Vulcans started watching their neighbors a bit sooner, including Earth... okay, I don't follow how that got Cochrane's warp vessel into orbit a few years sooner, but I'm sure Nash had something to do with it too :)
 
Butterflies, right? The Andorians contacted and started interacting with the Vulcans a bit sooner, the Vulcans started watching their neighbors a bit sooner, including Earth... okay, I don't follow how that got Cochrane's warp vessel into orbit a few years sooner, but I'm sure Nash had something to do with it too :)
You're missing the point. The Federation getting founded in 2159 CE instead of 2161 CE or whatever wouldn't move the staring point of the Stardate system to a later time as measured in CE, it would move it to an earlier time as measured in CE. That means that if the system was the same the Stardate corresponding to a particular CE date would be higher, not lower.
 
You're missing the point. The Federation getting founded in 2159 CE instead of 2161 CE or whatever wouldn't move the staring point of the Stardate system to a later time as measured in CE, it would move it to an earlier time as measured in CE. That means that if the system was the same the Stardate corresponding to a particular CE date would be higher, not lower.
Ah I think you misunderstood. I was suggesting that with the Federation founding earlier all it's actions started earlier. So for instead of Admiral Kahurangi being appointed Head of Starfleet in 2301CE it was in 2299.5CE.

Of course that requires a ton of things to remain constant despite the 1.5 year drop in time since then but often times in Sci-Fi things like that which should have massive butterflies don't so it's not too unreasonable.

It could always just be something screwing with the Stardates like you suggest however. Honestly there is no way to tell outside of WoG from @OneirosThe Writer anyway.
 
The [-10 Relations with Lecarre] made me think.
Does the Relation mechanic also say something about our opionion about them or do they think worse of us, because their espionage attempt was deflected?
 
Ah I think you misunderstood. I was suggesting that with the Federation founding earlier all it's actions started earlier. So for instead of Admiral Kahurangi being appointed Head of Starfleet in 2301CE it was in 2299.5CE.
No, I perfectly understood you, it would just have precisely the opposite effect on the relationship between CE and Stardates you decribe, you are making the same mistake people make every year about daylight saving time. Maybe this helps: Say Stardate 0 was in 2250 CE before and is in 2248.5 CE in the new timeline. That makes the Stardate of 2250 CE higher than before, not lower. Or the CE date corresponding to Stardate 0 lower, not higher. It doesn't explain 2308.Q4 suddenly corresponding to a lower Stardate/ Stardate 2239X suddenly corresponding to a higher CE date.
 
Last edited:
@OneirosTheWriter
Whatever happened with the request to switch which computing subtech Daystrom and the Starfleet Science Academy we assigned to, given that the decision to assign Daystrom to 2310s Computing Installations instead of 2310s Shipboard Computing was based entirely on an incorrect understanding of apparently changed overflow/inspiration interactions?

That aside, you forgot several updates from the last research turn in the megapost.

2310s Computing Installations

30 / 30 Type-12 Duotronic Mainframe (Data Analysis Center II) (-1 RP required to activate Tech Team (8))
30 / 30 Wolff-T'Par Portable Mainframe (Portable Analysis Centers) (+2 rp annually from research colonies)

13 / 20 Pattern 3 SCF (Supercomputer Facility I) (Increases Comms Encryption, -1 to attempts to opposing SigInt attempts)

should be

30 / 30 Type-12 Duotronic Mainframe (Data Analysis Center II) (-1 RP required to activate Tech Team (8))
30 / 30 Wolff-T'Par Portable Mainframe (Portable Analysis Centers) (+2 rp annually from research colonies)
20 / 20 Pattern 3 SCF (Supercomputer Facility I) (Increases Comms Encryption, -1 to attempts to opposing SigInt attempts)


2310s Deflector Shields

I have no clue what is with the 20/40 here.

--

2310s Warp Core Safety

16 / 40 K19 Main Engineering System Module (Warp Core Damage Failsafe Design II) (Reduced chance of Warp Core Breach and reduce crew loss in the event of ship destroyed)
16 / 40 Light-Weight Coolant Redundancy (Warp Core Operation Safety Design II) (Improved reliability by 2%)
0 / 20 EPS Conduit Mag Failsafes I (Reliability for all stats improved by 0.1)

should be

27 / 40 K19 Main Engineering System Module (Warp Core Damage Failsafe Design II) (Reduced chance of Warp Core Breach and reduce crew loss in the event of ship destroyed)
22 / 40 Light-Weight Coolant Redundancy (Warp Core Operation Safety Design II) (Improved reliability by 2%)
6 / 20 EPS Conduit Mag Failsafes I (Reliability for all stats improved by 0.1)

--

2310s Message Security
Technology for looking into other people's messages, or stopping them from looking into yours.

10 / 40 Centi-Cochrane Band Antenna (Subspace Communications Intercepts II) (Allow deployment of Improved Listening Posts)
6 / 20 Subspace Communications Encryption I (Improve Information Security)
11 / 20 Subspace Communications Decryption I (Improve Intelligence Phase Information)

should be

14 / 40 Centi-Cochrane Band Antenna (Subspace Communications Intercepts II) (Allow deployment of Improved Listening Posts)
10 / 20 Subspace Communications Encryption I (Improve Information Security)
20 / 20 Subspace Communications Decryption I (Improve Intelligence Phase Information)
 
EDIT: The temporal anomaly may also have not actually changed the time at which any specific Federation historical event happened at all, and ONLY changed the way stardates were computed. Maybe the stardate calendar was invented by some Andorian and became an interstellar standard by coincidence.

@OneirosTheWriter how much fun is Sulu having as head of the explorer corps? It seem to me the last incident was at least part of a troll to Spock and or Sarek
Actually, Ambassador Sarek of Vulcan is a really good choice, perhaps one of the best choices possible.

Some of us suggested Spock- but thinking about it, that was probably colored by our natural bias for him as a major canon character. Right now in game, he's a promising Vulcan of early middle age. He's got a remarkable Starfleet career behind him, but as of 2308 he's only made a start on his second career as a xenopsychologist and diplomat. A good start, but a start. His credentials as a diplomat are nowhere near what the Diplomatic Corps would like to see in the guy who's responsible for stopping an ongoing mess on this scale.

Whereas Sarek is a distinguished and accomplished diplomat of late middle age (about 150), who has been handling high-level negotiations since at least the mid-2260s (Journey to Babel). And he's damn good, we know this because he's a living legend to guys like Picard in the mid-2300s.

So for now, when you need a Vulcan diplomat and you want to send the very best, you send the father, not the son.

That'll be changing in the TNG era as Sarek loses edge to age and encroaching Bendii Syndrome, while Spock builds greater experience and reputation. But right now, that's where things stand.
 
Last edited:
Admiral Ablett was wrong, but not totally.

What he's talking about would work for a Heavy Cruiser, a ship that is easier on logistics but still in 'The Ballpark' would be great for our system defense and crisis response...but for the stuff an Explorer does, IE The FYM and our biggest jobs, we need the best of the best...and with a backup of Heavy Cruisers(IE old Explorers that aren't outdated yet, or later a design specifically for the job), we don't need that many explorers.

There may also be the Pocket-Explorer concept I've been 'championing', which is basicly a Battlecruiser to the Full Explorer's Battleship, but that was meant to support the bigger 'boys' in my mind.


@OneirosTheWriter
I just had a thought, could we do a refit like the Connie-B to the Excelsior once we replace it in the Explorer Corps, IE streamline it so it can go into a cruiser role easier?

I still want to do a straight combat refit to the ship, but a Excelsior-A refit focused around making it easier to produce would be nice.
 
Admiral Ablett was wrong, but not totally.

What he's talking about would work for a Heavy Cruiser, a ship that is easier on logistics but still in 'The Ballpark' would be great for our system defense and crisis response...but for the stuff an Explorer does, IE The FYM and our biggest jobs, we need the best of the best...and with a backup of Heavy Cruisers(IE old Explorers that aren't outdated yet, or later a design specifically for the job), we don't need that many explorers.

There may also be the Pocket-Explorer concept I've been 'championing', which is basicly a Battlecruiser to the Full Explorer's Battleship, but that was meant to support the bigger 'boys' in my mind.


@OneirosTheWriter
I just had a thought, could we do a refit like the Connie-B to the Excelsior once we replace it in the Explorer Corps, IE streamline it so it can go into a cruiser role easier?

I still want to do a straight combat refit to the ship, but a Excelsior-A refit focused around making it easier to produce would be nice.

I honestly sorta agree with continuing to just build Excelsiors and let them take on the role of our main heavy cruisers once we start putting out newer Explorers.

Of course this is all loooooooong range planning. Specifics are probably months away at least in real time
 
I honestly sorta agree with continuing to just build Excelsiors and let them take on the role of our main heavy cruisers once we start putting out newer Explorers.

Of course this is all loooooooong range planning. Specifics are probably months away at least in real time
that's what I've been wanting to do forever, as Excelsior's would be a great heavy cruiser.

and your right, I just wanted to put in my 2 cents worth.
 
The problem with reclassifying Excelsiors is that we currently (and with mid term building plans) have too few home fleet Explorers even for Combined Fleet Doctrine, let alone Lone Ranger Doctrine. If we reclassify all of our existing Explorers we will never see a reasonable proportion of Explorers. There is no real advantage for reclassification either assuming we keep up Explorer tech which we need to anyway.
 
Last edited:
I would think mass producing excelsiors would be too time and resource heavy when we can build smaller ships of comparable performance.
 
The problem with reclassifying Excelsiors is that we currently (and with mid term building plans) have too few home fleet Explorers even for Combined Fleet Doctrine, let alone Lone Ranger Doctrine. If we reclassify all of our existing Explorers we will never see a reasonable proportion of Explorers. There is no real advantage for reclassification anyway assuming we keep up Explorer tech which we need to anyway.
Reclassification isn't needed here, we don't even need a streamline refit...the Excelsior can do the Heavy Cruiser job just fine now.

I would think mass producing excelsiors would be too time and resource heavy when we can build smaller ships of comparable performance.
that's why I'm pulling for a streamline refit to be implemented at some point, so we can build them faster and cheaper.
 
Last edited:
Back
Top