On the third hand, it was officially decided (at least at Cryptic) that as of Picard season 3, STO is an alternate future timeline. Upcoming shows might draw from it, but are not obligated to because the timelines split when the Ent-F was decommissioned in the Prime timeline, while remaining in service for another nine years and then getting an upgrade in the STO timeline.
Well... TECHNICALLY speaking STO's Ent-F is still only a couple years old. The first time we ever see her is in the 2800 FE series. I believe in Boldly They Rode, when the Enterprise shows up under the command of Captain Shon to help fight off the time displaced Dominion Fleet. That set of missions, while not mainline anymore, still exist as side stories we can play, and shows Captain Shon losing the Belfast, then gaining command of Enterprise. It does add context to why we see Shon flying the Belfast in the Romulan arc, but then suddenly he's Captain of the Enterprise later on in the story. So... while the Prime Ent-F was decommissioned in 2402, STO's Ent-F was commissioned in 2409.
We can, however, pull a little timey-wimey to claim that she was first commissioned in the late 24th century, and 2409 was a refit (preparatory to her upgrade to Yorktown-class in 2410). It's just that we can't reconcile her decommissioning in 2401 and the launch of Ent-G in 2402 with Ent-F relaunching in 2409. That was when the game devs said that they couldn't unite the timelines and we were now in a divergent universe.
Honestly the ENT-G isn't a total impossibility to harmonize, all we need is something happen to the G that demands that the ENT-F is pulled out of mothballs and the recommissioned, decommissioning doesn't mean "is destroyed", just "is taken out of service" and to use a real life example the Iowa class battleships were decommissioned and recommissioned several times before finally permanently taken out of service.
However, they were never recommissioned while another ship of the same name was in service. The name Enterprise, in Prime canon, was assigned to NCC-1701-G in 2402, so Prime canon can't recommission the Ent-F at this point (although precedent from both Ent-A and Ent-G imply that the ship herself could be recommissioned with a new name and registry number, just as both of those ships were).
On the third hand, it was officially decided (at least at Cryptic) that as of Picard season 3, STO is an alternate future timeline. Upcoming shows might draw from it, but are not obligated to because the timelines split when the Ent-F was decommissioned in the Prime timeline, while remaining in service for another nine years and then getting an upgrade in the STO timeline.
Well... TECHNICALLY speaking STO's Ent-F is still only a couple years old. The first time we ever see her is in the 2800 FE series. I believe in Boldly They Rode, when the Enterprise shows up under the command of Captain Shon to help fight off the time displaced Dominion Fleet. That set of missions, while not mainline anymore, still exist as side stories we can play, and shows Captain Shon losing the Belfast, then gaining command of Enterprise. It does add context to why we see Shon flying the Belfast in the Romulan arc, but then suddenly he's Captain of the Enterprise later on in the story. So... while the Prime Ent-F was decommissioned in 2402, STO's Ent-F was commissioned in 2409.
We can, however, pull a little timey-wimey to claim that she was first commissioned in the late 24th century, and 2409 was a refit (preparatory to her upgrade to Yorktown-class in 2410). It's just that we can't reconcile her decommissioning in 2401 and the launch of Ent-G in 2402 with Ent-F relaunching in 2409. That was when the game devs said that they couldn't unite the timelines and we were now in a divergent universe.
Honestly the ENT-G isn't a total impossibility to harmonize, all we need is something happen to the G that demands that the ENT-F is pulled out of mothballs and the recommissioned, decommissioning doesn't mean "is destroyed", just "is taken out of service" and to use a real life example the Iowa class battleships were decommissioned and recommissioned several times before finally permanently taken out of service.
However, they were never recommissioned while another ship of the same name was in service. The name Enterprise, in Prime canon, was assigned to NCC-1701-G in 2402, so Prime canon can't recommission the Ent-F at this point (although precedent from both Ent-A and Ent-G imply that the ship herself could be recommissioned with a new name and registry number, just as both of those ships were).
"all we need is something happen to the G that demands that the ENT-F is pulled out of mothballs and the recommissioned" Obviously this would mean there would not be 2 ships named the "Enterprise" in the active roster, but say if G was damaged beyond repair, they probably would take F out of Mothballs instead of waiting H to be built.
On the third hand, it was officially decided (at least at Cryptic) that as of Picard season 3, STO is an alternate future timeline. Upcoming shows might draw from it, but are not obligated to because the timelines split when the Ent-F was decommissioned in the Prime timeline, while remaining in service for another nine years and then getting an upgrade in the STO timeline.
Well... TECHNICALLY speaking STO's Ent-F is still only a couple years old. The first time we ever see her is in the 2800 FE series. I believe in Boldly They Rode, when the Enterprise shows up under the command of Captain Shon to help fight off the time displaced Dominion Fleet. That set of missions, while not mainline anymore, still exist as side stories we can play, and shows Captain Shon losing the Belfast, then gaining command of Enterprise. It does add context to why we see Shon flying the Belfast in the Romulan arc, but then suddenly he's Captain of the Enterprise later on in the story. So... while the Prime Ent-F was decommissioned in 2402, STO's Ent-F was commissioned in 2409.
We can, however, pull a little timey-wimey to claim that she was first commissioned in the late 24th century, and 2409 was a refit (preparatory to her upgrade to Yorktown-class in 2410). It's just that we can't reconcile her decommissioning in 2401 and the launch of Ent-G in 2402 with Ent-F relaunching in 2409. That was when the game devs said that they couldn't unite the timelines and we were now in a divergent universe.
Honestly the ENT-G isn't a total impossibility to harmonize, all we need is something happen to the G that demands that the ENT-F is pulled out of mothballs and the recommissioned, decommissioning doesn't mean "is destroyed", just "is taken out of service" and to use a real life example the Iowa class battleships were decommissioned and recommissioned several times before finally permanently taken out of service.
However, they were never recommissioned while another ship of the same name was in service. The name Enterprise, in Prime canon, was assigned to NCC-1701-G in 2402, so Prime canon can't recommission the Ent-F at this point (although precedent from both Ent-A and Ent-G imply that the ship herself could be recommissioned with a new name and registry number, just as both of those ships were).
"all we need is something happen to the G that demands that the ENT-F is pulled out of mothballs and the recommissioned" Obviously this would mean there would not be 2 ships named the "Enterprise" in the active roster, but say if G was damaged beyond repair, they probably would take F out of Mothballs instead of waiting H to be built.
Game-wise we probably would not find out for quite a while since the devs would probably want to wait and see if the series hinted at the end of PIC is picked up or not, and probably not even for the entire run of the series if it is, to see if the G gets wrecked at the end of it. Despite the declaration of separate parallel timelines, the devs will probably want to take advantage of any boost that possible series would give them.
0
rattler2Member, Star Trek Online ModeratorPosts: 58,582Community Moderator
They do want to take advantage of everything they can, however if they can't reconcile canon events with in game events... as was stated before STO is its own timeline. So we can draw from Canon, but we can't bend over backwards into a pretzel to conform to it 100%. And since Ent-F is still a relatively new ship STO wise... it makes no sense to mothball her for the G, and then without any kind of explanation bring F back into service.
Makes more sense that Ent-F's history in game is exactly as we have seen in game, being the newest Enterprise in our timeline, than trying to shoehorn the events of Picard s3 in to get the G, but not explain why we have the F again.
Also... I hope the Devs tweak that Athan Prime beacon console. The Ent-A being a TOS connie makes no sense. Should either switch the model to the TMP Connie or rename her to be the USS New Jersey, which IS a TOS Connie.
Comments
"all we need is something happen to the G that demands that the ENT-F is pulled out of mothballs and the recommissioned" Obviously this would mean there would not be 2 ships named the "Enterprise" in the active roster, but say if G was damaged beyond repair, they probably would take F out of Mothballs instead of waiting H to be built.
Game-wise we probably would not find out for quite a while since the devs would probably want to wait and see if the series hinted at the end of PIC is picked up or not, and probably not even for the entire run of the series if it is, to see if the G gets wrecked at the end of it. Despite the declaration of separate parallel timelines, the devs will probably want to take advantage of any boost that possible series would give them.
Makes more sense that Ent-F's history in game is exactly as we have seen in game, being the newest Enterprise in our timeline, than trying to shoehorn the events of Picard s3 in to get the G, but not explain why we have the F again.
Also... I hope the Devs tweak that Athan Prime beacon console. The Ent-A being a TOS connie makes no sense. Should either switch the model to the TMP Connie or rename her to be the USS New Jersey, which IS a TOS Connie.