Interesting, I wasn't aware of that. Can you elaborate, or has this been discussed in some other thread before?
Thing is, the destruction of Romulus would be a pretty huge event for the Trek universe, that I don't see how one could manage to avoid mentioning it, even if we jump ahead to 2400. Might just be best to sweat out 2386 being stretched out for several years much like 2376 was.Perhaps another time jump would be the only way they can move beyond the events of ST'09? But I remember the fanrage at the timehop in "Rough Beasts of Empire" being pretty severe, to the extent DRGIII quit TBBS.
Would anyone here be on board with the novelverse picking up in a newly established status quo in, say, 2400?
Then I wonder why STO is allowed to use them, they Hobus and everything. They even reference Spock trying to save Romulus.
Maybe because they're under CBS Consumer Products which has the rights to use the KT stuff?
Perhaps another time jump would be the only way they can move beyond the events of ST'09? But I remember the fanrage at the timehop in "Rough Beasts of Empire" being pretty severe, to the extent DRGIII quit TBBS.
Personally, I think that the smaller time jumps also hurt the other series, even if it is just a few months between books.As I recall, the time jump itself wasn't so bad, and most of the poor reaction to that book came from Sisko's character arc.
Massive reaction to the beginning of the arc and DRG3 hasn't been back since. It's too bad, because all the crap people were angry about pretty much gets worked out by the end of the 3-part arc. It makes me wonder that if RBoE and the duology that followed the next year had been billed as a trilogy, it would've been easier for people to swallow...As I recall, the time jump itself wasn't so bad, and most of the poor reaction to that book came from Sisko's character arc.
Yeah, getting to feature those events in the novelverse (as well as the loss of Spock, which is massive) would be preferable. I was just speculating on how the current issue can be circumvented.Thing is, the destruction of Romulus would be a pretty huge event for the Trek universe, that I don't see how one could manage to avoid mentioning it, even if we jump ahead to 2400. Might just be best to sweat out 2386 being stretched out for several years much like 2376 was.
I wouldn't mind this. I enjoy these kind of jumps where we don't know what to expect and what situations we'll the characters will be in, hopefully. Sometimes this doesn't always work out, like the DS9-R, but sometimes it does..Would anyone here be on board with the novelverse picking up in a newly established status quo in, say, 2400?
even if Western historians like to call it the Byzantine Empire after that.
But the best way to avoid mentioning the loss of Romulus is to just ignore the Romulans altogether, and then we get to "Well how do we feature the Typhon Pact without featuring the Romulans?" So that ultimately means the Typhon Pact won't be mentioned either. My point is even a time jump is going to run into problems since it still can't mention the loss of Romulus. The only solution to the problem will be the novels getting the license to cover Abrams material.^There's no reason to avoid mentioning the Typhon Pact. Just because Romulus was lost, that doesn't mean the entire Romulan Star Empire was lost. The Roman Empire continued after Rome fell, even if Western historians like to call it the Byzantine Empire after that.
But the best way to avoid mentioning the loss of Romulus is to just ignore the Romulans altogether...
, and then we get to "Well how do we feature the Typhon Pact without featuring the Romulans?" So that ultimately means the Typhon Pact won't be mentioned either.
STO and ST: Countdown feature the Hobus event. Could TrekLit feature the loss of Romulus and pretend it's referencing STO, and not the movie? A bit like dating the other twin.
STO and ST: Countdown feature the Hobus event. Could TrekLit feature the loss of Romulus and pretend it's referencing STO, and not the movie? A bit like dating the other twin.
We use essential cookies to make this site work, and optional cookies to enhance your experience.