To Prove One's Self/Faction Missions
Jump to navigation
Jump to search
To Prove One's Self: Borg
| Mission Name | 1st Crew |
2nd Crew |
3rd Crew |
4th Crew |
5th Crew |
Mission Text | Success | Failed |
|---|---|---|---|---|---|---|---|---|
| Android on Board |  |
 |
 |
AND |
Assimilating androids is an area in which the Borg has less experience. Five of Twelve enlists your crew's help in studying the effects of nanoprobes on androids. | It is difficult finding willing subjects (or cyberneticists willing to let anything Borg-related near their creations), but you finally manage to find a subject. The first tests are anything but promising, but you gather a lot of useful data. | DIALOGUE FAIL | |
| Competing Collectives | AND  |
AND  |
 AND |
News reaches you that the severed drones have been acting strangely. There is talk of assimilation and a new collective. Starfleet Command sends your crew to investigate. | Your crew investigates some of the witness accounts and finds out that the drones have considered the idea of creating a new Collective. It seems to only be an idea, but Starfleet's engineers get to work on ways to disrupt the assimilation process. | DIALOGUE FAIL | ||
| Faces From the Past | AND |
AND |
AND |
A civilian at a Federation outpost is spotted forcing an unconscious Borg drone into a shuttlepod. They manage to slip away before anyone can stop them and your team is tasked with bringing them back. | Your crew manages to track the shuttlepod to an abandoned mining asteroid. After an exhaustive pursuit, they catch up to the pair to learn thte civilian is a Huan man–and the drone was his wife who was assimilated four years ago. | DIALOGUE FAIL | ||
| Nightmares and Daydreams | |
OR |
|
|
OR
|
Some of the Borg drones who were part of B-4's crew are experiencing strange episodes, and on more than one occasion, a drone has become violent without obvious cause. Research this phenomenon. | Your medical officers study a drone who was taken into custody after a violent episode. You learn that it stems from the sudden way they were disconnected from the Collective. For now, the only solution is to get the drone to a regeneration alcove. | Your medical team attempts to study a drone after a recent violent outbreak, but they underestimate the drone's mental state and the drone unleashes a violent assault in sickbay. |
| Stolen Secrets | AND |
AND |
AND |
The Tal'Shiar have laid claim to the severed drones, accusing them of stealing state secrets, and have sent operatives to capture them, which has also led to promises of offensive action from the Borg if the drones are captured. | Your crew manages to intercept the Romulan operatives. You try to reason with them, but have also B-4 and the drones in advance. When the operatives refuse to back off, you let them go, but as you expect, B-4 and the drones have escaped. | Your crew attempts to intercept the Romulan operatives, but is too slow. By the time you reach B-4's location, he and the drones have already been siezed. | ||
| Tempting Fate | AND |
AND |
AND |
B-4 is still fixated on his goal of joining Starfleet like his brother, causing him to completely ignore what the Borg consider a generous offer. They ask you to serve as a go-between to help persuade him. | Your officers contact B-4 and share with him the Borg's offers–biological implants and an opportunity to further explore his capabilities among the Collective. They feels he holds great potential. B-4 is not convinced, but he agrees to give it thought. | Your officers contact B-4 and lay out the Borg's offer, as well as the alternative--deactivation. B-4 refuses to relent however, fixated on his original goal. | ||
| Usurped | AND |
AND |
AND |
While studying data on the brain structure of Soong-type androids, the Borg encounter the concerning possibility that bringing B-4 into the Collective could cause unintended consequences. They enlist your crew's help in finding a resolution. | Your engineers investigate the information you have on B-4's current state and finds a few possible options, though none of them are guaranteed to prevent B-4 from influencing the Collective. Starfleet Command asks you to keep that caveat to yourself. | DIALOGUE FAIL | ||
| Vengeance | |
|
|
AND |
News of B-4 and the severed drones has spread throughout the galaxy, causing heated emotions in those who have lost loved ones to the Borg. Several ships take off for B-4's last known location and Command sends you to intervene. | Your crew gets there in time to persuade the potential assailants to turn back. Convincing them to accept the reasoning behind the temporary alliance with the Borg is difficult, but you are at least able to convince them to stand down. | Your crew pursues the ships, but arrives too late to find a heated battle between B-4, the drones, and the angry victims of the Borg. You are forced to join the fray to end the fighting, but there will likely be casualties. |
To Prove One's Self: Section 31
| Mission Name | 1st Crew |
2nd Crew |
3rd Crew |
4th Crew |
5th Crew |
Mission Text | Success | Failed |
|---|---|---|---|---|---|---|---|---|
| For Science | AND |
AND |
AND |
Several prominent scientists within the Federation are arguing for the right to be able to study B-4 once he is deactivated and brought in. Starfleet Command asks you to vet the claims to B-4. | Your officers sit down and interview each scientists, many of whom come from fields other than cybernetics. Rather than making the final determination, you compile and condense the data and hand it over to Command to make the final call. | DIALOGUE FAIL | ||
| On The Run | AND |
AND |
AND |
Luther Sloane enlists your crew to help track down B-4 and the drones, as they've slipped away from their last known location and disabled all methods of tracking. | You travel to their last known location and track their movements and using other methods of locating them, finally succeeding by seeking concentrations of cobalt. But B-4 spots a shuttlepod belonging to another away team and his group escapes. | DIALOGUE FAIL | ||
| Privileged Communications | AND |
AND |
AND |
Luther Sloane has been monitoring the communications of B-4 and his crew, but has happened upon several encrypted messages he cannot decode. He asks your crew for help. | Your engineers and science officers work to decrypt the messages. They marvel at the sophisticated encryption method, unsure of whether it was B-4, the Borg, or both, and finally manage to decrypt them. | DIALOGUE FAIL | ||
| Proactivity | |
|
|
OR |
OR
|
A concern has been expressed about being able to take in B-4 with the Borg drones around. Dr Bashir is working on a prototype and he could use the aid of a keen-minded Starfleet crew. | Your crew works with Bashir. With B-4's drones severed from the Collective, your research shows their interlink transceivers are susceptible to a specific frequency that, when emitted from a tricorder, could incapacitate them momentarily. | DIALOGUE FAIL |
| Retribution | AND |
AND |
AND |
Reports of B-4's wild ride have circulated throughout the UFP and many people are insistent that no restraint be shown in handling B-4. These assertions and other anti-android sentiments have Data concerned. Ease tensions throughout the Federation. | Your officers visit outposts throughout the Federation to try and allay fears about what B-4 has done and what other android-like beings might do. The positive PR campaign seems to be making a difference. | DIALOGUE FAIL | ||
| Rights Erosion | |
|
|
AND |
Data has expressed his concern about B-4 being shut down. He fought to have the right to choose, but on top of that, he worries about the permanent effects of a forced shut down on B-4. Work with Data to address his concerns. | Even though B-4 isn't able to be reasoned with, with Data's help, you are able to figure out how to generate a backup of B-4's programming in the event he is damage during the shut down. | DIALOGUE FAIL | |
| Scars | AND |
AND |
AND |
An Admiral who lost his son to the Borg is furious that B-4's severed drone accomplices are being allowed to rejoin the Collective and could pose a future threat. He takes matters into his own hands and heads for a direct conflict. Stop him. | Your crew manages to intercept the admiral before he can even get within firing range of B-4's group. You try to persuade the admiral, not only of Starfleet's reasons, but of past instances of severed drones influencing the Collective. He relents. | DIALOGUE FAIL | ||
| Stranded | AND |
|
AND |
|
One of the Borg drones has stowed away aboard a pursuant ship, where he attempts to assimilate the vessel. The attempt overloads the severed drone, killing him, and causes the ship's computers to fail. Rescue the ship and her crew. | Your crew rushes to aid the endangered ship and her crew. You manage to arrive in plenty of time and try to repair the ship. You manage to stabilize the ship's systems, but still insist the crew board your vessel and proceed to a nearby outpost. | DIALOGUE FAIL |