VOY 3x26: Scorpion Part 1
Is there some kind of Starfleet form I can sign to opt out of transporter hacks you “just came up with”?
Could I theoretically lock onto the poop in my lower intestine and the piss in my bladder and beam them out of myself so I don’t have to go to the toilet?
No. Piss is stored in the balls.
Lol, a few years ago on the alien site, I wrote a scene for The Orville as a “what if The Orville suddenly got transporters” That was basically the premise of it.
If there’s interest, and I can find it (I saved it to a text file somewhere before nuking my account), I can post it here.
cut to the planet below, where there are three puddles of meat and clothes gurgling in pain and disappointment
“Good enough, they’ll take the (space-)night shift. I’ll double the calcium rations.”
Space October memes, engage!!
whenever I see transporter memes, it reminds me that no one in starfleet needs to die. they could save and update your pattern. you’d only lose the away mission.
:|
Imagine murdering a bunch of space travelers and they all come back while you’re still looting the bodies.
Pretty sure that’s explained in canon by being too compute and storage intensive. You can’t store a person’s pattern in any medium, apart from the buffer.
And in there it’s only very temporarily before breaking down (see scotty in the Dyson sphere or m’bengas kid)
I always looked Galaxy Quest’s take on this:
“But the pig-beast is inside out… and now it has exploded.”
It was just like a clueless captain to say “energize” as if that’s going to magically make it work. Like, I’m trying to invent a whole new field of engineering here, Kathryn. Maybe step off a bit if you want them back in one piece.
- Torres (later to Vorik over a mug of something replicated and syntheholic)
Yeah, that’s one of those tropes I hate pretty much everywhere, but (old) Star Trek is great enough to look past it.
They are skilled and professional. But how incompetently was the playbook written, if pretty much everyone can come up with something previously not derived spontaneously, if it’s that easy?
I generally view them as developmental or unreliable methods. A 20% risk of killing everyone involved is horrifying for a normal away mission return. However, the same risk for pulling a team away from imminent death is a lot more tolerable.
This also explains how they can implement them so quickly, it’s already buried in the codebase.
IMO, it’s essentially the duality of techno babbling. In the hands of good writers it can enhance an already well written story.
In bad writing, it’s often used as a fluff drama element, sometimes even becoming deus ex machina.
Instead of a DNR (do not resuscitate), create a DNTH (do not transporter hack)