Campaign of the Month: August 2017

Star Trek: Aftermath (Klingon Phase)

Phase II, Session 9
Rebuilding the Marathon, The Daystrom Institute, Ferengi Hijenks

And now, it’s story time!

Once upon a time, not very long ago at all, 4 ferengi went on shore leave and this is what happened….

FERENGI HIJINKS

Day 1 – Interrogations Begin – The Marathon docks at Starbase 134, the crew disembarks and undergoes intensive ‘interviews’ to root out Klingon spies and saboteurs….

After his interview with Starfleet Intelligence and waiting to be released from restriction to quarters, Ensign Adred (Leader Security Team 4) looked over a deal his family clued him in on, but he lacked the wealth to do it alone without family support (in other words, almost no profit for him), and even his family’s available funding likely wasn’t enough. He sought out his fellow ferengi crew members, LtJG Oopog (Helm 2), Ensign Guths (EPS Shift Leader 4), and CPO Dor (Comms 3, Female). Between them they had enough accumulated credits and GPL that, with clever leveraging through 3 false front corporate fronts and a few loans here and there from orion based sources, they could pool the necessary funds. Though Adred brought the least capital, he did bring the deal, which was enough for all to agree to split the venture equally (Starfleet’s influence must be rubbing off).

Day 2 – Interrogations Continue
While crew interview continued Adred chatted with the ferengi cartel via video. The business partnership was formalized between the Ferengi after much arguing and hissing, with much contention regarding the female Dor, but finally all agreed to allow her full rights and shares. Adred’s deal was a mining operation going bankrupt and selling off their equipment and the mineral rights of a dilithium rich asteroid in one of the Rigel belts to the highest bidder. Adred’s family had done some investigation into it and knew that with their mining techniques they would be able to extract more from the asteroid than others could, though the quality of the dilithium might be low. Since the asteroid appeared to be mined out there were few interested parties and none of them were offering close to what this asteroid should be worth when ‘properly’ mined.

Day 3 – Shore Leave, Day 1.
On shore leave, the ferengi vacationed in the way all ferengi do – with a business deal. Early that day the ferengi set off to examine the mine. It was a difficult mining operation to make profitable the way the orion miners were going at it, but it is a common situation among dilithium deposits the Ferengi mine, so they knew they could make it work. The profits would go to their families, and each of them had a relative with mining experience who can come in and oversee the operation. This let them all wash their hands of the operation and still fill their coffers, plus a bit for their families, for a basic brokering effort. By putting the funds into shell corporations and having family members manage the operation they were within the letter of Starfleet regulations and saw no issue with their actions. With little time to operate, they met with the orions and signed the deal by the end of that day and headed back to the asteroid to complete detailed scans, inventory, check the assets against their manifest, and prepare to begin operations, staying overnight in the small work facility built on the asteroid. They were awakened at roughly midnight by what felt like an earthquake. What they didn’t realize was that the orions felt cheated by the ferengi’s negotiating tactics and sold the information about the asteroid to some nausicans.

Day 4 – Shore leave, day 2.
All was well when they went to inspect the business initially, prior to purchase. However, nausican miners showed up and began poaching their asteroid, causing the shaking they felt. Afraid to contact Starfleet and shining light on their investment for people in the chain of command to see, they decided to confront the Nausicans with an attempted bluff. The Nausicans figured out where the ferengi were broadcasting from, docked with the work facility, told them not to come back, beat them senseless, and launched them into space in an escape pod. Their SOS is picked up and they are rescued by a transport ship who drops them on Rigel after giving them medical attention for broken ribs and torn ears.

Upon release from medical, Oopog, in a rage, insisted that they must defend their property, quoting Rule of Acquisition #25: “Fear makes a good business partner”. Agreeing with him, Adred suggested they hire Sophos Security Corporation, a private mercenary company his family was familiar with to help them enforce their claims. The Sophos Security Corporation is based on Mars in the Sol system but has a division on Rigel since they have many customers in this area. They sell their services as an elite ex-military & ex-mercenary force for hire and are a favorite among non-Federation races with assets to protect within Federation space. Sophos launched an immediate covert surveillance operation of the asteroid that evening, upon verifying receipt of payment, to discover the pirates seemed to be gone.

Day 5 – Shore leave, day 3.
The security teams set up on a nearby unclaimed and otherwise worthless asteroid, as the pirates still seemed to be gone. They quickly set up their defensive perimeter and quick launch hangers on their commandeered asteroid. Later that day the unsuspecting nausicans returned for another load. The mercs launched and confronted the nausicans in space, turning them back, none too gently as the nausicans went on the offensive. Lightly armed, outnumbered, and outmatched by 20 merc fighters, the 12 mining vessels broke off after losing 2 ships and retreated from the system. The ferengi were ecstatic, ordered replacement mining equipment from Ferenginar and sent gloating messages to their families to send people to begin operations in their mine immediately.

Day 6 – Shore leave, day 4.
Responding to the nausican pirate mining fleet’s request for help, 15 unmarked fighters and 10 frigates, matching nausican navy frigate configurations, rolled in on Rigel destined for the asteroid. Panicked mining operators throughout the area called Starfleet for help. Patrols from Starbase 134 were dispatched to assist the fighter pickets already in the area. They caught up with them at the asteroid where the nausicans were mopping up the last of the merc forces having lost 2 of their own frigates and 6 fighters. Seeing the battle in progress and the bombardment of the facility having already taken place the Starfleet commander, a brash young Lt Eric Johansson, ordered immediate action and all fighters in his wing to open fire. The onslaught took the nausicans by surprise, and they are overwhelmed despite enjoying greater numbers than Starfleet. Within 2 minutes 4 Starfleet destroyers joined the fight and the nausicans chose to retreat from the system. The nausicans communicated as they retreated, “This is a day that will be remembered and avenged! You have killed the son of Warlord Kr’Kall’a!”

Day 7 – Last day of shore leave.
While investigating the matter, the actions of 4 Starfleet ferengi came to the attention of the Federation Marshall Service. Specifically, how their actions, while correct and within the letter of the law and regulations, created this incident. The son of the second most powerful Warlord on Nausicaa was killed in combat with Starfleet and his clansmen have vowed revenge – something they are famous for fulfilling. The order to take the ferengi into protective custody was sent though channels to the security forces of Starbase 134, and a team was dispatched. Upon beam in they found Oopog lying on the floor of a wrecked café in the main city on Rigel III, Chellar, talking to the local constabulary and being treated for minor cuts and abrasions, but no sign of Adred, Guth, or Dor. His statement reads, “We were just minding our own business when 4 large, armed people beamed in and assaulted us (the pair of ferengi). They managed to subdue Adred and Dor and beamed out with them when you [the security team] arrived.” Adred’s comm badge is among the debris, Guth’s isn’t but it isn’t functioning either apparently. Dor is found nearby hiding in a garbage shoot. Oopog and Dor are to be interviewed and returned to his captain to determine their disposition. Since the ship they serve on is on a high priority mission, no charges are being preferred at Starbase 134, leaving such matters to their captain’s discretion. However, the ship the abductors beamed up to has broken orbit and left the system at high warp on a course for Nausicaa, presumably with Adred aboard. End of report.

Later that day, an attempt to transport Oopog and Dor fails due to quick intervention on the part of Starfleet Intelligence, who has him under surveillance. The ferengi are suspected of being operatives of the Klingons, though there isn’t any proof at all and they passed their “interviews” with flying colors.

View
Phase II, Session 8: Starbase 134
You didn't see this coming....

NEWS FROM THE FRONT:

This…is FNN. Wolf Sanders reporting.

Reports of Klingon atrocities in occupied Romulan space are as expected: brutal, cruel, and frequent.

The forces of House Monak were repelled in their offensive against Talvath, a prime Romulan resource world.

House Dagot, holding Khazana, had been stalled since the opening days of combat, but now is being pushed back. Intelligence believes their forces have been hardest hit by ship reallocations from the assaulting forces to shore up the forces building up along the Klingon/UFP borders.

In the Romulus sector Klingon forces continue to engage the Romulans in heavy combat. 3 Klingon houses have been identified so far in the operation – Mur’gek, Volas, and B’Tori, none of them being high ranking houses in the Klingon social/military structure. Klingon tactics are focused on support vessels and lighter ships, leaving capital ships unengaged but stripped of outer fleet defenses. Klingon casualties are very high, especially among B’Tori forces, but the tactic is effectively leaving the Romulans with little ability to protect the evacuation operation, and it may have to be called off. The evacuation fleet, already injured in the initial assault, is down by a further 30%, though only 3 Starfleet vessels have been destroyed since the opening days of the war, all of them freighters caught incidentally in the blasts of other destroyed ships. In fact, the Klingons are taking great care to not target or damage Starfleet vessels in the area. 3 Starfleet Carrier Battle Fleets are operating in the area to protect the shipping and have seen some action, but it seems limited to rogue and overzealous Klingon ship captains in the fog of war rather than a deliberate effort to engage Federation forces. The USS Nimitz experienced minor damage to its starboard nacelle in a “friendly fire” incident from a Romulan D’deridex warbird.

Information from other sectors is mixed and confused, with worlds changing sides frequently. The Klingons employing their “hammer strike” tactics against Romulan strong points, the Romulans employing deception with hit and run tactics to harry Klingon forces and break up their attacks while sustaining little injury themselves, and engaging in large, overwhelming offenses behind Klingon lines. Still, their major supply and repair worlds in the area are cut off, forcing them to abandon wounded vessels or tow them great distances for repair, both costly choices.

Romulan forces stationed in Cardassian space have been called up, leaving only a skeleton fleet to protect their interests there. The Romulans have asked the Federation to help them protect their interests in the area, but the Federation hasn’t given them a decision on the issue yet. Meanwhile, the Cardassians are petitioning the Federation to stand aside while they “negotiate” with the Romulans for their lost worlds. Klingon forces in the Cardassian sector have become very aggressive, launching 3 unsuccessful small probing offensives against the Romulan worlds there and shooting at everything on their paths both to and from the Romulan holdings.


Star Fleet Intelligence Report:

Star Fleet Intelligence Captain sends instructions to the Captain of the USS Marathon. In it she mentions that the sabotage is a not so subtle communication from the Klingons to the Federation.

FULL MESSAGE FOLLOWS: Received via subspace message, personal communiqué for Captain’s eyes only:

(She’s a salt and pepper haired woman in her mid 50’s, linebacker build, intense eyes, looks like she used to be pretty but it now just stern and domineering) Captain, this is Captain Jessup, Starfleet Intelligence, Romulan sector. I can’t begin to tell you how disturbed we are to hear of your sabotage incidents. This corroborates a far reaching infiltration into Starfleet’s support services branch that has been under investigation for the last 7 months. We hadn’t realized how deeply some of their operatives had been hidden, and we’re positive we haven’t cleaned them all out yet. There’s every possibility that you haven’t seen the last of the sabotage on your ship yet.

You should be aware that the USS Pydna experienced some sabotage efforts, though not on the scale you encountered, and not until they were well into their mission. An Orion saboteur was found at Starbase 241. At Cardassia Prime, we believe we found another infiltrator, but this one slipped away from us before we could capture him and seems to have disappeared into the Badlands. There was extensive genetic alteration, so we’re not even sure of the race and sex of the infiltrator, but we are continuing our efforts to obtain the target.

In many ways, this is a not so subtle message from the Klingons to the Federation. We believe that these infiltrators were setup to be caught, and if the one in custody is any indication, they don’t have any deep intelligence to give us. We read the Klingon message as, “Stay off our boarders and out of the Romulan invasion or you’ll have a war on our hands.”

Indications are that the Klingons are prepared to make good on such a threat, positioned to immediately launch a strike into Federation territories with no notice and striking hard at our defensive positions. Furthermore, there seem to be stepped up efforts from their diplomats to convert a great many neutral and weakly loyal systems to the Klingon side. Above all, they are prepared to stop you at all costs and damn the consequences. Much the same thing is going on with the Pydna, though to a lesser degree. This is why you have your escort ships available to you, and we only wish we could spare you more. Good luck on your mission captain, Jessup out.”


Admiral Burtell’s Update:

The captain receives a recorded message on a private channel from Admiral Burtell:

Attention Captain, Command Crew, Chief Engineer, USS Marathon:

As a result of the sabotage done during the Marathon refit, Starfleet Intelligence, in cooperation with Starbase 234 Special Operations, has ordered a complete, MANUAL, level 1 diagnostic and component by component teardown and scan at Starbase 134 on Rigel. This will also gave Starfleet time to deliver a new warp core and nacelle upgrades to the Marathon, freshly constructed at Utopia Planitia under level 1 security protocols, and delivered by the USS Sentinel. The Sentinel along with Battle Group 33, which it serves as flagship for, arrives at Starbase 134 three days after the arrival of the Marathon.
Kindly do all in your power to prepare your ship for this process. The faster it is completed the faster we can get you back into space.

You’ll additionally be glad to know that the Warptug USS Brazos was dispatched and has recovered USS Voodoo and is en route to Starbase 134 where she should be repaired in plenty of time to deploy with you after you are again spaceworthy. All damage BG28 has suffered should be taken care of and those ships should be fully operational by the time you are.

Regards,
Branch Admiral Burtell
-———————————————————————————————
This additional message is included:

Captain Morgan, welcome back! We’re glad you made it back in one piece, more or less, and we’ll get you fixed up and back out to space ASAP. Nice work on the Ipsus crew as well. The intelligence boys are prying all kinds of things out of that Klingon crew captured on your trip back here. Nice work there as well! It seems that what you ran into was just the tip of the iceberg. I’ll have them give you a full intelligence briefing once you’re settled (see Captain Jessup’s report).

In the meantime, the PR boys have had quite a time spinning your story to the press. Prepare yourself and your senior personnel for the cameras – they’ve got interviews lined up with all of you. The intel boys will cover what you can and can’t say. Before you say anything, not my idea, out of my hands, don’t bother.

As for your ship, nice job on catching the saboteur! Hmmm, I’m not in the habit of saying ‘nice job’ this often – it’s a nice change of pace. Anyway, you’ll be down a bit. Since it seems that the Klingon operatives had the run of your ship during its refit, Starfleet ordered a complete, MANUAL, level 1 diagnostic and a component by component teardown and scan at Starbase 134. The bad news is that you’ll be down for the better part of 5 weeks under normal circumstances. The not so awful news is that because you are on such a high profile mission you’ve bumped everyone else out and have first right of refusal on all labor, parts, and specialists until you’re space born again. They’re projecting 17 days, but we’ll see. On the positive side, this will give Starfleet time to deliver a new warp core to the Marathon, freshly constructed at Utopia Planitia under level 1 security protocols, and delivered by the USS Sentinel – Admiral Sesat’s flagship – when he rolls through here with Battlegroup 33 on his way to his new posting at Deep Space K-7. The Federation Science Council wants the Marathon’s warp core for study, so looks like you’re getting a new one, and its next generation at that, complete with upgrades to your nacelles as well making you the fleet’s only TW-3 ship.

Your crew will be debarked and detained for 2 days, and all key crew members will be debriefed on the events surrounding the sabotage. Any crew that Starfleet Intelligence needs will be detained for further questioning. We will do our utmost to insure a clean, un-tampered with, loyal crew for you when you return to your mission, captain. After that, we’re granting you and your crew 5 days shore leave (within 1 system of Rigel and Starfleet Intelligence monitoring), after which I’m sure they’ll be anxious to help put the ship back together and get her ready to return to action as soon as possible. I’m authorizing the facilities on Rigel 2 for your crew who can qualify for it. For everyone else, Risa is close and I hear it’s nice this time of year. No quibbling on this captain – you and your crew may not have a chance at any R&R for quite some time. We need them off the ship anyway so we can do depressurized work for a bit.

OK, that’s mostly it; prep your officers for interviews, prepare for debriefing, have a good time and be safe and make good decisions on shore leave, then get your ship put together and back to work ASAP. Burtell out.”
-—————————————————
Computer Record: Rigel II – Need to Know Basis, Top Secret Clearance Required. Federation scientists have worked with the REDACTED. Visitors are given REDACTED. Orbiting hotels accommodate all guests and scientists visiting this world. With the advent of REDACTED but still remains at the top of the “must do” vacation lists of the rich & famous, and those who wish to emulate them.
Same entry upon clearance approval:
-—————————————————
Computer Record: Rigel II – Amusement Planet. Automatically reads the minds of visitors and presents them with their thoughts made reality, even if these realities are dangerous or deadly to the visitors. Federation scientists have worked with the AI system running the planet and managed to place some rudimentary safety protocols into its thinking. Visitors are given strong safety briefings and mental discipline training before being allowed to visit the planet, and visits are restricted to no more than 2 days, with no sleeping allowed. Orbiting hotels accommodate all guests and scientists visiting this world. With the advent of holodecks, its popularity has dropped off, but still remains at the top of the “must do” vacation lists of the rich & famous, and those who wish to emulate them.


Note: Battlegroup 33 is 4 days away from arrival at Starbase 134 at the time of the Marathon’s arrival at Starbase 134, arriving at the end of the day of the medal ceremony.

USS Marathon Upgrade Technical Review:
NEW WARP CORE: Starfleet is taking this opportunity to upgrade the USS Marathon with the FTW3 warp core from previous their FTWC-2. Whereas the FTWC-2 physically looked like a standard warp core with 2 half-sized cores attached 2/3 of the way up, the FTW3 has 3 half-sized cores arranged equilaterally roughly ½ along the main core. This is the first field deployment of the unit. Please see technical manual for full details.
4th_Generation_Warp_System_Diagram.JPG

PERFORMANCE EXPECTATIONS:
• In solo flight this core, properly configured with FTWC-3 Engines, should propel the vessel at TW10 in solo flight, a step up from the previous TW9 speeds.
• It is expected to enhance the ability of cutter ships to create STWCs, though to what degree is uncertain.
• Most impressively is its ability to operate in “expanded” mode. In expanded mode the speed is reduced to TW9, however, the conduit is substantially increased in size and capacity, allowing multiple ships to travel along with the cutter ship. The greater the number of ships traveling in the conduit the greater the instability of the conduit and the shorter the distance it can be maintained. (Note: An unstable conduit simply disintegrates dropping all vessels within it back into normal space, unlike a conduit rupture, and this outcome has been deemed to be safe for all involved after recording thousands of such destabilization events with no negative effects in live testing as well as simulations.)
• This core relies on the same ejection system as the previous model.
Disposal of previous cores: The TransWarp cores of the USS Marathon and the USS Ipsus are both being transferred to the Daystrom Institute Warp Research Annex, located in orbit of Rigel III (Chelar) for detailed research. When available, the senior engineering officers of the Marathon have a standing invitation to participate in the research being conducted there.
TransWarp_II_System_Diagram.JPG

ENGINE UPGRADE: The USS Marathon Nacelles are being refit to bring them up to spec for FTWC-3 certification to match your new warp core.
TransWarp_III_System_Diagram.JPG

STRUCTURAL INTEGRITY FIELD: The USS Marathon is receiving a new enhancement to its structural field. This is the same system being deployed aboard the Guardian Class Battleships being deployed now. It will effectively increase your superstructure points by 48%, has an independent temporary battery supply, which will be useful should help you ever find yourself in the crushing effects of the TransWarp Domain again. It’s potentially handy in a fight as well.


PRE-INTERVIEW BRIEFING BY STARFLEET INTELLIGENCE OFFICER QUINCY:
• Commander Loraine Quincy’s Pre-interview PR/intelligence briefing –
Don’ts:
• Do not discuss Klingons attacking you in the TWC, but the attack once you were out is fine to discuss in general terms.
• Do not discuss an accident of ANY KIND having to do with any TWC.
• The crew of the Ipsus are heroes and not to be portrayed in any other light.
• The mission was a Starfleet rescue operation mounted to save people in an unfortunate circumstance, comrades in trouble, that kind of thing.
• Do not discuss sabotage, infiltrators, or enemy operatives. Your ship was fully operational at all times until exiting TW Domain space, and you suffered damage in the process of escaping it.
• Romulans are not to be mentioned regarding any space combat involving BG28, or at all for that matter. You have no opinion of what’s going on in Romulan space.
• Do not taunt happy fun press. Don’t think of this as a press conference so much as a misinformation briefing for our enemies and a public image bolstering session for our Federation citizens.
Do’s:
• The crew of the Ipsus are heroes and not to be portrayed in any other light.
• The mission was a Starfleet rescue operation mounted to save comrades in an unfortunate circumstance.
• Present yourself as prototypical Starfleet personnel who care so much more about others than themselves it’s sickening.
Your objectives here are to:
• Build, or at least not damage, confidence in the TWC system.
• Keep operational information about the capabilities of your ship and the TWC system secret.
• To keep the public calm and confident in Starfleet.
• To further the image of the heroic crewbeings of Starfleet.
• As much as possible, to honor your heroic and good work.
-—————————————————
THE MEDAL CEREMONY:
As the Federation Anthem blared in the hall, ended, then repeated, and repeated, and played over and over again for the next 3.72 hours, the crew gathered in formation and the officers arrayed themselves on the Dais while the exploits of their amazing adventures (heavily edited) were read to the throngs of Admirals and up and comers gathered there to be seen by important higher ups who were also there or would know who was there. The Award was read aloud and then pinned to the chest of each officer (and simply passed out to the crew members.

GM Note:

  • Captain and crew of the USS Marathon, please update your characters with the following tour event: Parasitic Infection – you (if you had a headache), or your crew (if you didn’t).
  • Captain and crew of the USS Marathon, please update your characters with the following award: Citation of Conspicuous Gallantry. If this is your second time to receive it then add “With Cluster” at the end of it. If you have received it twice already, add “With Clusters” (note the plural clusters). If you have received it more than that refer to the following:
    4th – Clusters with Alba Leaves
    5th – Clusters with Alba Branch
    6th – Clusters with Alba Branch and Frocking
    7th – Heavy Frocking
    8th – Heavy Frocking with Cluster
    9th – Heavy Frocking with Clusters
    etc….

The Reading – Honorific: Citation of Conspicuous Gallantry
Awarded: Captain Alexander Morgan, USS Marathon, commanding (insert your name and rank here if you discover you are not Captain Alexander Morgan)
Citation: While trapped in an unknown dimension of space in the vicinity of Regulus, and enduring various distresses and failures within this space, the Captain and crew of the USS Marathon did detect, find, and rescue all surviving hands aboard the USS Ipsus escaping said inter-dimensional space and returning to Federation space, attempting to take the Ipsus in tow with her, though this ultimately turned out to be impossible. The decision to do so resulted in the recovery of five souls and the bodies of many of the crew of the Ipsus, which provided comfort and closure to their families. The warp core of the USS Marathon and data collected will be donated to Starfleet’s Space Sciences division to provide valuable scientific evidence to further the goals and aims of the United Federation of Planets. Captain Morgan is recognized for his clear thinking and positive risk taking in the face of unknown adversity, and the entire Crew of the USS Marathon is commended for their brave execution of their captain’s orders in uncertain and hazardous conditions.

Ship Honorific: Citation of Conspicuous Gallantry
Awarded: USS Marathon, NCC-72002, Captain & Crew
Unit Citation Reading: As per above.

Note: Battlegroup 33 is 4 days away from arrival at Starbase 134 at the time of the Marathon’s arrival at Starbase 134, arriving at the end of the day of the medal ceremony.

-———————————————————————————————

What Happened:

TIMELINE OF EVENTS:
-8 Days – Marathon begins moving towards Starbase 134, contacts BG28, saboteur discovered broadcasting their position, found, Nausican scouts show up, scan, and scoot. BG28 steps up to warp 9. – Previous Adventure Log
-7 Days – Klingons arrive to attack Marathon, then more of them, Marathon kills 2 (including ship with the USS Bull Run’s sensor pod on it’s nose), BG28 meets up with Marathon, fighting and escaping. – Previous Adventure Log
-6 Days – USS Ob Warptug arrives, takes Marathon under tow, fleet moves faster but USS Voodoo badly mauled and has to be left behind (all crew rescued).
-5 Days – Harassed by Klingons and Nausicans.
-4 Days – Harassed by Klingons and Nausicans.
-3 Days – Harassed by Klingons and Nausicans.
-2 Days – Harassed by Klingons and Nausicans.
-1 Days – Harassed by Klingons and Nausicans, Starbase 134 picket joins BG28 and Klingons and Nausicans break off their attack.
0 Day – Arrived in Rigel system, met by honor guard of 67 Starfleet starships and many 144 fighters (gross!), who escorted the Marathon into system, delivered her to Starbase 134, and put her into repair yard Alpha 3. Complete with a congratulatory message from Admiral Uunaimed (human, male) of the USS Random (Galaxy III) flagship of the Starbase 134 picket) in full dress uniform (along with a miffed and uncomfortable looking crew in the background). The crew was politely disembarked onto a waiting personnel transport (space bus) and landed at Starbase HQ on Rigel IV where they were assigned quarters. Enlisted were assigned private officer grade quarters, officers received VIP quarters. The Command staff and Department Heads are given rooms in an admiral/ambassadorial suite complete with a 3 living areas, a staff room, and 2 conference rooms, Star Fleet Intelligence officers posing convincingly as serving staff. All crew members are separated from their luggage and belongings. Lt. Th’azyron bemoans the separation from his weapons, all hidden knives and phasors having been confiscated from him upon exiting the transport. Senior officers receive agenda message for upcoming events and are otherwise left to mingle among themselves until escorted to their quarters and locked into them. All crewmembers are locked into their quarters and are isolated.

+1 Days: The following morning, going in order of rank from high to low (except for the Ferengi whose interrogations go for a full 2 days and ‘alternate techniques are used’ as they are psionically resistant, their files receive the addition, “Person Of Interest”), the Captain is interrogated for 2 hours using invasive psionic techniques and being questioned while in that state. Surprising many, he is declared clean, as are all other senior officers. Following the senior officers interrogation sessions, they find they have been moved to other quarters, still VIP level, but each suite has adjoins common room where all can meet and interact.

+2 Days: Interrogations continue, all Civilian Specialists are cleared as are all but 1 officer, and the interrogation teams (35 of them) are working their way through the crew. By the end of the day another 4 (5 total) potential threats are found, removed, never heard from again. The psionically sensitive among the crew note that during their ‘interviews’ as many as 12 other psi’s or sensitives were present nearby and ‘tuned in’.

Commander Loraine Quincy joins the officers and gives them their pre-interview PR/intelligence briefing for the upcoming press conference many of them didn’t know was going to happen and now get to dread. He told them the do’s and don’t as follows:
Don’ts:
• Do not discuss Klingons attacking you in the TWC, but the attack once you were out is fine to discuss in general terms.
• Do not discuss an accident of ANY KIND having to do with any TWC.
• The crew of the Ipsus are heroes and not to be portrayed in any other light.
• The mission was a Starfleet rescue operation mounted to save people in an unfortunate circumstance, comrades in trouble, that kind of thing.
• Do not discuss sabotage, infiltrators, or enemy operatives. Your ship was fully operational at all times until exiting TW Domain space, and you suffered damage in the process of escaping it.
• Romulans are not to be discussed. You have no opinion of what’s going on in Romulan space.
• Do not taunt happy fun press. Don’t think of this as a press conference so much as a misinformation briefing for our enemies and a public image bolstering session for our Federation citizens.
Do’s:
• The crew of the Ipsus are heroes and not to be portrayed in any other light.
• The mission was a Starfleet rescue operation mounted to save comrades in an unfortunate circumstance.
• Present yourself as prototypical Starfleet personnel who care so much more about others than themselves it’s sickening.
Your objectives here are to:
• Build, or at least not damage, confidence in the TWC system.
• Keep operational information about the capabilities of your ship and the TWC system secret.
• To keep the public calm and confident in Starfleet.
• To further the image of the heroic crewbeings of Starfleet.
• As much as possible, to honor your heroic and good work.
The officers discuss and debate and formulate their press strategem. While they are doing this, most of their personal belongings are returned to them. By end of day, all personal effects are returned.

+3 Days: Everyone puts on their dress uniforms (which is basically a dress) and prepares for their award ceremony. (see Above)
Following the ceremony (10:00am local time) the senior officers enjoy a very dry and tedious 4 hour reception. There they meet the top local brass including Admiral Burtell, dignitaries, members of the press, high-level business people, and defense contractors. (It’s really a LOT of fun…hors d’oeuvres, drinks, lots of press, lots of brass – the perfect cocktail to destroy a career, or make one). No carousing are blown as far as we know (can’t say the same for all the admirals), and all is well. Finally, at 2:00pm the press conference gets under way.
MEET THE PRESS – Interviewed by:
• Wolf Sanders (human male) of FNN (Federation News Network)
• Sorva (vulcan male) of The Rational Enquirer (Information stripped of emotionalism and mysticism)
• Mott Fruis (bolian female) of The Freedom Group (syndicated talk show)
• Stanton Meriwether Haventhorp (human male) of Modern Spacefarer Magazine (For private ship owners, promoting the interstellar yachting lifestyle)
• Jali Moenserg (denobulan female) of The Plain Truth (dumbing down the news for the average Joe since 2219)
• 20 other miscellaneous newsletters, publications, talk shows, blogs, and public rumor mongers of various races and sexes
In a private reception for the senior officers, they are officially “pinned” (again, it’s a photo op) with their awards in front of a small audience (all at the Fleet Captain level and above, many of them Starfleet Intelligence officers). Afterwards, the members of the press corps of Starbase 134 are introduced. The media feeding frenzy gets underway. The incoherent 1st Officer (only entirely drunk) is the highlight of the show.

Press Conference Interview Questions:

1. Captain:
A. Stanton Haventhorp of Modern Spacefarer Magazine – How did you know you weren’t in normal space anymore?
B. Jali Moenserg of The Plain Truth – What was it like in that strange dimension you were in?
C. Mott Fruis of The Freedom Group – Did anything happen to you and/or the crew while you were in there? Did you see any interesting creatures or make first contact with anyone?
D. Wolf Sanders of FNN – How did you find the Ipsus?
E. Wolf Sanders of FNN – How did you buoy up the spirits of your crew when you learned the grisly fate of your sister ship?
F. Wolf Sanders of FNN – Will you be returning to this new area of space for further exploration? Follow up: Do you know how to return to this new part of space?
G. Sorva of The Rational Enquirer – With this being your first command and being so new to the captain’s chair and in such a high stress situation, how did you get the crew to follow your orders?
H. Can we see your new medal? Can you tell us how you felt when you received it please?
2. 1st Officer (too drunk to answer), Tactical Officer:
A. Sorva – Did you agree with your captain’s decision to fly into an unknown dimension of space?
B. Wolf – If you were in command, what would you have done differently? Follow up: How often do you find yourself at odds with your captain like this?
C. Stanton – At any point, were you close to needing to relieve the captain of command for the danger he put the ship and crew in?
D. Jali – What did you feel when the Ipsus first came into view?
E. Mott – How did you grieve for the crew of the Ipsus and help the crew of your ship to come to grips with the losses?
F. Sorva – Considering your situation and ship’s condition, was the effort to attempt to rescue the Ipsus logical?
G. Mott Fruis – I had a brother that served on a dangerous Starship a few years ago and he nearly got killed on several occasions. Is that why you serve commander – for the thrill and adventure of it?
3. 2nd Officer:
A. Jali – What does a 2nd Officer do? No, I mean in a crisis situation like this – are you like a spare 1st Officer?
B. Wolf – What did you do during the rescue operation?
C. Mott – Were you expecting trouble from the survivors, or maybe alien intruders, or anything like that?
D. Stanton – Was it hard to keep your people calm and focused during the rescue, or was there some panicking?
E. Stanton – In the fight with the Klingons, after you returned to real space, how badly were you outmatched?
F. Did the Klingons damage the Marathon? Is that why you’re in the ship dock for repairs?
G. Sorva – Do you feel the decisions of your captain to rescue the Ipsus were commendable or foolhardy considering you could have all been killed in the attempt?
4. Chief Engineering Officer:
A. Wolf – How long has Starfleet known about this new dimension of space and why are we just hearing about it for the first time?
B. Mott – Are there plans to return to this new dimension, and if so how will you do it?
C. Jali – First, you’re a genius, and now a hero. I have to ask, and our audience is dying to know, are you currently seeing anyone?
D. Sorva – Were you able to learn anything that will help refine the work of of Dr. Sethis of the Vulcan Science Academy, whose equations make TransWarp Conduits possible?
5. Ops/Helm Officer:
A. Stanton – How did you know how to fly in that new dimension? Was everything weird, like backwards, upside down, or reacting funny, or something like that?
B. Jali – Would you like to go back and explore it further?
6. Medical Team Leader:
A. Jali – Have any of the crew grown strange appendages, odd skin, changes to their foreheads, or developed amazing new abilities as a result of exposure to this new area of space you were in?
B. Wolf – How are the surviving crew of the Ipsus doing? Is there any chance we can talk to them?
C. Wolf – What was the interior of the Ipsus like?
D. Stanton – Was it dangerous getting on board her? How did you do it?
E. Jali – Weren’t you afraid of getting germs or parasites or something from them? I mean, they’ve been here in unknown space for months – there could have been anything over there!

How It Turned Out

The publicity ploy of Starfleet PR of holding a press conference with the senior officers of the Marathon has had mixed results:
• Wolf Sanders of FNN, human, male (Federation News Network) – Gives a straightforward accounting of the fiction that Starfleet Intelligence spun, painting the crew as heroes and the work as nail-biting drama to save the desperate, but oh-so-brave, survivors of the Ipsus, pulling off the amazing feat of recovering the ship and deceased crew members of the ill-fated ship as well. There’s talk of a movie of the week with Jason Spurgeon (vid star and sexy hunk) playing the captain and Marvin Grayson (comedic genius) playing his comic relief as the First Officer.
• Sorva of The Rational Enquirer, vulcan, male (Information stripped of emotionalism and mysticism) – Gives a biting article on the ill-advised attempt with a high likelihood of failure and loss of yet another ship and crew under the command of an untested captain with a yes-man first officer which succeeded purely by random chance and the scientific and engineering efforts resulting from the intensive study of the theories of Dr. Sethis of the Vulcan Science Academy. The human instinct to venture into every possible place and situation they can has once again ended in near disaster, only averted by the most unlikely perversions of chance.
• Mott Fruis of The Freedom Group, female, bolian (syndicated talk show) – The Klingon attack against the Marathon occupies nearly 70% of the broadcast with each of the panel members having a different take on what it could mean to the security of the boarder planets, all of them bad. The potential for changes in the physiology and psychology of the crew and potential first contact with new, threatening, species take up the remaining time allowed. A very brief spot in the beginning and end of the show discuss the heroic rescue, the plight of the Ipsus, and the glory seeking aspect of Starfleet (showing the crew getting their medals as they say this).
• Stanton Meriwether Haventhorp of Modern Spacefarer Magazine, human, male (For private ship owners, promoting the yachting lifestyle) – Starfleet, as always, is jealously guarding the information that could be critical to the captains and crews of civilian craft using these STWC’s. However, that Starfleet has the capability to not only enter this domain, but to find and effect a rescue is encouraging. At this time, the recommendation of Modern Spacefarer is to use the STWC network only as necessary, but with reasonable confidence.
• Jali Moenserg of The Plain Truth, female, denobulan (dumbing down the news for the average Joe since 2219) – The crew is so brave, their mission so AWESOME, this new area of space so mysterious, and such an eligible BACHELOR on board as well! A detailed description of how the senior crew, especially the chief engineer, looked in their dress uniforms, how they plan to go back and, “just rescue everyone ever who got stuck in there”, and hints at how a certain commander, who is still single and shall remain unnamed, may have been flirting with a certain reporter.
• 20 other miscellaneous newsletters, publications, talk shows, and public rumor mongers – It seems obvious from a general reading/viewing/listening to the material coming from the press conference that someone leaked information about people in TransWarp space turning into lizards (unfounded, denied by Starfleet Intelligence and Starfleet Medical) and a rumor regarding discord among the crew, in particular the first officer and the captain, has been circulating. The sources of both of these is under investigation by Starfleet Intelligence. Starfleet Intelligence is generally pleased with the press conference regarding their objectives, misinformation and information dilution/deflection, and issues they wished to keep secret.
:
-————————————————————

Admiral Sesat and Battlegroup 33 arrives at Starbase 134 at the end of the day of the medal ceremony. He entered the hall where the medal ceremony was held and the remnents of the party were still enjoying the food, drink, and political maneuvering. He approached several very senior admirals, boiling mad, and had a conversation at a low volume that eavesdroppers would describe as ’couldn’t really hear much, but there was a lot of hissing’. Spotting the Captain in the room, he composed himself and marched over to make the obligatory congratulations and introductions. He told the Captain that he had his new warp core on board, that the Captain should be very grateful to him for bothering to use his battleship as a transport, and that he’s better put it to good use. Then he took the Captain by the arm and walked him into a small side room where they remained for roughly 4 minutes and talked about who knows what? Admiral Sesat then left the room and the event, beaming back to his flagship. Admiral Burtell then briefly entered the room, emerging 2 minutes later and looking very troubled. The Captain exited the room and twirled his mustache.


SHORE LEAVE

+4 Days: Begin shoreleave (hold on to your butts!)
Several officers choose to go to Rigel II, including the Chief Engineer, and all of them are able to pass the discipline training and get to go down to the planet and enjoy the amusements to be had there – except the Chief Engineer. The events that occured on Rigel II are classified and can only be found in the personal journal’s of the participants and we shall examine this time no more.

The remaining officers (including the Captain), and after 2 days of struggling with discipline training the Chief Engineer, head to Risa. There are many events that happen on Risa, including a Vulcan pon farr, but what happens on Risa stays on Risa and we shall examine this time no more.

+9 Days Shoreleave ends (release your butts!)
The Chief Engineer gets invited to the Daystrom Institute on Rigel III, bargains to bring 2 people with him, and offers these slots to his assistant (who would have been invited anyway) and the Captain.

Tired of the drinking issue and eager to test his ability to get anything and everything he wants, the Captain had his 1st Officer transferred off the ship and promoted his Chief Engineer (who had just become a chief engineer and held the position for only a few days now) to that position. He promoted the Assistant Chief Engineer, Lt Christina Williams (his former girlfriend that he seems to still be interested in) to Chief Engineer, and he made his tactical officer, Lt. Th’azyron, his new second officer. A new Assistant Chief Engineer is now being vetted to join the crew.

View
Phase II, Session 7: The Long Road Home
Cat and Mouse with Klingons

With the Captain and 1st officer indisposed the 2nd officer and chief engineer took over command. His first official act was to transfer command function to engineering where he could more effectively do both jobs. Just before the Klingons appeared, the chief counselor reported that the two sane-ish Ipsus survivors were actually doing worse emotionally now than when they first entered the ship and that there was little that could be done for them at this time. The Captain had wanted reports on their condition, so this was his report. Then he simply sauntered away.

The Chief Operations Officer received an openly broad but encrypted communication from Starbase 134, thus blowing radio silence, notifying the Marathon that Battlegroup 28 was headed their way at warp 9 and that a warp tug was moving to them at warp 7.

About those Klingons…. 2 Vor’cha entered sensor range and rapidly closed with the USS Marathon and matched her warp speed. Chief Science Officer Jog scanned and discovered they were accompanied by a third cloaked Vor’cha, and it was running a normal cloaking device. They bumped up their speed and began to close with the Marathon. At roughly this moment the 1st officer, having recently been returned to duty by medical made his dramatic and imposing entrance onto the bridge and promptly assumed command, much to the relief of the 2nd officer who then threw his full attention into the engineering functions. The results of his renewed attention was a spectacular effort that allowed the ship to drop from warp 5 to warp 3 twice as rapidly as any ship should sanely do so, especially when damaged as badly as the Marathon was. The XO gave it the token, “Make it so” sort of thing (it was actually, “Yeah, ok, do it”) and the Marathon’s sudden deceleration caused the Klingons to blow right by and many times the speed of light relative velocity.

Vor_Cha_Image.jpg

IKS Uvas Shalloss

When next the Klingons matched speed with the Marathon they were accompanied by a second group consisting of 1 Vor’Cha battlecruiser and 1 B’rel Cruiser separated by 500,000km, no ships were cloaked as far as Lt Jog could tell. Again, the Chief Engineer did miracles with the engines and the Marathon out accelerated both groups of Klingons.

The group with the B’rel cruiser, now identified as the IKS Soikra and mounting the Starfleet sensor pod from the USS Bull Run, and the Vor’cha battlecruiser IKS Uvas Shalloss were the first to catch up with the Marathon. The first officer ordered the ship to attack and the Helmsman (no character info available) brought the ship around as the Chief Tactical Officer readied what remained of the ship’s weaponry (nothing functional on the port side).

B_Rel_Cruiser.png

IKS Soikra

The Klingons closed on the Marathon but held their fire until they were very close, as did the Marathon, both ships intent on making these shots count. The XO’s superior tactical skill won out enabling the Marathon to get the first shot off, and Lt Th Azyron put everything into exacting vengence upon the Soikra, the ship that caused the TW Domain that nearly killed them 2 scant episodes ago. The 4 phasers punched a hole in the Klingon’s inferior shielding that allowed a full volley of 8 photon torpedoes through, utterly destroying the Soikra. The explosion wasn’t close enough to the Marathon to damage it thanks to extensive ship to ship combat training and the lessons learned there. However, the Uvas Shalloss wasn’t prepared for the sudden destruction and she had only her forward shields up allowing the full impact of Soikra’s explosion to hit her hull directly, nearly destroying her. What the Marathon didn’t yet attempt and the Soikra didn’t fully accomplish, the chief engineer aboard the Uvas Shalloss managed via a critical fumble roll for his ship at the worst possible moment for the Klingons – and their ship also exploded. Thus, the USS Marathon racked up its first two combat kills and avenged itself upon those that had so injured it and her sister ships.

The Marathon got underway again and the Engineer managed to get Warp 6 out of her by cutting the port nacelle completely off from the EPS power feed and reconfiguring the starboard nacelle for single engine flight operation. The crew of the Marathon kept the ship ahead of and out of the hands of the Klingons until roughly 34 minutes after the battle they were joined by Task Force 28. As doing ‘warp jumping’ with a fleet of ships is problematic, especially across multiple warp bands, Commander of Battlegroup 28 Captain Harlan Mattix chose instead to engage in a running fight. At the height of the battle there were 6 Klingon Battlecruisers and 5 Nausican raiders attacking BG28 trying to get at the Marathon, who continued to shoot at them along with BG28.

Organization: Battlegroup 28
Commander: Harlan Mattix, Captain
Commander Ship Type
Captain Harlan Mattix USS Lynx Akira Cruiser
Captain Masuus Eashan USS Huntley Streamrunner Destroyer
Captain T’Lairan USS Ivanhoe Streamrunner Destroyer
Captain Dewrnot Saine USS Voodoo Spitfire Destroyer
Captain Murali Kilaru USS Wrath Spitfire Destroyer

The groups sniped at each other until the arrival of the Warp Tug USS Ob arrived, throwing off the rhythm of BG28’s defensive patterns. Once the Ob locked on the the Marathon she was able to disengage the drive and put full warp power into shields (Extending them around the Ob) and weapons while the tug towed her at warp 7, speeding up the entire Battlegroup and dramatically enhancing their lethality (though the Klingons quickly learned to stay to her port side). In the end 2 Nausican raiders were destroyed and the rest moved off, and 3 Klingon ships were destroyed while the survivors harried BG28 and the Marathon all the way to Starbase 134. Among the Starfleet vessels, the Ob took some minor structural damage, the Huntly sustained serious damaged but was able to keep up and maintain the ability to fight, and the Voodoo was badly damaged, having to eject its warp core and transporting the crew to other ships, but it is salvagable and was towed by the Lynx.

Upon arriving at Starbase134 Admiral Burtell communicated with the Officers of the Marathon and her Captain (now more or less conscious and on the bridge). She gave coordinates of the specific space dock for the Marathon, that her crew was not to leave the ship, no one in or out. That Starfleet Intelligence was setting up to process the entire crew and weed out all compromised elements. That the ship would be undergoing a full component by component inspection to ensure no more issues. Finally that there would be more instructions as time passed and to take these instructions very seriously, as all personnel would undergo full interrogation under psionic conditions to ensure the safety of the ship and crew.

View
Captain's Log
Coming out on the other side

Captain’s Log

We have made it out of the other side. We discovered one of the missing starships, but we were unable to acquire any data from the computers onboard. Massive damage and it appears that we have discovered an issue with the psyche of the survivors. We have brought them onboard, but I am still weary of them. I may have security tag them until we reach the Starbase for repairs.

We have contacted the battle unit to escort us safely there, as the damage is too great to move over Warp 5. We have had a few other ships come into our sensors, but they left as fast as they entered it. We have a few hours remaining until the group arrives. Until then, we must do all we can to avoid contact and engagement.

Once we are at the Star Base, we are going to have a complete check of the crew, as we have found yet another crew member that has been brainwashed. As well as the crew was vetted, it appears not as well as I would like. My attitude towards the officers so far has been to do their jobs. I seem to have found myself being short with one or two of them, as I am not an expert in their areas. I need them to understand that they need to give me an overview of the situation to make a command decision. If we are in battle, that is one thing that I have no issues with.

Also, Christina has been around and has shown to be an invaluable member of the Engineering team. I have given some space, as has she, but one of us will soon break the unawkwardness and we will see where that goes.

Until then, we wait for our escort and are in search of a signal coming from the ship.

View
Phase II, Session 5 & 6: Trapped In The Transwarp Domain
"There's No Place Like My Home Dimension" - Wizard Of Oz VIII, circa 2297

“There’s No Place Like My Home Dimension”

- Wizard Of Oz VIII, circa 2297

Entering the TW Conduit, the last thing that most of the bridge crew saw was the Klingon Torpedo hitting the wall of the conduit on the port (left) side of the ship because a split second later the viewscreen went dark and all lights and panels went out along with gravity and inertial dampeners. The ship lurched as the shields failed and people and objects flew in all directions, colliding with each other and objects of various sized, shapes, and sharpness. The emergency lighting kicked in right after the gravity systems. The crew had just time enough to realize they were going to hit – something – right before they did.

No one onboard escaped without bumps, bruises, and scrapes. 25 people died. Nearly half the crew had injuries ranging from serious broken bones to life-threatening injuries, or death. 78% of the casualties were on the port side of the ship. Miraculously, somehow the shields were all up, at only 20%, but up. The raised shields saved the ship and everyone’s life, though no one can say how they came back up.

In the first few minutes after ‘entry’ into the transwarp domain (TWD), Assistant Chief Science Officer and head of the Computer Science Division, LtJG Curtix Na Zach, (who was one of the very few without serious injuries) brought the Emergency Medical Hologram (EMH) and the Emergency Holographic Damage Control Team (EHDCT) systems online. By judicious and careful reallocation of resources within the computer systems he was able to create 4 functional EMHs and 4 EHDCTs.

Though there wasn’t a direct call for it, he was all too aware that the bridge had taken a serious hit (his station being on that deck and directly behind the bridge) and that command personnel would be needed in this crisis and he deployed 1 EMH there, probably saving the life of most of the people there. He sent one to Medical, one of the hardest hit areas of the ship, where the EMH was able to begin getting medical personnel back on their feet to help throughout the ship. He sent one to Engineering on a hunch (the 43 calls for EMH help may have helped influence his decision as well) and another to the Physical Sciences lab which showed on sensors to be the hardest hit area of the ship, and whose Division leader would step up and take the place of the freshly crushed science officer on the bridge (Lt Svak will be missed).

The EHDCTs LtJG Na Zach distributed to hotspot areas as well preventing the Fusion plants from overloading and preserving Auxiliary Power, clearing an EPS rupture that could have been catastrophic, preventing the loss of the port engine due to an over stressed nacelle, performing emergency shutoff of the Impulse Engines to save them from potential overload damage from the EPS situation, and afterwards literally hundreds of small tasks that allowed the ship to somewhat recover functionality over the first 3 hours in the TWD. Well done LtJG, your medal is in the mail.

In the Physical Sciences lab Lt Jog Clivurc responded well to the EMH’s treatment and was soon on his feet, ignoring the EMH as he moved out of the lab, filled with the wounded and dead of his science division and hailed the bridge. Being the senior ranked science officer on the ship and LtJG Na Zach being too valuable in his present duties, Captain Morgan promoted him to temporary Chief Science Officer as his first official duty after regaining consciousness. Upon receiving this news he made his way to the bridge and started science-ing all over the place. There were sensor scans, interesting theories, and the shocking discovery of a Starfleet vessel some distance away from their location broadcasting an automated distress call. It was the USS Ipsus, disappeared some 4.5 months ago in this area and the very ship the USS Marathon was here to replace.

No matter what the engineers did, the warp core would not activate. Most shocking to them was the fact that matter and anti-matter was colliding withing the dilithium matrix, just as it was supposed to do, but simply did not react to it’s counterpart. They weren’t sure what the issue was, though there were theories – hundreds of them (ok, 4) – and they simply couldn’t think of anything they could do to correct the situation so they moved on to their numerous other problems for the time being.

At 3 hours past entry the ship’s systems were more or less back online, at least the ones that still existed. The EPS rupture got into the transporter and replicator networks and basically blew out every part of those systems. While Chief Engineer * Vegga Aece* was unconscious and/or recovering from his fairly dire wounds, his Assistant Chief Engineer Lt Christina Williams wasn’t as badly injured and went to work on the issues the ship faced. Realizing that the repairs needed replacement parts, along with a newly requested sensor that needed to be manufactured from scratch, she directed the engineering crew and made it her primary duty to scrounge what she could and then to use them to build an engineering replicator, and then to use that to make the needed sensor system. By the time 6 hours had passed she had done both and it had been installed. She was cranky.

Lt Jog Clivurc conducted intensive scans of the space surrounding the Marathon. He looked over the engineering reports regarding what was going on with the warp core. He consulted the (surviving) civilian specialists regarding what was found and they reached a consensus of 4 theories and proposed a sensor enhancement module that could potentially prove 1 of them and rule out the other 3, or rule out 1 in favor of the other 3. Jog fed the information and made an official request of Lt Williams (as if the assistant chief engineer had nothing better to do) and she went to work on building an engineering grade replicator with which she could build more replicators, critical parts for engineering, and the new sensor module. It took 3 hours to complete, and the module took another 3, but eventually it was done and installed roughly 10 hours after entering the TWD. With the data from the new sensor module Clivurc was able to rule out 3 theories and confirm the most likely candidate.

At the 3 hour point confidence was high enough to bring the impulse engines back online, immediately supplying power to the ship and more than doubling shield strength. With the shields stronger matter and antimatter began to dislike each other again, and the warp core was brought onine, capping out at 30%. Due to its behavior as well as how the EPS conduits reacted, the idea that something had invaded the warp core and acted to inhibit matter/anti-matter reactions, though what that was. A request for WTF was sent to the Science Officer:
-Unlike our universe where gravity is by far the weakest of the 4 fundamental forces, here it is much stronger, nearly equal to the others. The ship’s graviton detectors were tuned to our universe’s level of gravitons and were simply didn’t detect them at their normal levels. The new detector was set to an extremely course resolution and picked up the massive gravimetric signature immediately. With a little refinement and computer modeling the Science Officer and Civilian Specialists formulated the theory of ‘Denatured Gravitons’ and successfully predicted, in broad strokes, how it operated later experiments conducted by the Daystrom Institute would show.

At around the 6 hour point Chief Security/Tactical Officer Lt. Stilicho Th’azyron began operations along with his Assistant began playing with a shuttlecraft on a tether to see if it was possible and safe for the ship to move in the TWD. The shuttle was fine until it passed through the shields of the Marathon, whereupon its own shields rapidly failed (3.8 microseconds) and it was crushed with massive, sudden force. It was retracted and mounted on the wall of the Captain’s ready room. A similar attempt was about to be made with a warp shuttle when the Captain thought better of the action, thinking the shuttle might be needed.

After roughly 24 hours the ship and crew were as ‘put back together’ as they were going to get and the Captain ordered that the ship set course for the distress signal of the USS Ipsus.

She was 2 hours away at full impulse and the captain the ship to travel at that speed. Shortly after entering the TWD it was noticed that the sensors worked unbelievably well, at a little more than 3 times their normal effectiveness, allowing the Marathon to determine active lifesigns onboard the Ipsus while still an hour out from her. As they closed they refined their readings and found 5 individuals onboard her who still breathed, and a great many that did not. Repeated hails were ignored or not noticed.

The ship is able to move on impulse only. The engineering team is able to determine that the ship isn’t generating the power needed to breach the
TransWarp barrier as it is currently operating. With limited options,
the Captain orders the Marathon to investigate the other ship by moving to it. Transporters are destroyed from an EPS overload, and exposing a shuttlecraft is a bad idea as well, as verified by the Tactical department. A personnel umbilical would be possibly funny, but also a bad idea as the crewman attached to it would be crushed as well. This left direct hull -
to – hull docking of the ships as the only viable boarding solution.

Sensors revealed the structural integrity fields in the Ipsus’ engineering section were set to maximum, and seemed to be using the entire output of a wounded fusion reactor to run them, along with minimal life support. The only accessible docking access that didn’t seem to be crushed was the warp ejection port, which required some interesting piloting and engineering to accomplish, but was doable. As communications were either out on the Ipsus, non-functional in this space, or they were unable or unwilling to respond, uncredited ship’s officer #3 came up with an interesting idea. Some interesting communications work resulted into tapping directly into the commbadges of the Ipsus crew and actually getting a response from some very shaken personnel. A boarding party of engineering crew and security officers erected a makeshift docking collar, force fielded it into place, and opened the ejection port of the Ipsus. From there they made their way to the deck plating below the compartment of choice and cut their way in. Using sensor scans, the Science Officer was able to advise the away team of the positions and general health status of the personal onboard the Ipsus along with the fact that 3 of them were restrained.

The Ipsus was declared lost just over 4.5 months ago. Onboard were survivors who are in bad shape. They’ve had water, food, life support, emergency medical supplies, even bedding, but they’ve been trapped here for over 4 months with no way to contact anyone and no reason to
believe anyone would even be looking for them, much less able to reach them. Several of them (there were 26 originally) died of their injuries. Others just lost it and became a threat to either themselves or others and had to be killed, or eventually killed themselves. There were 3 crewmen
that died after being restrained. Of the remaining 5, 3 of them are quite mad and are in restraints (strapped to stretchers). Only Security Specialist 2nd Class Vul’shara of Keth Uclanath and Medical Specialist 2nd Class
Geet Naveen were still somewhat coherent. The others are BCS Specialist 1st Class Keval th’Zarath of Keth Dra, Chief Science Officer Lt Jamie Werner, Ship’s Counselor Lt Cmdr Miloi Raise.

Vul’shara, after recovering her wits, told the rescue party, “I don’t know if this matters or not, but Lt. Werner was trying to restart the warp core. He’d been repairing it for two months. That’s when he lost it and nearly killed the Counselor. He was talking about being almost ready for a low energy power up about 3 days before he went crazy. It was after we finally had to restrain him by maybe 2 weeks that the Counselor went insane and just started howling all day and night. But he stopped after about a
week and just kind of stares and twitches now. I think Keval seemed to know she was becoming unbalanced because she asked to be restrained before she hurt someone. Since then, me and Geet have been taking care of them and just kind of watching to see which of us was going to be
next. Neither of us knows anything about the warp core, or what good it
would do even if we did get it started without blowing it up, and so we haven’t touched it. It’s just like Lt Werner left it.”

Geet piped up, “You should probably also know that the Counselor and the Science Officer had a theory that the space that we’re in is at least partially responsible for everyone’s unstable mental health, though they weren’t sure why that would be. I hope that’s helpful.”

The two of them collapsed into exhaustion as soon as they’re brought to sickbay. They were in poor health, both mentally and physically and the ordeal had been taxing. The bodies of their fallen crewmates are brought aboard the Marathon as well and autopsied. It was found that all of the
deceased and living crew of the Ipsus are suffering severe brain damage caused by very low dosage thalaron radiation over time. Sensors do detect trace amounts of the radiation in the space surrounding the ships. The damage to the bodies can be cured, and even the brain tissue might be regenerated given time and research, but the memories, knowledge, and personalities of the surviving Ipsus crew is permanently damaged and irretrievable. The Marathon’s shields are an effective deterrent to thalaron radiation in these dosages, and the Assistant CMO assures the Captain that the crew has nothing to fear.

Once they have been checked out, Geet and Vul’shara are assigned to quarters together to rest, they are locked in (rations are supplied), and guards are posted outside. The dead of the Ipsus (that can be reached) are laid out alongside the dead of the Marathon in the Main Cargo Bay and identified. At this point serious thought turned to how to get out of the TWD.

Multi-warp core restart sequence technique – There were arguments. And theories. And arguments about theories. And theories about arguments. It was finally decided to treat this as a contaminant the could be filtered out by the warp field, and that if a second warp field could be brought online then the two could be used to ‘clean’ the warp core. They made use of the warp core on the Ipsus that had been almost fully repaired (it only took the Marathon engineers 1 hour to bring it online). They activated the warp core of the Ipsus and expanded it to cover the core of Marathon, then shut down the Marathon’s core and restarted it within the Ipsus’ core, roughly a one hour process, which allowed the Marathon’s core to operate at considerably higher output. Then the same process was reversed to bring the Ipsus’ core online at a higher output. After 4 cycles of this, the Marathon had achieved just high enough warp output to be able to activate it’s Transwarp Drive in cutting mode.

All seemed to be going well when something in the Ipsus warp core went terribly wrong. Some undetected weakness caused a critical overload to begin building in the Ipsus’ warp core with no way to shut it down. The engineering crew got out as fast as they could, but they were too slow, and the Marathon was in the explosion zone of the Ipsus when she blew with enough power to destroy both ships. A curious quality of the heavier gravity in this domain caused the explosion to not propagate in the same way it would have in normal space, such that the Marathon was able to withstand the blast. Still, it would have been nice to bring the ship back.

Both the Captain and 1st Officer were later found to have sustained further injuries in the blast, but held on to consciousness long enough to give the order to start the TW Drive and cut out way out of “this damned Transwarp Domain”, which the crew did. Surprisingly, upon re-entering normal space they found that they had drifted in the TW Domain several light years, indicating that it was moving relative to normal space, and that they were now roughly 4 light years from Starbase 134, an 8 day journey at their best warp speed of warp 5 due to a damaged, bent, and twisted port pylon.

They signaled BattleGroup 28 who agreed to radio silence and began moving towards them, due to arrive in 4.5 days. The crew went about the business of putting the ship back into as much order as possible and patching up crew to full health. The Captain and 1st Officer kept their injuries hidden.

After roughly a day spent warping towards SB134 a signal was detected being broadcast from the ship. It was detected by doing intensive scans of the ship itself after 2 Nausican raiders showed up, moved to within their sensor range of the Marathon (but still far out of weapons range), then turned and left prompting the crew to investigate what was going on. A foreign transmitter was found, hastily deployed with no effort to hide it, in one of the forward photon torpedo tubes. Evidence was planted to implicate another crewman, who happened to be unconscious and under medical supervision since before exiting the TW Domain. Trace DNA was located and tracked to a cargo handler who was taken into custody, interrogated, then, upon the chief counselor’s advice and with his approval, a vulcan volunteer was allowed to mindmeld with her. The results showed mental fragmentation consistent with a personality overlay and memories of planting the transmitter. She was immediately stored in the brig.

At this point the Captain and 1st Officer succumbed to their wounds, had to be taken to sickbay, and missed most of the next gaming session.

View
Phase II, Session 4: Distress In The Transwarp Domain
...please pass the duct tape...

THE CONDITION OF USS MARATHON: INITIAL DIAGNOSTICS

.

ENGINES:

Warp Drive: Unknown, inoperable
Transwarp Drive: Unknown, inoperable
Impulse Engines: 93% Port Engine Output, 96% Starboard Engine Output
Auxiliary Fusion Plants: 99.2% Port Plant, 99.6% Starboard Plant
Batteries: 97.2%

SENSORS:

Transwarp Sensors: Online, 56% Operational
Long Range Sensors: Online, 80% Operational
Short Range Sensors: Online, 88% Operational
SHIELDS: Online, 42% Operational
12 Points Shielding
19 Points Shielding With Impulse Engines
COMPUTER SYSTEMS: 88% Operational

WEAPON SYSTEMS:

Phasors: Offline, 16% (crushed emitters and tracks)
Photon Launchers: Offline, 48% (crushed housing)
Tractor/Presser Beams: Offline, 20% (crushed emitters)

SUPERSTRUCTURE: 25%

Warp Nacelles: Misaligned, EPS Damage, likely more
External Bulkheads: Serious damage, catastrophic failure likely at warp 6 and above
Internal Bulkheads: 68%, more damaged Port side than Starboard
Turbolifts: Online, 93% Operational
Transporters: Offline, 37%

CREW:

46% Total Casualties, 156 of 340 Total Crew Members. Breakdown:

Crew Efficiency 54% Enlisted Officer CivSpec
Minor Injuries: 62 12 45 7
Serious Injuries: 68 33 22 12
Dead: 25 15 8 2
Total: 156 60 75 21

PCs:

Serious Injury CPT
Serious Injury XO
Dead CEO
Dead CSec/Tac
Serious Injury Sci Chief
Bumps & Bruises Asst CSO
Dead Asst CEO
Minor Injury Crew Chief
Serious Injury Asst Tac

PAINT: 82%, looks terrible


SKILL DEVELOPMENT SYSTEM

You’ve played your character a little bit now, and by now have spotted things you wish you had done, or done differently. No problem, I want you to be happy with your character(s) and I have 3 solutions for you:
1. A complete re-roll. If he/she/it is that awful then roll it up again and send it to me to evaluate.
2. Adjust your skill points. Take from one and give to another to re-balance your character.
3. Participate in skill development. If you like your character but it need work in areas or needs to add a missing skill then take advantage of the Skill Advancement System: How It Works, and the Skill Advancement Tool makes it easy to use the system. At this point you have 2 weeks of training you may apply to your character, which is enough to get a single skill to 28 if you are solely focused on it, and another 4 weeks will get you over 40. It get pretty slow after that, but 6 weeks of focused effort can get you to a professional level with intensive training, FYI.


WHAT HAPPENED:

TBD….

View
Phase II, Session 3: 110 Hours Of Drive-by Short Range Scanning Later....
Anyone got a deck of cards?

TRANSWARP APPLIED PHYSICS

GRAB AND PULL Vs. USING WARP ENGINES

Warp engines don’t work in TransWarp space:
*Transwarp engines move you in Transwarp space when cutting or in Transwarp flight
*Warp engines create power, but not movement, different physics

TransWarp engines are not to be used in existing TransWarp Conduits
*TransWarp Engines will disrupt the existing conduit and start ‘cutting’ a new conduit
*Warp engines are fine but buy you nothing, can’t affect the Conduit, different physics

The TransWarp Conduit will draw any object at the event horizon in. Let it, fighting it will cause serious structural and engine damage to the ship and could possibly (remote chance) cause damage to the ‘conduit’

A TransWarp Conduit is a pathway through TransWarp space that will flow one direction, the other direction, or both.
Starfleet needs 2-way conduits: Paired opposite one-way conduits are very rare as one-ways tend to flow the same direction.

Conduit Difficulty:

65% Conduit created collapses rapidly.
30% 1-way stable conduit, easiest to find and cut.
4.9998% 2-way stable conduit, difficult to find a long term conduit but with persistence is usually possible
0.0002% 1-way opposing paired stable conduit (theoretical). The first should be easy to find and cut, opposite is exceedingly rare

Difficulty tables to create stable Conduits:
Distance from star:

100 AU 99%
125 AU 90%
150 AU 78%
200 AU 40% Add This
300 AU 25%
500 AU No penalty

Particulate density in the area: (the emptier space is the better)

Very Low 0%
Low 5%
Moderate 15%
High 30% Plus This
Very High 50%

Sensor Probe Ping Strength Yields:
Penetration Difficulty:

0.01-0.03 0%
0.04-0.1 5% Plus This
0.11-0.15 15%
0.16-0.20 30%
0.21-0.25 50%
? = Chance of success
. .

What Happened…

The USS Marathon continued on it’s breath-taking scanning mission at sublight speeds! 96 hours were mostly spent doing high impulse drive by’s of 112 total potential transwarp entrance points scattered over a very wide area between 100 and 500 AU (1 AU = 92,960,000 miles), slowing to do intensive short range scans of each one before zipping off to the next. It took some time.

During the process of these scans, interesting sensor tachyon spikes, along with various other readings slightly above background radiation levels but unusual as well, came to the attention of the sensor crew. They worked to eliminate all possible causes and were left with the conclusion that it was a cloaking device. However it matched nothing known, and it was far too faint to be local, but finding an active cloak at range is unheard of. It was reported to the bridge and a program was built to track and analyze the signatures to see if anything useful could be learned.

Over time the theory of the mysterious cloaked vessel(s) became more likely as the readings corresponded almost exactly to the computer model of an advanced cloak on an unknown ship following the USS Marathon’s apparently random course as it flew from point to point, under the assumption that the captain of said cloaked ship believed he/she/it was impervious to scans.

Uncomfortable with the concept of being followed by a cloaked ship, plots were considered and one was eventually hatched when it was proposed by Science Officer Svak. The Marathon crew made preparations and set the trap. A position was selected, well away from any potential TW entry points, and the Marathon made a show of intensely scanning, investigating, and otherwise knowing all there was to know about one particular cubic meter of space while watching for the mystery readings to appear in their area.

The Chief Engineer, Lt Vegga Aece, had his crew reconfigure the main deflector array (took about an hour) and 2 complete volleys of level six high energy burst photons for the trap. When the readings came into the area, the XO gave the order (the Captain was doing whatever the hell it is that Captains do in their ready room) and the area was filled with tachyons via the main deflector array. A full volley of the modified torpedoes were then fired in a globular formation around the ship and detonated at maximum distance. The result was that a Klingon Bird of Prey B’rel Cruiser was forcibly decloaked. Notably, it had a strange pod attached to its ‘nose’ that sensors revealed to be of Federation origin, and later analysis determined to be from the USS Bull Run, one of the Transwarp Cutters that had been missing for some time. The Klingon vessel took flight at high impulse to get out of the tachyon-filled area, recloaked. and (it was assumed) left the area so their captain could administer fatal discipline amongst his/her/its crew. With the sensor data from the encounter, the Marathon’s scientists and specialists went to work on the Klingon’s new cloak with fresh eyes while everyone else went back to the primary mission of scanning.
sship8.jpg

Battlegroup 28, currently inbound to Regulas from Starbase 234 and assigned to the protection of the USS Marathon, was hailed and advised of the situation, whereupon they increased to maximum speed. Their commander and captain of the USS Lynx, Captain Harlan Mattix were insistent upon warping in and placing themselves in protective formation around the Marathon, but Captain Morgan demanded that he not do that, then put 13 science officers and civilian specialists on the screen at once, each explaining how their warp fields would destroy their delicate work. Mattix achieved his goal of shutting them up by acquiescing to Captain Morgan’s demand and parking in a ‘good spot’ to jump in from if needed. The Marathon went back to work performing it’s high intensity scans on potential Transwarp entry points.

This high intensity activity was interrupted about 3/4 of the way through it by a distress call from a Ferengi freighter under attack by Nausican forces believed to be pirates. As Federation space law and tradition demands, the Marathon broke off operations and sped (at sublight so as not to mess up their carefully plotted potential Transwarp entry points with a messy warp field) to the aid of the freighter. upon arrival, sensors revealed that the freighter was badly damaged and that the crew had evacuated via escape pods into space.

As the Marathon closed with the freighter, attempting to get into transporter and tractor range, 2 Nausican Corvettes dropped out of warp fairly close to the transport. They only had forward disruptors and immediately powered them up as they also began to close on the Freighter and actively scanning the Marathon as they did, the two ships now in a “Race Of Destruction” (cue 27 Ovaries, nuclear post-apocalyptic speed-metal band circa 2076, mega-hit “Race Of Destruction”). When it became clear that the Nausicans would come withing their weapons range of the freighter before the Marathon came within range of the Nausicans Lt. Th’azyron made some very clever and equally rapid adjustments to the phaser settings (that shall never be mentioned to the XO) and bought the Marathon the extra range needed for the “shot across the bow” that Captain Morgan ordered. The Nausicans seemed uninterested in the phaser array of the USS Marathon as they turned tail and ran, warping out of the area and towards the Nausica homeworld. The Marathon arrived in transporter range with just enough time to lock on to the survivors, beam them to the cargo bay, raise shields, not be killed or damaged by the explosion of the freighter, and beam their security forces site-to-site to the cargo bay where they challenged each other to a contest of seeing who could eye the various Ferengi with most suspicion. Battlegroup 28 was notified and it’s various ships sent 15 shuttles to pick up the Ferengi (who had outstayed their welcome from nearly the moment they arrived) and care for them (in holding) until a transport could arrive from Starbase 134 to take them away.

Eventually completing the task, the Marathon was left with 115 candidate sites to investigate. They were well spread out from each other so those sites were selected and probed first, then moving out from there the rest were scanned. The sites were investigated by the Marathon approaching, launching a probe into them, taking the readings from the probe, and recovering the probe for further analysis when it was possible. 60% of probes never made it back. The remainder yielded 10.5 potential cutting sites first (the .5 was a remote possibility but still worth checking).

As Battlegroup 28 gathered around her, the Marathon began cutting operations. The first 8 were not workable, though 2 of them were completed and failed on the attempt to reenter them leaving the poor Marathon 20 light years away to schlep back to Battlegroup 28’s location (though flying at Transwarp speed is hardly schlepping!). On the 9th attempt the conduit held, it held on the return trip, and it held as the Marathon made another trip through it and back to ‘cement’ it in place with their technobabble devices. Success!

Lining up to try the next one, the Marathon successfully opened the conduit and, with shields raised to full and weapons locked down (like you do) allowed the conduit to pull them into it. As this was happening the Klingon vessel uncloaked inside the BG28 ring of ships and a single photon towards the USS Marathon, then maneuvered and recloaked. LtJG Naclado at helm took emergency evasive actions, without orders from anyone; the torpedo missed the Marathon and struck the wall of the conduit instead causing it to rupture.

The Marathon was badly shaken as if by a physical impact, all power was lost, and many were hurt, hurt badly, or killed. Minimal power to emergency systems and lighting, life support, artificial gravity, and inertial dampeners kicked in rapidly and the crew began to disentangle themselves and assess their situations. The computers were off line as well as the sensors, communications, turbolifts, and only Auxiliary Power and Batteries were supplying power.

After a flurry of activity, investigation, and first aid efforts, the condition of the ship and crew was determined, the report follows:

THE CONDITION OF THE USS MARATHON: INITIAL DIAGNOSTICS

ENGINES:
Warp Drive: Unknown, inoperable
Transwarp Drive: Unknown, inoperable
Impulse Engines: 93% Port Engine Output, 96% Starboard Engine Output
Auxiliary Fusion Plants: 99.2% Port Plant, 99.6% Starboard Plant
Batteries: 97.2%

SENSORS:
Transwarp Sensors: Online, 56% Operational
Long Range Sensors: Online, 80% Operational
Short Range Sensors: Online, 88% Operational
SHIELDS: Online, 42% Operational
12 Points Shielding
19 Points Shielding With Impulse Engines
COMPUTER SYSTEMS: 88% Operational

WEAPON SYSTEMS:
Phasors: Offline, 16% (crushed emitters and tracks)
Photon Launchers: Offline, 48% (crushed housing)
Tractor/Presser Beams: Offline, 20% (crushed emitters)

SUPERSTRUCTURE: 25%
Warp Nacelles: Misaligned, EPS Damage, likely more
External Bulkheads: Serious damage, catastrophic failure likely at warp 6 and above
Internal Bulkheads: 68%, more damaged Port side than Starboard
Turbolifts: Online, 93% Operational
Transporters: Offline, 37%

CREW:
46% Total Casualties, 156 of 340 Total Crew Members. Breakdown:

Crew Efficiency 54% Enlisted Officer CivSpec
Minor Injuries: 62 12 45 7
Serious Injuries: 68 33 22 12
Dead: 25 15 8 2
Total: 156 60 75 21

PAINT: 82%, looks terrible

View
Phase II, Session 2: A Day In The Life Of Transwarp Scanning
Lockdown, a brawl, and a drunk 1st Officer, oh my....

Where we left off:
The ship and crew have recently arrived at Starbase 134 orbiting Rigel 6.
Rigel_VI_-_Starbase_134.JPG
The 1st officer joined the Captain and 2nd officer for a briefing from Admiral Burtell and are on their way back to the ship now. Information from the Admiral’s briefing and the Captain’s orders package follow:

EXCERPT FROM STARFLEET TRANSWARP PROCEDURES MANUAL

(A DAY IN THE LIFE OF TRANSWARP SCANNING)

Since the Federation does not have the technology to physically fix and hold TransWarp Conduits (as the Borg do), finding areas of space that will support long-term, self-sustaining TWCs (Transwarp Conduits) are our best option at this time. It can be a lengthy process, but the payoff is substantial to the Starfleet and the Federation. This process has been developed and refined over the last several years. Used by a ship with TransWarp capabilities, it is the most effective method we know to establish STWCs (Stable Transwarp Conduits) at this time.

01 Begin long-range scans of the system to find the areas of weakest space/time threshold.
02 Mark the areas of weakness/instability as the ship executes a meticulous, all-axis scan from 100 AU out to roughly 250 AU (125 AU from the star), roughly a 38-hour process.
03 Plot a course to take you, as efficiently as possible, to all of the areas you marked for intensive short-range scans, hitting the areas of greatest weakness/ instability first to create a list of candidate points. This is roughly a 90 hour process.
04 Track the ease of penetration for each candidate point using sensors and TW probes (your ship has 200 of these, and can manufacture more with the engineering replicators), ranging from 1.00 to 0.01, ideally looking for something in the 0.10 to 0.01 range, but accept up to 0.25 if it’s within 200 AU of the STWC endpoint. Create list of cutting candidate sites. This is roughly a 12 hour process.
05 Report your findings to Starfleet and that you are about to begin TW tests. Notify the nearest Starbase Ops Center when you are about to enter TransWarp and again when you exit. Begin creating candidate TWC’s:
…A. Generate an EM triggering pulse with the main deflector, the frequency of which is the encoded frequency that must be used every time a non-TW ship opens the Conduit.
…B. Engage TW engines and begin to create the TW field, ensure shields are at maximum, and enter the new Conduit you are creating.
…C. Using long-range sensors to detect TW eddies and maintaining Main Deflector power until you are inside TW space, push into TW space and move towards your destination point to “carve” the conduit.
…D. Use the Main Deflector at the same frequency again to create an end point, dropping TW Drive power as you pass through it. Notify Starfleet.
…E. Turn, activate the new Conduit, enter from the new end point under standard warp power, and travel to the beginning point. Notify Starfleet.

06 Reenter the TW conduit. From the inside scan for TW Domain inconsistencies, fluctuations, and outside influences that may indicate instability of a long-term conduit. A safety margin of no more than 0.02% is acceptable.
07 Notify Starfleet of the detailed results.
08 Move to the next candidate point and repeat. Continue until all candidates have been explored. The best acceptable conduit and 2 alternates will be officially logged, assuming any are found.
09 If none can be found, repeat the process traveling to a shorter mid-point. Attempt to establish 2 short runs instead of a single longer run. This is an undesirable solution but acceptable.
10 Be on the lookout for anything that might indicate the fate of the other ships as you proceed. This will add to our understanding of what’s happening and will help improve safety margins.


Starfleet Transwarp Cutters
.

USS Narsil, Nebula Cruiser – Lost, presumed Destroyed, vicinity of Ka’Tula to Starbase 241, cause: poor understanding of Transwarp physics.

USS Actium, Nebula Cruiser – Lost, presumed Destroyed, vicinity of Starbase 234, cause: suspected Klingon aggression

USS Bull Run, Nebula Cruiser – Lost, presumed Destroyed, vicinity of Starbase 234, cause: suspected Klingon aggression

USS Aries, Nebula Cruiser – Lost, presumed Destroyed, vicinity of Bolarus to Starbase 241, cause: unknown

USS Pydna, Nebula Cruiser – Active, Operating along Romulan border vicinity of Starbase 241, cause: suspected Klingon aggression

USS Salamis, Nebula Cruiser – Lost, presumed Destroyed, vicinity of Starbase 234, cause: suspected Klingon aggression

USS Onami, Nebula Cruiser – Lost, presumed Destroyed, vicinity of Starbase 234, cause: suspected Klingon aggression

USS Ipsus, Nebula Cruiser – Lost, presumed Destroyed, area of Starbase 234, cause: suspected Klingon aggression

USS MarathonActive, Operating along Klingon border vicinity of Starbase 234


USS MARATHON LONG RANGE OBJECTIVES

With the conclusion of the Starfleet Strategic Objective on Bolarus last week, final decisions were made and strategies engaged such that your long term orders are now available. You and your command crew are authorized access to this information, should you choose to inform them. This information, like everything else surrounding your ship and mission is classified, top secret clearance and need to know required.
At best possible pace, accomplish the following STWC paths (see map):
Phase I: Link up the main Federation territories with the Free Worlds of Klinzhai territories – west and east. Proceed in this order:

  • Regulus to Starbase 234
  • Starbase 234 to Starbase 84
  • Starbase 84 to Nimbus.
    Phase II: Link up the border defenses along the Klingon border of the main Federation territories. Proceed in this order:
  • Regulus to Kenda (Outpost 68)
  • Kenda to Deep Space K-7
  • Deep Space K-7 to Starbase 133
  • Starbase 133 to Toraz (Outpost 16)
  • Toraz to Boradis (outpost 48)
  • Boradis to Cestus (Outpost 26)
  • Cestus to Starbase 82
    Phase III: Link up the border defenses along the Free Worlds of Klinzhai territories. Proceed in this order:
  • Starbase 105 to Starbase 117
  • Starbaase 117 to Starbase 152
  • Starbase 105 to Bon Turani (Outpost 112)
  • Bon Turani to Vintara (Outpost 92)
  • Vintara to Starbase 123
  • Starbase 152 to Outpost 186
  • Outpost 186 to Veridian
  • Veridian to Luzaera
  • Starbase 123 to Zalda (Outpost 74)
  • Zalda to Junon (Cold Station Theta)
    Phase IV: Link up the border defenses along the Romulan neutral zone. Proceed in this order:
  • Starbase 84 to Outpost 23
  • Outpost to Tomed (Outpost 17)
  • Tomed to Qualor (Outpost 14)
  • Qualor to Kaleb (Outpost 11)
  • Kaleb to Kolaran (Outpost 95)
  • Kolaran to Dessica (Outpost 7)
  • Dessica to Bolarus

Authorized this stardate by my signature,
Rear Admiral Thora Burtell,
Starfleet Special Operations Fleet 3, Commanding


BATTLEGROUP 28

Battlegroup 28 under the command of Captain Harlan Mattix on the USS Lynx, an Akira class cruiser. With him are the USS Huntley and the USS Ivanhoe, both Streamrunner class destroyers, and the USS Voodoo and the USS Wrath, both Spitfire class destroyers.
Organization: Battlegroup 28 – Commander: Harlan Mattix,

Captain Ship Type
Captain Harlan Mattix USS Lynx Akira Cruiser
Captain Masuus Eashan USS Huntley Streamrunner Destroyer
Captain T’Lairan USS Ivanhoe Streamrunner Destroyer
Captain Dewrnot Saine USS Voodoo Spitfire Destroyer
Captain Murali Kilaru USS Wrath Spitfire Destroyer

Even though it’s only 5 ships, the group is assigned Battlegroup status to establish its priority when making requests, receiving conflicting orders, and enforcing the safety of the USS Marathon and crew answering directly, and only, to Admiral Thoris Burtell, Starbase 234 Starfleet Special Operations.


What happened?

The Captain, XO, and SO left the meeting with Admiral Burtell to head back to the transport point and back to the Marathon chatting as they went. It was soon apparent that the XO was quite drunk. It seems he had just spent the last 2 days ‘entertaining’ the Admiral while they both awaited the arrival of the Marathon. After arriving back onboard ship, the Captain ordered the XO to an out of the way lounge to sober up after a few stern words about decorum and proper respect to the Captain and setting an example and making good decisions, etc….

A shuttlepod from Starbase 134 flew over to the USS Marathon with orders from Admiral Burtell to collect the saboteur and the devices and materials related to her crimes but were locked out of docking with the airlock they were approaching and told to standby while he clarified orders with the Captain, who told him not to release the prisoner. The shuttle crew sulked in their shuttle waiting for orders from someone telling them what to do.

Starbase 134, Rigel 6
Starbase_134.jpg

The Captain communicated with Admiral Burtell who suggested (ordered) that he turn over the prisoner and materials to the shuttle, countering with the information that he had ordered that the ship be placed in ‘lock down’, no one in or out without his permission while they finish the security sweeps and searches already underway. ADM Burtell’s offer of personnel and tech to assist were turned down, and she ordered the Captain to be underway on his mission in 12 hours or turn the ship over to Starbase 134 technicians for a full sweep.

Doctor Sellers forwarded a report to the Captain during this conversation (but read later) stating that the saboteur was genetically modified, it was subtly done, and so thorough that he couldn’t be sure what race or sex the individual had originally been.

Lt Stilicho Th’Azyron received an urgent communication from his Assistant Sec/Tac officer at this point, telling him, “Sir, there is a brawl outside of lab 12!”. He arrived rapidly, greeted by the sight of 5 people in labcoats, 1 male and 4 females (1 female was vulcan), brawling (slap-fighting and scratching) with each other and the security team trying to break it up without hurting anyone. To the side was another female in a labcoat displaying poor bladder control and clearly frozen in panic, and LtJG Louisette Nørup, acting Asst Sec/Tac Officer, who was pointing a phaser at the melee in general. When Lt Th’Azyron appeared she requested, “Sir, permission to stun everyone?”, clearly in over her head and close to panic herself. Lt Th’Azyron bellowed a very intimidating couple of sentences to the effect of, “Knock it off and act like grown ups!”, which were largely ignored. At this point, for reasons that are still murky, Nørup opened fire on all individuals in the conflict pile of bodies using heavy stun setting, and the melee ended.

It looked a lot like this….
It_Looked_A_Lot_Like_This.jpeg

Lt Th’Azyron backed Nørup’s play, officially anyway, and sickbay was notified and starship services was notified – the mess was soon cleaned up. After a quick investigation, it was discovered that these were two groups from the pool of 30 civilian specialists the ship was to receive from at this starbase, and they had both independently arrived at the conclusion that they needed to get a jump on lab assignments and talked/bribed/intimidated/charmed their way into a beam over to the ship with their equipment. They both had their sights set on lab 12 because of it’s specialized equipment and they wanted to plant their flag of ownership upon it.

Ordering the CivSpecs escorted from Sickbay to a nearby conference room (without windows) Lt Th’Azyron had a ‘meeting’ with them where he laid down the law with them. There was clarity among them when he was done. Someone wet themselves again. It is notable that the CSO (Chief Science Officer) didn’t assign either team to that lab (Vulcan spite?).

The now sober first officer got roped into an unfortunate long term activity.

The Captain took it upon himself to write to Admiral Burtell’s superior officer, not realizing that she reported directly to the Admiralty Directive’s Council, the body that sits directly beneath the Federation Joint Chiefs of Staff and puts their decisions into orders issued to all of Starfleet. The Captain’s answer was short, terse, and came from the Chief of Military Operations, Fleet Admiral J. Crog (that’s right, that J. Crog, the old Andorian warhorse himself) making the communique an immediate collector’s item and also extremely classified. He referred the Captain back to Admiral Burtell who, it seems, had stuck her neck out to specifically have him assigned to this position.

Following that, the searches continued, yielding nothing and concluding (coincidentally) with Burtell’s 12 hour deadline. Beginning initial scans, the Marathon crew found a higher concentration of potential areas of weakness or instability to investigate in their 38 hour sweep. They additionally took the opportunity to run a battle simulation, destroying the Klingon B’rel Cruiser they were up against at short range and damaging themselves in the process. Lessons were learned, there were jokes, there was crying. One crewman had fun.
Klingon_Emblem.jpg

View
Phase II, Session 1: Taking Command
USS Marathon, Refit and a new crew….

toboldlygobanner.jpg

Transwarp domain space – the new final frontier. These are the voyages of the USS Marathon. Her multi-year mission is to seek out optimal entry locations, exit locations, build Stable Transwarp Conduits (STWC) between them, and do so without getting killed. To boldly go where most such ships have disappeared without a trace. Pulsar_Class_Exploration_Cruiser.JPG Her crew is made up of the finest minds with relation to all phases of the STWC building process available. The officers and crewpersons of the Marathon are supplemented by 30 civilian specialists, support personnel to assist the Marathon in any potential encounters with the unknown. Together they will strive to create a vast network throughout the United Federation of Planets which will facilitate travel, trade, defense, and greatly reduce the environmental load the warp drives are placing on normal space.

TransWarp_II_System_Diagram.JPG


Theater Briefing

Klingon relations reached an all time high at the moment of the Dominion surrender and have been deteriorating at a progressively rapid pace ever since. Several incidents in Cardassian space have led to shooting matches between Klingon forces and Star Fleet.
Star Fleet’s diplomatic intervention in the Klingon/Romulan conflict following the “Nemesis” incident were viewed by the hawks among the Klingon Empire as interference in their “right to make war” and portrayed Chancellor Martok as a weakling in the pocket of the Federation. Their masterful use of propaganda related to the event led directly to the ascension of Chancellor Kur’gek to the head of the Klingon Council after killing Chancellor Martok in a dual. The loss of Martok was a strong blow to Federation/Klingon relations and Kur’gek has ridden higher and higher on the political capital he and his cronies manufacture at the expense of the Federation.

Having fully consolidated his power, the imminent supernova of the Hobus star was a gift on a silver platter for Kur’gek. Roughly 50% of Klingon forces had secretly assembled along the border, ready for the moment of greatest weakness and assaulted across shortly before the supernova event of the Hobus star. They overwhelmed the Romulan border defenses and plunged deeply into Romulan territory, attempting to take the new Romulan capital of Remii.
Joint Romulan/Vulcan and some Federation forces held the system from the Klingons after a protracted and viscous battle. At Romulas and Remus the Klingon forces attacked every non-Klingon ship that came within weapons range, including many unarmed Federation transport vessels providing humanitarian assistance. Thanks to the warning of the Romulan border defenses, enough warning was received for 2/3 of the Federation forces to vacate the system prior to the Klingon forces arrival.

While the future is unclear, what is clear is that the Klingons mean to end the Romulans as a power in the quadrant and have made their move at the worst possible time from the perspective of the Romulans. Without help, the Klingon gambit is likely to succeed and the Romulan Star Empire will fall.


Captain’s Orders:

GRADE ADVANCEMENT: Commander Morgan, as of stardate 2387.082 at 11:05 hours you are hereby promoted to the rank of Captain in the service of the Star Fleet of the United Federation of Planets, and accorded all the rights and privileges associated with this position. Congratulations. (If you fail you die. – Addendum for Klingon officers, if applicable).

ORDERS: Captain Morgan, you are hereby ordered to travel to the Cardassia Prime, Federation Drydock Facility 4, to arrive by Stardate 2387.0904, there to report to Facility Commander Captain Terrance Finstadd, and take command of USS Marathon NCC-72002, currently under refit at said facility. Complete such remaining refit and repair as is necessary and be underway no more than 2 days from accepting command. Move with rapidity to Starbase 74, there to take on additional crew and officers. The USS Marathon will undergo minor refit while at Starbase 74, receiving a type 36 sensor array modification to further its capabilities to complete the mission. Upon completion of sensor installation, move with rapidity to Rigel, and there take on remaining crew and officers. Report via subspace to Admiral Thoris Burtell, Starfleet Special Operations, Starbase 234 for assignment and official duties.


Ship’s orders:

STWC Exploration: USS Marathon, NCC-72002, is hereby transferred to Starfleet Special Operations Fleet 3 based at Starbase 234, under command of Admiral Thoris Burtell as of stardate 2387.0904 at 11:05 hours. USS Marathon is hereby ordered to proceed immediately to Rigel, there to begin without delay to conduct exhaustive surveys of space in the vicinity of Rigel and Starbase 234 and, if necessary, points in between towards the goal of establishing a Stable Transwarp Conduit between Regulus and Starbase 234. This mission is of highest priority to Starfleet, and the warp 6 speed restriction does not apply to the USS Marathon for the purposes of accomplishing this mission. Unlimited first priority access to the Federation Stable Transwarp Conduit Network is authorized for the duration of the missions of the USS Marathon.

STANDING ORDERS:
1. Observing the prime directive where it applies is the highest priority.
2. Protect the citizens, property, ships, trade, and sovereign territory of the Federation in the area of operation is the second highest priority.
3. Use diplomacy to resolve situations unless given no other choice, and then use the least amount of force possible to accomplish the above directives.
4. Seek a point in the Regulus system as close as possible to the Rigel/Regulus STWC endpoint from which to establish a STWC endpoint.
5. Seek a point near Starbase 234 from which to establish a STWC endpoint.
6. Create a STWC between these endpoints and verify stability and safety of said STWC.
7. Additional mission specific directives will be cut on an as needed basis through the office of Starfleet Special Operations Fleet 3 Adjutant, BAdm Fintes.
8. Under no circumstances will you allow this technology and/or related materials and records to fall into the possession of non-Starfleet hands and you will take any and all necessary measures, regardless of how dire, to ensure this.
9. Observe the following Rules Of Engagement:
..A. Federation ships shall not fire upon another ship unless first fired upon.
..B. This supersedes Rule of Engagement A in the event that engaging another vessel is necessary to accomplish the directives above, and then Federation ships shall use the least force necessary to accomplish the directive(s).
..C. When encountering superior numbers Federation ships will avoid contact, break contact, and/or withdraw from conflict if there are no considerations towards the directives above.
..D. When engaged in combat in the accomplishment of the directives above, Star Fleet vessels shall do their utmost to ensure they are meeting these directives, and shall not withdraw from conflict unless their continued presence can make no difference in the outcome. Captains shall exercise prudence to protect their ship and crews balanced against the accomplishment of directives.
..E. With all other directives satisfied, protect the ship and its crew above all other considerations.

Starfleet_Special_Operations_AOE_SB234.JPG

What Happened:

The Chief Engineer, Lt Cmdr Vegga Aece, Was the first senior officer to board the USS Marathon, arriving a full 9 days ahead of the others. He was greeted enthusiastically, if abruptly, by Captain Terrance Finstadd, commander of the Starfleet refit facility at Cardassia (yes, really) Prime. Cpt Finstadd had just finished dressing down (screaming at) one of his ratings, a very young (and smallish) caitian named Phipps for some alleged grievance that Phipps had committed.

The Starfleet refit facility consisted of a very small mobile habitat/office and 9 mobile docking facilities plus a number of enormous Starfleet shipping containers used for warehousing. The USS Marathon was in Dock #4.

Cpt Finstadd gave Vegga’s orders a cursory once over and had Phipps fly him over to the ship on a ‘Worker Bee’ construction pod. Phipps gave the Lieutenant Commander the full external tour of the ship, doing a full orbit around and then over and under the ship. The only real surprises were the pod in the ‘Roll Bar’ above the ship was clearly empty, and the bottom of the secondary hull where one would normally see the warp core ejection port was cored out in a circle through 4 decks and 9 meters across, leaving main engineering open to space.

Upon boarding Vegga made his way to the bridge, assumed on-board command as he was the ranking officer, and made his was to Main Engineering. There he met the Transwarp Engine Crew and the Transwarp Sensor Crew, technically part of engineering, who promptly introduced themselves and then informed him that they were not in his chain of command. They further briefed him that they would work efficiently with the engineering crew, but that now one in the engineering department, including him, had the clearance to be briefed on, read up on, touch, of interfere in any way with them performing their duties regarding either the Transwarp engines or the Transwarp sensor systems. This is when it became apparent to Vegga that this ship was to be equipped with Transwarp capabilities, as his orders and briefing had made no mention of it in any way.

Over the next several days the ship was tweaked, tuned, painted, polished, and given a new warp core. It was mounted to the decking that had been cored out from the secondary hull, and the entire thing was mounted to the Marathon as a single piece. An anti sensor field was placed around the core and decks and a tarp of some kind tossed over the core itself to prevent prying eyes. Installation was smooth and by the numbers, except for the parts that were not.

Things were starting to run smoothly when, suddenly, the Captain showed up, precisely on time. No one perished, though it was a near thing with Phipps.

The only incident was when Lt. Stilicho Th’azyron of Keth Idrani, the Security/Tactical Chief reported in. Captain Finstadd was again chewing out Phipps, whose fur on the left back side of his head was heavily smoking from some sort of burn. Not paying complete attention to what was happening in the worker bee shuttle with the stench of the still smoking Phipps, and Phipps being distracted for some reason, he delivered Lt Stilicho Th’azyron of Keth Idrani to the USS McKinley. Closely observing his surroundings Th’azyron noticed that this did not seem to be his ship. After a quick conversation with Captain Harkness, Phipps departed and delivered the LT to the Marathon after the obligatory fly around.

Worker_Bee_class_Shuttle_Pod.jpg

1. Meet and greet: PC’s arrive, Chief Engineer first, Meet Facility Commander Terrance Finstadd, get refit briefing (cover the ship upgrades) if authorized, meet 3rd assistant Shipwright Phipps (very small very young caitian), tour ship, meet other PC’s and important NPC’s present, gets updates on crew arrival ETA’s at destinations.

There was much meeting and greeting and backgrounds were compared to see if the PC’s may have served together at any time. It seems the Captain and Lt Christina Williams, the Assistant Chief Engineer, um, did serve together and know each other at some point. It also seems that the Chief Engineer and Assistant Chief Engineer had met at a training school and did not much care for each other.

2. Refit complete end of first day, roughly 2am. Basic shakedown testing of new systems takes 1/2 day

The shields are tested under phaser fire from USS McKinley, starting at very low levels and progressing to higher levels with diagnostics in-between. Photon & Quantum torpedoes are launched at large asteroids (4 total are destroyed) designated for munitions testing. Systems check out, diagnostics are all in the green.

After receiving this news, and anxious to have the Dock #4 available for the next ship, Cpt Finstadd, with Phipps looking surly in the background, addressed the Captain via comms. “Cardassia Prime, Federation Drydock Facility 4, Terrance Finstadd commanding. I do hereby release the USS Marathon, NCC-72002, from this facilities care for Active Operations, transferring control to its Captain and crew so they may make for Starbase 74 in the Tarsus system. Smooth operations to you Marathon. Finstadd, out.”

Cpt Finstadd transfers the USS Marathon to Burtell after successful systems test

Arriving via tightbeam transmission from Cpt Finstadd’s “office”, Ship’s orders:
STWC Exploration: USS Marathon, NCC-72002, is hereby transferred to Starfleet Special Operations Fleet 3 based at Starbase 234, under command of Admiral Thoris Burtell as of stardate 2387.0904 at 11:05 hours. USS Marathon is hereby ordered to proceed immediately to Rigel, there to begin without delay to conduct exhaustive surveys of space in the vicinity of Rigel and Starbase 234 and, if necessary, points in between towards the goal of establishing a Stable Transwarp Conduit between Regulus and Starbase 234. This mission is of highest priority to Starfleet, and the warp 6 speed restriction does not apply to the USS Marathon for the purposes of accomplishing this mission. Unlimited first priority access to the Federation Stable Transwarp Conduit Network is authorized for the duration of the missions of the USS Marathon.

3. Set course for Starbase 134 via STWC chain with skeleton (mostly engineers) crew. A. 1.5 hours travel at Warp 2 (general speed limit within most star systems), 108.83 AU, to STWC entrance in Cardassia system and drop in, 1.24 hours to exit in Bajor system 6 LY Distance. B. 3 hours travel in Bajor system at Warp 2, 217.66 AU, to reach next STWC entrance, 4.33 hours to exit in Trill system 21 LY distance. C. 1 hour travel in Trill system at Warp 2, 72.55 AU, to reach next STWC entrance, 3.09 hours to exit in Draylon system, 15 LY distance. D. 2 hours travel in Draylon system at Warp 2, 145.11 AU, to reach next STWC entrance, 2.72 hours to exit in Tarsus system, 13.2 LY, near Starbase 74.

4. Layover here for 6 hours and receive sensor pod upgrade as per secondary order set, pick up 1/3 crew (various enlisted specialists), Department Heads, & 2nd Officer. Continue on journey.

Crisis of equipment failure, or was it?
Much of what took place is classified. The essence is that a device was used to disrupt the power systems and emergency forcefield system aboard the Marathon in Coridan space, traveling at warp 1 across that system towards the STWC to Rigel. The ship was stopped while repairs repairs were made, the device was disarmed and disconnected, and the ship was searched. Other devices were found, the investigation revealed the saboteur, and the devices were found to be of REDACTED origin.

Charlie, the ship’s counselor had a conversation with the suspect yielding the location of other devices that weren’t found. The work of the Chief SEC/TAC officer, with assistance from LtJG Curtix Na Zach, the Assistant Chief Science officer uncovered the identity of the suspect, and the captain and the chief engineer were both very involved in the quick resolution of the situation. An additional device was uncovered in the investigation that was not placed by the saboteur and it’s unclear whether all devices are found at this time.

5. Travel to Starbase 134 in Rigel. There meet Admiral Thoris Burtell in via subspace upon arrival at Starbase 134. Receive Captain’s briefing along with 1st officer.

Surprising the captain and officers of the Marathon, Admiral Burtell was waiting at Starbase 134 and comms the Marathon as they enter their holding position. This gives the officers no time to work on their investigation before the Captain and SO have to beam to the Starbase and meet with the Admiral.

The captain and SO are met at the beamdown point by Admiral Burtell’s officious little Adjutant, Branch Admiral Izzy Lefler (no image available), who escorted them to a meeting room where the Admiral and the ship’s XO, Cmdr Ano Merzek (image not available), was waiting for them.

Captain’s Briefing:
Transcribed from the logs of Admiral Burtell, Special Operations, Starbase 234 from her briefing of Cpt Morgan and command crew at Starbase 134. After meeting and greeting and typical pleasantries Burtell begins:

“There’s no sense in candy coating this gentlemen; your mission is extremely hazardous. You should know that, though we officially claim it to be 3, we’ve lost 5 ships already in this area attempting to do exactly the mission you’ve been assigned. The Klingons are a direct threat to you – they don’t want us in the Romulan/Klingon war. They know that if we enter, we’ll come in on the Romulans side of things. God, I can’t believe I just said that… Sorry, Captain. To continue…

“As much as they do not desire the Federation in the fight, they are preparing for the worst. They know what we’re up to out here, and in particular, what you’re up to out here. They know what a Transwarp Pulsar Class is and what it means if you succeed: It means a direct, high speed pipeline of Federation ships, personnel, and materials arriving on their doorstep, rolling in from the heart of the Federation to reinforce in a matter of a couple of days instead of several weeks. They are not enthused.

“With that sort of threat a distinct possibility, they can’t allow it to happen, but they can’t get caught doing it or they’ll push us towards an alliance with the Romulans. Therefore, there is every reason to believe that there are cloaked Klingon vessels in the area you’ll be working. Furthermore, there is every reason to believe that they had a hand in the disappearance of your 5 missing Transwarp sister ships.

“Your crew was selected for their capability, not their compatibility. You have some, ah, personalities among them, especially among your senior officers. They are all very skilled at what they do, the exact skills you’ll need to make this mission a success and help you overcome the unexpected. However, that typically carries with it an ego to match. It should be an eventful tour for your first command, and a strong challenge for your leadership and that of your command crew.

“Your ship is one of only 2 Transwarp vessels currently in Starfleet. In order to give you every chance of actually succeeding and not sharing the fate of your predecessors, you’ve had some upgrades to your vessel. The engines, of course, you know about. However, in addition to those, your shields are the very best available that we could fit on a ship of your class. Your computer cores have been updated to the most advanced systems in Starfleet, which is necessary for the last major upgrade, your sensors. From what we’ve been learning from your sister ship, the USS Pydna, operating out of Starbase 241, our closest star base to the Romulus system, we’ve made upgrades that will make your scanning much more effective and hopefully let you complete your mission more quickly.

“Support is available. This mission is critical and we are prepared to support you all we can. However, as you are moving through Transwarp space you’ll be outrunning any support we can give you and we’ll have no idea where you’ll re-emerge into normal space, or what will be awaiting you there. In the Regulus area is battlegroup 28 under the command of Captain Harlan Mattix on the USS Lynx, an Akira class cruiser. With him are the USS Huntley and the USS Ivanhoe, both Streamrunner class destroyers, and the USS Voodoo and the USS Wrath, both Spitfire class destroyers. As you can see, we’re making a strong commitment of hardware to your cause, for what it’s worth. Yes, we expect success, but more than that, it’s absolutely vital that we have it! Captain, can you get this done, are you the Captain for the job?”

“I wouldn’t be here if you and Starfleet didn’t think I was, Admiral”, was the captain’s cocky answer.

Ignoring the disrespectful attitude, the gallant admiral continued, “The star systems briefing transferred to your computer have the latest Starfleet Intelligence on the systems in the area – please avail yourself of it. If you need anything don’t be shy. You’ve got a priority ship on a priority mission – it doesn’t happen often, so enjoy it Captain! What are your questions? Very well, brief your people and go to work Captain. Questions?”

The situation with the people in engineering that aren’t officially under the chief engineer’s command was raised, and Burtell was surprised that Starfleet Intelligence was playing this in such a heavy handed manner. She confirmed that they are actually techs from Starfleet Intelligence, and that they are under the command of whomever the captain says they are under, though they didn’t bother to disclose that to anyone, nor did their orders require them to. Not to worry, she would address proper protocols when cutting orders with the SI Admiral in question, and the captain is free to operate his ship as he sees fit.

The situation with the sabotage was then brought up and the Admiral promised the Captain that he would be provided with whatever help he wanted, and to just let her know what he wanted.

“Very well then, good luck to you. Dismissed.”


Following the briefing with the admiral, the Captain, XO, and SO all had the opportunity to, at long last, meet each other.

View
Phase II, Session 0: Character Building, Player Greetings, Learning the System
Wow, there's a lot of setup to this....

OFFICIAL LAUNCH DATE: 11/11/2017 3:00PM GMT-6
.
.

GAME FREQUENCY: WEEKLY
.
.

To Get Started….
.

Step 1: You already did it (it was joining Discord! If you didn’t, please go to Star Trek: Aftermath on Roll20
Step 2: You already did it (it was joining Obsidian Portal!)
Step 3: Join Roll 20
Step 4: Sign Up For a Free Box.com Account (no one makes any money on this, but it’s a free 10GB for you and gives you access to the gaming stuff and a lot more) then send the GM the email you used to sign up with so he can give you permission to access things
Step 5: Download the Character Generator tool (which you can’t do if you don’t do step 4)
Step 6: Choose your position on the ship (Again, step 4 required)
Step 7: Go through a character generation walk through to learn how to use the tool (don’t fall in love with your first try!)
Step 8: Develop your character concept, use the CG tool, and build your Starfleet Officer. Go nuts with it! Write up details, hopes, dreams, an ugly divorce, a whirlwind romance, and why you have that artificial arm and an overpowering fear of shrimp. Or do nothing,
Step 9: Select a secondary position (not department head or higher) that you will occasionally play, but not your main. Follow steps 6 and 8.
Step 10: Grouse with the other players about what a jerk the GM is (meet and greet and have fun). We’re ready to go on the next game.

At this point we can debate the best time to play if my posted schedule doesn’t work for everyone.

View

I'm sorry, but we no longer support this web browser. Please upgrade your browser or install Chrome or Firefox to enjoy the full functionality of this site.