Star Trek: Aftermath (Klingon Phase)

Starting Game Situation

(From Home Page)

Session 0: Building Characters
Pre-Session Campaign Information

Star Trek: Aftermath, Cardassian Theater

Session 1: Character Building

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



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 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.

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


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.


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.

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.


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.


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.

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.
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:



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


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 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

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….

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.

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



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.

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:


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%

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

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

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%

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

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




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%


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


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


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%


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


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


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.



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.

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.

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.


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).


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.


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.