STAR TREK: A Long Road (Voyager Fix It Quest)

[DragonCobolt]

Spoiler: Fleetwide Buff

The Dragon: Once per episode, at the beginning of combat place an Advantage on the field representing a cunning tactic or strategy devised by Danara Pel.

Spoiler: USS Voyager

NAME​	USS Voyager	PROF.​	MULTIROLE
CLASS​	Sovereign Class Heavy Exploration Vessel	CONST​	2371
SHIELDS​	13/13​	RESISTANCE​	6​	SCALE​	6​
POWER ​	13/13​	CREW SUPPORT​	6​	SMALL CRAFT​	5​

		COMMS​	ENGINES​	STRUCTURE​	COMPUTERS​	SENSORS​	WEAPONS​
BREACHES​		0/6​	0/6​	0/6​	0/6​	0/6​	0/6​
​	​	9​	11​	10​	11​	9​	10​
COMMAND​	3​	12​	14​	13​	14​	12​	13​
CONNING​	2​	12​	14​	13​	14​	12​	13​
ENGINEERING​	2​	11​	13​	12​	13​	11​	12​
SECURITY​	3​	13​	15​	14​	16​	13​	14​
SCIENCE​	2​	11​	13​	12​	13​	11​	12​
MEDICINE​	2​	11​	13​	12​	13​	11​	12​

TALENTS​	Command Ship: Can give advantages using Command within range to Away Missions or to supporting ships. EMH: Has an EMH! Improved Warp Drive: When going to warp, roll 1cd on an effect, regain the power point. Quantum Torpedoes: Can use Quantum Torpedoes! (60 total) Secondary Reactors: +5 to Power High Resolution Sensors: +1 momentum to out of combat sensor checks.
TRAITS​	Federation Starship – A highly sophisticated and advanced vessel, with holodecks, replicators, and similar comforts, primarily designed to handle multiple operations. Highly sensitive and requiring constant maintenance, the vehicle is less rugged than other interstellar craft Maquis Crew - a good chunk of the crew are former Maquis troublemakers. Expect discipline problems and unorthodox plans.
WEAPONS​	Phaser Arrays Power Cost: 1-3 | Range: Medium | Damage: 9cd [+1 per extra power spent] Can Use Spread: Hit +1 time at ½ damage per effect OR Area: hit +1 ship per effect within close range. Versatile 2: Gain 2 bonus momentum with a successful hit Photon Torpedoes Power Cost: 0 | Range: Long | Damage: 6cd High Yield: If it causes 1 breach, it causes +1 breach Quantum Torpedoes Power Cost: 0 | Range: Long | Damage: 7cd (Vicious 1 - +1 damage on effects) High Yield: If it causes 1 breach, it causes +1 breach Calibrations: Requires 1 minor action to calibrate Tractor Beam (Strength 5) Power Cost: 0 | Range: Close | Damage: None Effect: If successfully established, enemies face a diff 5 check to escape.

CREW COMPLIMENT (Base Stat: 9 | Base Skill: 2)
CO: Captain Katheryn Janeway (Skilled: Command, Science | Weakness: Combat)

SPECIAL ABILITY: "We Can Be Better" - if you succeed on any diplomatic check with Janeway, Get +1 momentum​

XO: Commander D-91 (Skilled: Command | Weakness: Socialization)
HELM: Lt. Tom Paris (Skilled: Conn | Weakness: Not Being A Fucking Up)
TACTICAL: Ensign Harry Kimm (Skilled: Gunnery | Weakness: Harry Kim)
SECURITY: Lt. JG Amy Strong (Skilled: Personal Combat | Weakness: Lying)

MAQUIS HEADBREAKER: C'nola (Skilled: Combat, Sneaking and Scheming | Weakness: Emotional Wreck)​

SCIENCE: Tuvok (Skilled: Science | Weakness: Emotionless)
COMMS: Lt. Bian T'are (Skilled: Communications | Weakness: Combat)
MEDICAL: The EMH (Skilled: Doctor | Weakness: Kind of a Dick)
ENGINEER: B'lanna Torres (Skilled: Engineering | Weakness: Also a dick)

SECONDARY CHARACTERS
Ensign Steve (Useless Security Goon)
Ensign Becky (plural fighter jock)
Petty Officer Third Class Jessie (Hard working engineer)
Crewman Billingsly (Dude, Billingsly!)
Crewman Chandra (Concerned Crewman)
Bifurcate (bidimensional robot girlfriend of Harry Kim)
Princess Lyan Positron (runaway daughter of magician most foul and girlfriend of Harry Kim)
Soria Flyte (Pegasus girl and girlfriend of Harry Kim)
Mirror Universe Trevor (he's fine!)

Spoiler: MRSS Val Jean

NAME​	MRSS Val Jean	PROF.​	TACOPS
CLASS​	Keldon Class Heavy Cruiser	CONST​	2370
SHIELDS​	12/12​	RESISTANCE​	5​	SCALE​	4​
POWER ​	7/7​	CREW SUPPORT​	4​	SMALL CRAFT​	3​

		COMMS​	ENGINES​	STRUCTURE​	COMPUTERS​	SENSORS​	WEAPONS​
BREACHES​		0/4​	0/4​	0/4​	0/4​	0/4​	0/4​
​	​	9​	9​	9​	8​	7​	10​
COMMAND​	3​	12​	12​	12​	11​	10​	13​
CONNING​	2​	11​	11​	11​	10​	9​	12​
ENGINEERING​	2​	11​	11​	11​	10​	9​	12​
SECURITY​	3​	12​	12​	12​	11​	10​	13​
SCIENCE​	1​	10​	10​	10​	9​	8​	11​
MEDICINE​	2​	11​	11​	11​	10​	9​	12​

TALENTS​	Electronic Warfare Suite: Whenever making a Jamming or Intercept communications check, can spend 2 momentum to select +1 target (repeatable.) Fast Targeting Systems: No +1 diff for called shots Improved Hull Integrity: +1 Resistance Cloaking Device: Spend 3 power, and make a Control+Engineering + Engines + Security check with a diff of 2. If successful, gain the Cloaked Trait (impossible to detect, cannot attack, shields are down.) It takes a minor action to decloak.
TRAITS​	Cardassian Ship – Durable, uncomfortable, close, cramped and cheap. Thinks creature comforts are for other people and technical sophistication is for people who haven't spent decades starving to death. The fact that the starving could have been avoided if the government were less...you know, monstrous doesn't seem to have occurred to that many of them. Okampan Crew – the crew are bright, perky, cheerful, and incredibly psychically powerful. Individually, they're all better than Vulcans, and as a gestalt? Who knows!
WEAPONS​	Phaser Arrays Power Cost: 1-3 | Range: Medium | Damage: 7-9cd (Spread: Hit +1 time at ½ damage per effect OR Area) Versatile 2: Gain X bonus momentum with a successful hit Disruptor Banks Range: Medium | Damage: 8-10cd (Vicious 1: Each effect adds +1 damage) Tractor Beam (Strength 3)

CREW COMPLIMENT (Base Stat: 8 | Base Skill: 1)
CO: Lt. Commander Brian Wacoche (Skilled: Commando Tactics | Weakness: Independent)
TACTICAL: Seska (Skilled: Being Seska | Weakness: Everything Else)
CONN: R'lash skilled: Piloting | Weakness: Romulan Fuckup)
ESPIONAGE: Kes (Skilled: Commando Tactics | Weakness: Naive)

Spoiler: Memorial Wall

Crewman Stadi - Age 23, Betazoid, born Beta Colony-5 to Zani and Talwyn of the House of Riis, survived by her sisters Tari and Batri.
R'mor - age 182, Vulcan, burn on Romulus to R'tan and Leslali, survived by his twelve nieces and nephews across the Empire

 

[Rivenscryr]

[X] There's our ride! Hack into the Ogla computers and drop in a nasty virus – after stealing whatever data you can of course – then reprogram the target for the test torpedoes before sneaking aboard, stuffing yourselves into where the warheads would have gone, for extract. It'll be just like one of your Japanese holodeck programs!

I too enjoy a bit of refuge in audacity.

 

[QueenPally]

[X] Time to maximalize this: Sneak to the launch room, stun everyone from ambush, shut down the launch, steal everything, and leave

 

[fanficfan]

[X] There's our ride! Hack into the Ogla computers and drop in a nasty virus – after stealing whatever data you can of course – then reprogram the target for the test torpedoes before sneaking aboard, stuffing yourselves into where the warheads would have gone, for extract. It'll be just like one of your Japanese holodeck programs!

This can only end badly and I am totally on board for it

 

[Model DC.14F]

[X] Lets try some sabotage. A stealthed phaser shot at a precisely chosen component, just enough to weaken it, to cause the whole launch to fail. In the confusion, sneak to the computer bay and start deleting stuff

 

[Indivisible]

[X] Time to maximalize this: Sneak to the launch room, stun everyone from ambush, shut down the launch, steal everything, and leave.

 

[Reese]

...I'm kind of worried about that launch. I mean, not just in the sense of "we need the components on those test torpedos" or "this will be another step towards the development of a fully operational and armed version", but in the sense of "So... do the Borg have everything involved in this particular project already?".

Because they do, IIRC, have some transwarp tech. Maybe everything here, they could already build, and don't because they have no reason to. Maybe they also already have defenses against it, and wouldn't consider someone else having it a threat that needs to be dealt with.

...But maybe, instead, their transwarp tech would only let them detect those torpedoes activating their main engines. Alert them to there being something interesting, dangerous, or both here. And we don't know if this is even the first test launch they've done.

I mean, on the plus side, a cube or three warping into the system would probably distract the Kazon from us real quick, but if we were the sort of people to consider setting the Borg on an entire mostly-innocent star system an acceptable solution to a problem like this, we'd probably already have done it.

So, how best to actually stop this, then? Hm.

...Yeah, the problem with deleting stuff is that it might not even set them back much at all, if they've got offsite backups. Even if they don't, they already got this far from wherever they started, and deleting stuff won't even set them back to that point, given what the scientists and engineers working on it will just remember.
Oh, and also, if we want to make what they were doing here public, we'd be deleting evidence of the very thing we wanted to convince people of. So, yeah, not voting for that.

[X] Time to maximalize this: Sneak to the launch room, stun everyone from ambush, shut down the launch, steal everything, and leave.

 

[Spart117MC]

They're torpedoes that go to Warp. It's not really significant enough for the Borg to bother to send a cube.

Even if they don't, they already got this far from wherever they started, and deleting stuff won't even set them back to that point, given what the scientists and engineers working on it will just remember.

Click to shrink...

If you're worried about that then, the plan you're voting for doesn't really address that either, because it doesn't involve kidnapping or executing the scientists involved. The folks in the launch center, and only the launch center, are going to be stunned momentarily and that's it.

Oh, and also, if we want to make what they were doing here public, we'd be deleting evidence of the very thing we wanted to convince people of. So, yeah, not voting for that.

Click to shrink...

If you think that's what the other plan is saying then you've misread it. The plan to hijack the torpedoes explicitly mentions stealing the data first before wiping the Ogla computers, unless you're arguing that we should leave their database intact?

 

[Reese]

They're torpedoes that go to Warp. It's not really significant enough for the Borg to bother to send a cube.

Click to shrink...

...Isn't torpedoes going to warp standard, though? And wasn't what made transwarp torpedoes special addressed in INITIATIONS (0.4)?

If you're worried about that then, the plan you're voting for doesn't really address that either, because it doesn't involve kidnapping or executing the scientists involved. The folks in the launch center, and only the launch center, are going to be stunned momentarily and that's it.

Click to shrink...

But we have no plan to accomplish that, is the thing. Even if we shot everyone here, burned the bodies, and destroyed every bit of data storage down to a single post-it note, that wouldn't remove the chance of offsite backups or some key researchers being elsewhere at the moment or the like. Therefore, if not trying to delete the data at all puts us in no worse a position than trying to delete as much of it as we can, why direct any of our limited resources in that direction?

On the other hand, stealing everything here we can, that's potentially useful. It denies the resources to the enemy just as much as if we'd blown the things up, but that's incidental to providing us with those resources. Things we could use ourselves, or trade, or use as evidence for other Kazon. And that last part's how we can shut this down.

If you think that's what the other plan is saying then you've misread it. The plan to hijack the torpedoes explicitly mentions stealing the data first before wiping the Ogla computers, unless you're arguing that we should leave their database intact?

Click to shrink...

You seem to have misunderstood me, sorry about whatever part of that was my fault, but yeah, while I feel like what's done with their copies of the data is a low priority for us here, it might indeed be better to leave it intact. [shrugs] Of course, if it looked like it was about to become evidence that'd get them in trouble, they could just delete it themselves -- it's not worth trying to destroy it ourselves, I think, but we shouldn't put much into trying to preserve these copies of it, either.

 

[DragonCobolt]

transwarp is fasssterrrr zoom zoom

In fact, technically speaking, I thiiiiiink Voyager is kind of transwarp? Or trans warp adjacent, since she has the moving nacelle things to counter-act the space-time ripping bullshit from TNG.

 

[Spart117MC]

...Isn't torpedoes going to warp standard, though? And wasn't what made transwarp torpedoes special addressed in INITIATIONS (0.4)?

Click to shrink...

No...? Torpedoes don't regularly go to Warp because no one makes torpedoes with Warp drives. Like a ship going at Warp can fire torpedoes but that's a different thing entirely. In other words these torpedoes have got FTL drives attached which isn't commonly done.

But we have no plan to accomplish that, is the thing. Even if we shot everyone here, burned the bodies, and destroyed every bit of data storage down to a single post-it note, that wouldn't remove the chance of offsite backups or some key researchers being elsewhere at the moment or the like. Therefore, if not trying to delete the data at all puts us in no worse a position than trying to delete as much of it as we can, why direct any of our limited resources in that direction?

On the other hand, stealing everything here we can, that's potentially useful. It denies the resources to the enemy just as much as if we'd blown the things up, but that's incidental to providing us with those resources. Things we could use ourselves, or trade, or use as evidence for other Kazon. And that last part's how we can shut this down.

You seem to have misunderstood me, sorry about whatever part of that was my fault, but yeah, while I feel like what's done with their copies of the data is a low priority for us here, it might indeed be better to leave it intact. [shrugs] Of course, if it looked like it was about to become evidence that'd get them in trouble, they could just delete it themselves -- it's not worth trying to destroy it ourselves, I think, but we shouldn't put much into trying to preserve these copies of it, either.

Click to shrink...

You do understand this is a research facility that has a test site attached to it? This isn't a major production facility. The damage to the Ogla's capacity to manufacture additional torpedoes is going to be insignificant if we limit sabotage to stealing prototypes and spare parts on the station while leaving them access to all existing plans and research.

@DragonCobolt I'm not misunderstanding the situation here am I?

 

[DragonCobolt]

Well, firstly, I think that torpedoes do go at warp speed, but that MIGHT be me confusing Star Trek with @open_sketch's Torchship. But, counter point: Torchship is rad.

My thinking is that torpedoes can go at warp 1-2, allowing them to keep up in modern battlefields and avoid point defense fire until the last second where they have to actually match velocities and wham the bad guy ship. However, if you could build transwarp torpedoes, they could go much much faster, and have much longer range because of that.

Secondly, it's unclear exactly where the Ogla got this tech base from - if they're just basing it on some widget they found, then removing the widget and wiping their data will leave them with twiddly sticks. And considering transwarp torpedoes are beyond the Federation, it seems reasonable to presume that they're doing some bottle shaking, ya know?

(Bottle Shaking: The practice of finding advanced pieces of technology and shaking it to see what comes out without understanding the underlying steps.)

 

[Spart117MC]

Thank you, though I was asking more in regards to the issue of research data and weapon blueprints and whether any of the current courses of action involves actively leaving them intact. Isn't the whole point for Tuvok and the crew being here in the first place to cripple the Ogla's abilities to make more torpedoes and thus that information a key target for them?

 

[Draz]

[X] Time to maximalize this: Sneak to the launch room, stun everyone from ambush, shut down the launch, steal everything, and leave.

I don't think we stop production unless we steal the really useful stuff or get enough evidence to convince the other Kazon to come down hard.

 

[DragonCobolt]

Thank you, though I was asking more in regards to the issue of research data and weapon blueprints and whether any of the current courses of action involves actively leaving them intact. Isn't the whole point for Tuvok and the crew being here in the first place to cripple the Ogla's abilities to make more torpedoes and thus that information a key target for them?

Click to shrink...

Oh, yeah, the goal is to make sure Ogla can't make more any time soon!

 

[Rivenscryr]

Oh, yeah, the goal is to make sure Ogla can't make more any time soon!

Click to shrink...

So what you're saying is that we should make sure the entire facility blows up behind us - and that it dumps incriminating data onto the Kazon intetnet.

 

[Fouredged Sword]

So what you're saying is that we should make sure the entire facility blows up behind us - and that it dumps incriminating data onto the Kazon intetnet.

Click to shrink...

We will release their internet history to the wider Kazon public. Nobody will be willing to look them in the eyes.

Much to the confusion of the Voyager crew who having access to holodeck programs likely find whatever Kazon consider scandalous to be absolutely vanilla.

 

[DragonCobolt]

Adhoc vote count started by DragonCobolt on Aug 18, 2023 at 11:37 AM, finished with 24 posts and 11 votes.

• ---

  6 people have voted

  [X] Time to maximalize this: Sneak to the launch room, stun everyone from ambush, shut down the launch, steal everything, and leave.

  • w34v3r
  • ThatGazzer
  • QueenPally
  • Indivisible
  • Reese
  • Draz

  4 people have voted

  [X] There's our ride! Hack into the Ogla computers and drop in a nasty virus – after stealing whatever data you can of course – then reprogram the target for the test torpedoes before sneaking aboard, stuffing yourselves into where the warheads would have gone, for extract. It'll be just like one of your Japanese holodeck programs!

  • Spart117MC
  • Legionman
  • Rivenscryr
  • fanficfan

  1 people have voted

  [X] Lets try some sabotage. A stealthed phaser shot at a precisely chosen component, just enough to weaken it, to cause the whole launch to fail. In the confusion, sneak to the computer bay and start deleting stuff

  • Model DC.14F

We're doin it LIVE!

WE'RE DOING IT LIVE!!!!!!!!!!!!!!!

So, funnily enough, you have enough momentum that you can maintain momentum (2 Momentum) between rounds of combat. so, that means Kes AND Tuvok can open fire on the bad guys!

So, roll 2d20 versus diff 2, twice, for both of them pew pewing and we'll see how much damage ya do!

 

[Draz]

Pew pew!

Draz threw 2 20-faced dice. Reason: Kes! Total: 2

Draz threw 2 20-faced dice. Reason: Tuvok! Total: 28

 

[Draz]

Lol. 2 doubles is a 1 in 400 chance, I think?

 

[Fouredged Sword]

Kes stuns the bridge so hard random Kazon relatives in other star systems fall over feeling woozy.

 

[DragonCobolt]

So, Kes got 4 successes and Tuvok got 2 successes!

So, roll me 7d6 twice! Since phaser rifles are gnarly beasts, and both Kes and Tuvok are trained soldiers!

WE'll be spending Kes' two bonus successes to get +2 damage.

 

[Fouredged Sword]

Post for roll

Fouredged Sword threw 7 6-faced dice. Reason: Kes goes pew pew Total: 18

 

[DragonCobolt]

That's 9 damage and 1 effect: Kes KO's two Kazons!

 

[Fouredged Sword]

Post for second roll

Fouredged Sword threw 7 6-faced dice. Reason: Tuvok goes pew pew (but calm) Total: 22

 

[DragonCobolt]

That's six damage and three effects!

So, Tuvok stuns four Kazons!

there were six Kazons!

you did it!

Now, I'm going to work, but will post up the chapter between shifts! While I do so, debate among yourselves: Will I keep the next episode, Projection's, narrative as is, or toss it entirely?