I don't find it odd, because it was needed to show was Bejazzle was all about rather quickly. But, that's me. Stepping in to worlds quickly is something is fundamentally apart of my viewing experience.
Spoilers Star Trek Discovery 3x11 Season 3 Episode 11 Citadel - Promo Trailer
- Thread starter teasertrailer
- Start date
Remember, a director's main job is to get the most out of the actors and the scripts he or she has to work with. Frakes does OK with what might just be weak material.
It wasn't a bad episode, I just think it failed to move the story forward - at that point we had the Georgiou thing going on, the burn with no movement, and I am still not sure StarFleet is above board...
So back to an earlier comment - Culber is a Bajoran and Burnham is a thrill of a Trill (sorry) - do we think that is undercover shanigans and they were altered before beaming over or is this something that happens to them when they beam over to the Citadel? Seems like an odd choice if the Citadel is the Kelpien ship.
I'm assuming something happens to them when they beam over since there'd be no reason why they'd need to disguise themselves as Bajoran and Trill to board a Kelpien ship.
The two parter was mostly about concluding Georgiou's run on Discovery (which is what we got, along with seeing how her stay in the Prime universe changed her).
As for Starfleet being above board... meh, for all intense and purposes, Georgiou is not alive. We also don't know just how much of the experience Burnham told to Saru... but its probable she told him everything... but Saru concluded himself that Georgiou is 'deceased' and this is exactly what the rest of Starfleet will be told.
In regards to the Burn storyline not moving forward... to be fair, the writers have been progressing this bit slowly through the season.
Every character follow-up was mostly done every other episode... the main storyline (the Burn) was also progressed along similar lines... but more clues were given to the audience (like the music) in greater portions.
Basically my idea is that the opening scene should have been something involving Icheb's shuttle crashing, or otherwise being in distress. The gore could have been included later, but we should find out about it at the same time as Picard for maximum effect. We absolutely should not be explained things onscreen that we've already seen - every moment in filmed drama is precious, and we could be spending that time on something else entirely.
I see the point but I don't agree. I think it sets a tension to explore.
DNA transporter hijinks. Ye Old Trek Plot #68
Or Burnham tries to pull a fast one on the Emerald Chain by pretending to be a Bajoran Exchange Student?
This nebula apparently is pretty far away from Vance's assets, but back before the Burn it was Starfleet territory, with Starfleet help expected to arrive for the Kelpien crew in a jiffy. How fast are these starships from the Burn era, really? Could Vance suddenly show up without spore drive? How could Osyraa, if that's her arriving in person?
Timo Saloniemi
This nebula apparently is pretty far away from Vance's assets, but back before the Burn it was Starfleet territory, with Starfleet help expected to arrive for the Kelpien crew in a jiffy. How fast are these starships from the Burn era, really? Could Vance suddenly show up without spore drive? How could Osyraa, if that's her arriving in person?
Timo Saloniemi
Enemies are almost always portrayed in Trek as having similarly or better armed and faster ships than Starfleet.
We don't know how fast the post burn ships are warp wise.
The tikhov was said to be 5 months away... But we don't know from where in the galaxy or at which warp speed.
It's possible we will see some Starfleet ships arriving at the last moment either with warp or spore drive (the spore drive would be preferable) to help discovery, but we don't know that for certain. The fleet is never there when you need it.
The enterprise e ended up battling the scimitar on it's own despite being fairly close to the Starfleet taskforce just beyond the bassen rift.
Once communications were cut off, you'd think the taskforce would warp to them just in case as they were battling the scimitar for a while... Heck, only the two romulan warbirds showed up.
Yup, that's an interesting question. Might be the Burn had no real effect on ship speed: few of the ships would have been built, let alone designed, after the Burn, so the same engines would soldier on. But the dilithium shortage might prompt the skippers to stick to economy cruise speed - assuming that such a thing exists in the first place, and that the least dilithium-expensive approach in fact isn't a mad but brief dash at warp eleventeen...
Probably at her own speed, which could be expected to be low, considering her mission. Also, it wasn't a theoretical question: somebody was going to perform crew rotation on them within that timescale. Might be the rendezvous could have been hastened, but we don't know by how much, except that it wouldn't have been enough to save the sick refugees.
There might be other destinations within Starfleet territory yet many months away, too: Burnham and Booker never managed to reach the vicinity of Earth during their initial year of travels, even though she'd have been highly motivated to try.
The cutting off of communications probably played little or no role there. If it were possible for the fleet to meet with Picard, it would already have. That it instead chose to wait would suggest that it had strict orders not to go to Romulan territory no matter what - the loss of the E-E would apparently be preferable to a border violation at this delicate time.
Vance has every excuse to fail to show up, including dramatic ones: he's a potentially shady character with hidden agendas. But yeah, he also has every excuse to spore-jump in and surprise everybody...
Timo Saloniemi
Didn't the Enterprise-E already left Romulan space by the time it reached the Bassed rift and crossed into the Neutral Zone?
They also informed Starfleet of what Shinzon wanted to do via subspace, hence why the taskforce was assembled and waiting.
Its likely the rift sits in the Neutral Zone bordering with Federation space.
And yes, while I understand the dance both Romulans and the Federation played bordering with the Neutral Zone in TNG... neither ship from either side was allowed to cross into the N.Z. without explicit permission on both sides.
The Enterprise-E had permission to cross the N.Z. and go to Romulus... and they were hurrying back to Federation once they discovered what Shinzon wanted to do.
Shinzon technically violated that agreement and he crossed into the N.Z while in pursuit of the Enterprise... also, since the rift disrupts all subspace communications, the fleet might have gone inside the rift without being detected... however, long range sensors might have seen the fleet entering the rift in that case (unless SF had a clever way to fool the Romulan sensors and make them think the fleet was still waiting).
The last we hear is that they are "headed for Federation space"; earlier on, Shinzon boasted that they'd never make it out of the RNZ.
Just before the fight, less than a minute before they enter Bassen, Data says that the fleet is about 40 minutes away. This, then, is the likely location of the border, too.
Possibly so. But the only reason for the fleet to stop, rather than to meet with the E-E, would be if they were not allowed to cross the border. The threat from Shinzon could be countered at two locations only: Earth, and the current location of the E-E. Waiting would serve no purpose if alternatives existed.
Yet both did, just as in TOS, and there never was war. So the risk probably wasn't deemed all that high whenever a skipper pondered whether to violate the treaty or not. But at this particular time, erring to the side of caution (and Federation) might have been a pretty good idea, especially as Picard had been able to tell Starfleet all about this enemy who apparently was at odds with the rest of Romulus.
...Perhaps the fleet was inside the rift, but due to its sensor-fouling properties, never managed to locate the fight?
But the writers didn't quite understand what they were writing here: it made no tactical sense for Shinzon to wait until Bassen before making his move. The comms blackout did not provide any advantage, and in any case, Shinzon deliberately squandered any extra minutes he might have gained.
Then again, little or nothing that Shinzon did made any sense, and squandering was one of his superpowers...
Vance is a bigger mystery here, while Osyraa might have something up her sleeve as well, instead of being all cardboard. But the plots themselves don't suffer if it turns out there's no mystery or depth to these characters. Unlike in ST:NEM.
Timo Saloniemi
The episode is called Su'kal, also preview pictures
http://blog.trekcore.com/2020/12/star-trek-discovery-311-photos-sukal/
http://blog.trekcore.com/2020/12/star-trek-discovery-311-photos-sukal/
Hmm, that makes me think that the finale will actually be called That Hope Is You, Part 2.
Book, Grudge, and Dr. Pollard.
I NEED TO KNOW MORE ABOUT THIS SCENE.
I NEED TO KNOW MORE ABOUT THIS SCENE.
I wonder why the last minute name change? Its not like ''Su'kal'' is spoilery.
Grudge is a time travelling mirror cat
